From 392ce9582df69b0d831a6bf29bc2a6f8f020913f Mon Sep 17 00:00:00 2001 From: Manuel Lorenzo Date: Thu, 18 Dec 2025 20:37:24 +0100 Subject: [PATCH] bump documentation references from 4.19 to 4.20 Signed-off-by: Manuel Lorenzo --- README.md | 6 +++--- docs/DEVELOPMENT.md | 2 +- values-4.18-hub.yaml | 6 ------ values-4.19-hub.yaml => values-4.20-hub.yaml | 0 values-hub.yaml | 2 +- 5 files changed, 5 insertions(+), 11 deletions(-) delete mode 100644 values-4.18-hub.yaml rename values-4.19-hub.yaml => values-4.20-hub.yaml (100%) diff --git a/README.md b/README.md index bd702a46..0a6e0998 100644 --- a/README.md +++ b/README.md @@ -16,11 +16,11 @@ Showcases the Zero Trust capabilities across Red Hat's product portfolio in a re The following components are included in the Layered Zero Trust Pattern * OpenShift cluster hardening - * [Compliance Operator](https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/security_and_compliance/compliance-operator) + * [Compliance Operator](https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/security_and_compliance/compliance-operator) * [Red Hat Build of Keycloak](https://access.redhat.com/products/red-hat-build-of-keycloak/) * Identities to access pattern components * OIDC client to authenticate uses to a web application -* [Red Hat Zero Trust Workload Identity Manager](https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/security_and_compliance/zero-trust-workload-identity-manager) +* [Red Hat Zero Trust Workload Identity Manager](https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/security_and_compliance/zero-trust-workload-identity-manager) * Provides identities to workloads running within OpenShift * [HashiCorp Vault](https://www.hashicorp.com/en/products/vault) * Secure storage of sensitive assets @@ -45,7 +45,7 @@ Utilize the following steps to prepare your machine and complete any and all pre ### Prerequisites -1. An OpenShift Container Platform 4.19+ cluster with: +1. An OpenShift Container Platform 4.20+ cluster with: 1. Publicly signed certificates for Ingress 2. A default `StorageClass` which provides dynamic `PersistentVolume` storage 2. To customize the provided default configuration, a GitHub account and a token for it with repositories permissions, to read from and write to your forks, is required. diff --git a/docs/DEVELOPMENT.md b/docs/DEVELOPMENT.md index 65dcd5ff..1e5497a1 100644 --- a/docs/DEVELOPMENT.md +++ b/docs/DEVELOPMENT.md @@ -17,7 +17,7 @@ The following options should be selected: * Activity: Practice / Enablement * Purpose: Trying out a technical solution * Salesforce ID: Can be omitted (See note below) -* OpenShift Version: 4.19+ +* OpenShift Version: 4.20+ * Features * Enable Cert Manager * Enable Cert Manager API diff --git a/values-4.18-hub.yaml b/values-4.18-hub.yaml deleted file mode 100644 index faa4f2ef..00000000 --- a/values-4.18-hub.yaml +++ /dev/null @@ -1,6 +0,0 @@ -clusterGroup: - subscriptions: - acm: - name: advanced-cluster-management - namespace: open-cluster-management - channel: release-2.12 diff --git a/values-4.19-hub.yaml b/values-4.20-hub.yaml similarity index 100% rename from values-4.19-hub.yaml rename to values-4.20-hub.yaml diff --git a/values-hub.yaml b/values-hub.yaml index 02eca5e3..65b36456 100644 --- a/values-hub.yaml +++ b/values-hub.yaml @@ -105,7 +105,7 @@ clusterGroup: # odf: # name: odf-operator # namespace: openshift-storage - # channel: stable-4.19 + # channel: stable-4.20 # annotations: # argocd.argoproj.io/sync-wave: "-4" # Install after OperatorGroup (-5) # quay-operator: