WIP: Support Matrix for OpenShift Jenkins releases

- Add Support Matrix for OpenShift Jenkins releases
- Add FAQ

Signed-off-by: Vinu K <[email protected]>

Author: k37y

modules/relocation-of-openshift-jenkins-images.adoc

@@ -49,3 +49,44 @@ $ oc import-image jenkins-agent-nodejs -n openshift
 ----
 $ oc import-image jenkins-agent-maven -n openshift
 ----
+
+.What is the Jenkins support matrix for OpenShift, including supported versions and architectures?
+
+Jenkins supports the following architectures across {product-title} releases.
+
+- amd64
+- arm64
+- ppc64le
+- s390x
+
+However, for OpenShift Extended Update Support (EUS) releases, only the amd64 architecture is officially supported. As a result, OpenShift Jenkins images are shipped exclusively for amd64 on these releases. This is because the {product-title} platform itself supports only the amd64 architecture for EUS releases. Refer to [Red Hat Jenkins Support Matrix](https://access.redhat.com/articles/7115356) for more information.
+
+.When Red Hat updates Jenkins container images, are they available for all OpenShift versions simultaneously?
+
+Yes, Jenkins container images are updated on a quarterly basis, and the updates are made available for all supported Jenkins images across all supported {product-title} releases.
+
+.How long are the released Jenkins images supported?
+
+Red Hat supports only the latest Long-Term Support (LTS) version of the Jenkins core, as provided in our latest container images. We do not support multiple core versions. Our policy is to align with the latest Jenkins LTS version released by the upstream community.
+
+.Does the Jenkins release align with OpenShift versions?
+
+Yes. Our goal is to maintain platform alignment—meaning Jenkins controller and agent images are built and tested for each supported {product-title} releases.
+
+.Are Jenkins release timelines aligned with OpenShift release cycles?
+
+Jenkins is no longer part of the {product-title} core payload. Releases are managed separately. However, our intent is to publish updated OpenShift Jenkins images for newly released {product-title} releases within a few weeks of the {product-title} GA release.
+
+.Does Red Hat follow the upstream Jenkins lifecycle and LTS versions?
+
+Yes. We align with the Jenkins upstream lifecycle and follow the LTS version. Red Hat typically ships OpenShift Jenkins image updates quarterly unless a critical fix requires an out-of-cycle release.
+
+To verify the current Jenkins LTS version:
+- Navigate to the Jenkins Catalog → Packages section
+- Search for “Jenkins”
+- The result will show two packages—one of which is the Jenkins LTS package.
+
+.What is not supported?
+- Jenkins versions older than the current OpenShift Jenkins LTS are not supported.
+- Running Jenkins outside of {product-title} is not supported.
+- Multiple core versions of Jenkins are not supported. Plugins bundled with our OpenShif Jenkins images follow the same versioning across all supported {product-title} releases.