[WFLY-19335] [COMMUNITY] Include instructions to run quickstarts on Kubernetes

[kabir]

https://issues.redhat.com/browse/WFLY-19335

[bstansberry]

@kabir @emmartins What does 'community' stability mean in the context of QS?

Stability levels have meaning in the sense that users can explicitly opt in to allow things of a given level without risking choosing things at a lower level. This is enforced via things like the --stability param to standalone/domain.sh and parameters passed to galleon-based provisioning tooling.

And, to be blunt, we want to be able to easily make them unavailable downstream.

How does that work for QS?

[kabir]

@bstansberry at the moment, the new content should not be rendered in EAP (via Asciidoc if statements around the includes of the k8s content). We already test on Kubernetes but don't advertise it to the users.

[emmartins]

@bstansberry what @kabir described is the standard way we ATM disable the rendering of upstream only content, e.g.:

ifndef::ProductRelease,EAPXPRelease[]
include::../shared-doc/build-and-run-the-quickstart-with-kubernetes.adoc[leveloffset=+1]
endif::[]

I guess we could consider to replace those attrs with a stability level, something like:

#only defines all stability levels if not product, otherwise only default 
ifndef::ProductRelease[]
:StabilityExperimental:
:StabilityPreview:
:StabilityCommunity:
endif::[]
:StabilityDefault:

#kubernetes feature is community level, once promoted it should use instead  ifdef::StabilityDefault[]
ifdef::StabilityCommunity[]
include::../shared-doc/build-and-run-the-quickstart-with-kubernetes.adoc[leveloffset=+1]
endif::[]

PS: we would still need those ProductRelease,EAPXPRelease attrs, for instance to switch conditional content from wildfly maven plugin to eap maven plugin