Merge pull request #44220 from rolfedh/RHDEVDOCS-3942

RHDEVDOCS-3942 Tracker for 2069771 - surface maven/nodejs pod templat…

Author: JStickler

modules/images-other-jenkins-config-kubernetes.adoc

@@ -11,6 +11,15 @@ To use the Kubernetes plug-in, {product-title} provides images that are suitable
 
 Both the Maven and Node.js agent images are automatically configured as Kubernetes pod template images within the {product-title} Jenkins image configuration for the Kubernetes plug-in. That configuration includes labels for each of the images that can be applied to any of your Jenkins jobs under their Restrict where this project can be run setting. If the label is applied, jobs run under an {product-title} pod running the respective agent image.
 
+[IMPORTANT]
+====
+In {product-title} 4.10 and later, the recommended pattern for running Jenkins agents using the Kubernetes plug-in is to use pod templates with both `jnlp` and `sidecar` containers. The `jnlp` container uses the {product-title} Jenkins Base agent image to facilitate launching a separate pod for your build. The `sidecar` container image has the tools needed to build in a particular language within the separate pod that was launched. Many container images from the Red Hat Container Catalog are referenced in the sample image streams present in the `openshift` namespace. The {product-title} Jenkins image has two pod templates named `java-build` and `nodejs-builder` with sidecar containers that demonstrate this approach. These two pod templates use the latest Java and NodeJS versions provided by the `java` and `nodejs` image streams in the `openshift` namespace.
+
+With this update, in {product-title} 4.10 and later, the non-sidecar `maven` and `nodejs` pod templates for Jenkins are deprecated. These pod templates are planned for removal in a future release. Bug fixes and support are provided through the end of that future life cycle, after which no new feature enhancements will be made.
+
+// Writer: This admonition is tied to the "Non-sidecar pod templates for Jenkins" deprecation item (JKNS-257) in the OpenShift 4.10 release notes. Update this admonition when this deprecation status eventually changes to "removed."
+====
+
 The Jenkins image also provides auto-discovery and auto-configuration of additional agent images for the Kubernetes plug-in.
 
 With the {product-title} sync plug-in, the Jenkins image on Jenkins startup searches for the following within the project that it is running or the projects specifically listed in the plug-in's configuration: