Skip to content

bump documentation references from 4.19 to 4.20 #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mlorenzofr merged 1 commit into from
Dec 18, 2025
Merged

bump documentation references from 4.19 to 4.20 #91

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion docs/DEVELOPMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
6 changes: 0 additions & 6 deletions values-4.18-hub.yaml
View file
Open in desktop

This file was deleted.

0 values-4.19-hub.yaml → values-4.20-hub.yaml
View file
Open in desktop
File renamed without changes.
2 changes: 1 addition & 1 deletion values-hub.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down