Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 1. Red Hat OpenShift GitOps release notes
Red Hat OpenShift GitOps is a declarative way to implement continuous deployment for cloud native applications. Red Hat OpenShift GitOps ensures consistency in applications when you deploy them to different clusters in different environments, such as: development, staging, and production. Red Hat OpenShift GitOps helps you automate the following tasks:
- Ensure that the clusters have similar states for configuration, monitoring, and storage
- Recover or recreate clusters from a known state
- Apply or revert configuration changes to multiple OpenShift Container Platform clusters
- Associate templated configuration with different environments
- Promote applications across clusters, from staging to production
For an overview of Red Hat OpenShift GitOps, see About Red Hat OpenShift GitOps.
1.1. Compatibility and support matrix Copier lienLien copié sur presse-papiers!
Some features in this release are currently in Technology Preview. These experimental features are not intended for production use.
In the table, features are marked with the following statuses:
- TP: Technology Preview
- GA: General Availability
- NA: Not Applicable
In OpenShift Container Platform 4.13, the stable
channel has been removed. Before upgrading to OpenShift Container Platform 4.13, if you are already on the stable
channel, choose the appropriate channel and switch to it.
OpenShift GitOps | Component Versions | OpenShift Versions | |||||||
---|---|---|---|---|---|---|---|---|---|
Version |
| Helm | Kustomize | Argo CD | Argo Rollouts | ApplicationSet | Dex | RH SSO | |
1.9.0 | 0.0.49 TP | 3.11.2 GA | 5.0.1 GA | 2.7.2 GA | 1.5.0 TP | NA | 2.35.1 GA | 7.5.1 GA | 4.12-4.14 |
1.8.0 | 0.0.47 TP | 3.10.0 GA | 4.5.7 GA | 2.6.3 GA | NA | NA | 2.35.1 GA | 7.5.1 GA | 4.10-4.13 |
1.7.0 | 0.0.46 TP | 3.10.0 GA | 4.5.7 GA | 2.5.4 GA | NA | NA | 2.35.1 GA | 7.5.1 GA | 4.10-4.12 |
-
kam
is the Red Hat OpenShift GitOps Application Manager command-line interface (CLI). - RH SSO is an abbreviation for Red Hat SSO.
1.1.1. Technology Preview features Copier lienLien copié sur presse-papiers!
The features mentioned in the following table are currently in Technology Preview (TP). These experimental features are not intended for production use.
Feature | TP in Red Hat OpenShift GitOps versions | GA in Red Hat OpenShift GitOps versions |
---|---|---|
The custom | 1.9.0 | NA |
Argo Rollouts | 1.9.0 | NA |
ApplicationSet Progressive Rollout Strategy | 1.8.0 | NA |
Multiple sources for an application | 1.8.0 | NA |
Argo CD applications in non-control plane namespaces | 1.7.0 | NA |
Argo CD Notifications controller | 1.6.0 | NA |
The Red Hat OpenShift GitOps Environments page in the Developer perspective of the OpenShift Container Platform web console | 1.1.0 | NA |
1.2. Making open source more inclusive Copier lienLien copié sur presse-papiers!
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
1.3. Release notes for Red Hat OpenShift GitOps 1.9.4 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.9.4 is now available on OpenShift Container Platform 4.12, 4.13, and 4.14.
1.3.1. Errata updates Copier lienLien copié sur presse-papiers!
1.3.1.1. RHSA-2024-0691 - Red Hat OpenShift GitOps 1.9.4 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2024-02-05
The list of security fixes that are included in this release is documented in the following advisory:
If you have installed the Red Hat OpenShift GitOps Operator, view the container images in this release by running the following command:
oc describe deployment gitops-operator-controller-manager -n openshift-operators
$ oc describe deployment gitops-operator-controller-manager -n openshift-operators
1.4. Release notes for Red Hat OpenShift GitOps 1.9.3 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.9.3 is now available on OpenShift Container Platform 4.12, 4.13, and 4.14.
1.4.1. Errata updates Copier lienLien copié sur presse-papiers!
1.4.1.1. RHSA-2023:7345 - Red Hat OpenShift GitOps 1.9.3 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-11-20
The list of security fixes that are included in this release is documented in the following advisory:
If you have installed the Red Hat OpenShift GitOps Operator in the default namespace, to view the container images in this release, run the following command:
oc describe deployment gitops-operator-controller-manager -n openshift-gitops-operator
$ oc describe deployment gitops-operator-controller-manager -n openshift-gitops-operator
1.5. Release notes for Red Hat OpenShift GitOps 1.9.2 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.9.2 is now available on OpenShift Container Platform 4.12 and 4.13.
1.5.1. Errata updates Copier lienLien copié sur presse-papiers!
1.5.1.1. RHSA-2023:5029 - Red Hat OpenShift GitOps 1.9.2 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-09-08
The list of security fixes that are included in this release is documented in the following advisory:
If you have installed the Red Hat OpenShift GitOps Operator, run the following command to view the container images in this release:
oc describe deployment gitops-operator-controller-manager -n openshift-operators
$ oc describe deployment gitops-operator-controller-manager -n openshift-operators
1.5.2. Fixed issues Copier lienLien copié sur presse-papiers!
The following issue has been resolved in the current release:
-
Before this update, an old Redis image version was used when deploying the Red Hat OpenShift GitOps Operator, which resulted in vulnerabilities. This update fixes the vulnerabilities on Redis by upgrading it to the latest version of the
registry.redhat.io/rhel-8/redis-6
image. GITOPS-3069
1.6. Release notes for Red Hat OpenShift GitOps 1.9.1 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.9.1 is now available on OpenShift Container Platform 4.12 and 4.13.
1.6.1. Errata updates Copier lienLien copié sur presse-papiers!
1.6.1.1. RHSA-2023:3591 and RHBA-2023:4117 - Red Hat OpenShift GitOps 1.9.1 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-07-17
The list of security fixes that are included in this release is documented in the following advisories:
If you have installed the Red Hat OpenShift GitOps Operator, run the following command to view the container images in this release:
oc describe deployment gitops-operator-controller-manager -n openshift-operators
$ oc describe deployment gitops-operator-controller-manager -n openshift-operators
1.6.2. New features Copier lienLien copié sur presse-papiers!
The current release adds the following improvements:
- With this update, the bundled Argo CD has been updated to version 2.7.6.
1.6.3. Fixed issues Copier lienLien copié sur presse-papiers!
The following issues have been resolved in the current release:
- Before this update, Argo CD was becoming unresponsive when there was an increase in namespaces and applications. This update fixes the issue by removing a deadlock. Deadlock occurs when two functions are competing for resources. Now, you should not experience crashes or unresponsiveness when there is an increase in namespaces or applications. GITOPS-2782
- Before this update, the Argo CD application controller resource could suddenly stop working when resynchronizing applications. This update fixes the issue by adding logic to prevent a cluster cache deadlock. Now, you should not experience the deadlock situation, and applications should resynchronize successfully. GITOPS-2880
-
Before this update, there was a mismatch in the RSA key for known hosts in the
argocd-ssh-known-hosts-cm
config map. This update fixes the issue by matching the RSA key with the upstream project. Now, you can use the default RSA keys on default deployments. GITOPS-3042 -
Before this update, the reconciliation timeout setting in the
argocd-cm
config map was not being correctly applied to the Argo CD application controller resource. This update fixes the issue by correctly reading and applying the reconciliation timeout setting from theargocd-cm
config map. Now, you can modify the reconciliation timeout value from theAppSync
setting without a problem. GITOPS-2810
1.7. Release notes for Red Hat OpenShift GitOps 1.9.0 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.9.0 is now available on OpenShift Container Platform 4.12 and 4.13.
1.7.1. Errata updates Copier lienLien copié sur presse-papiers!
1.7.1.1. RHSA-2023:3557 - Red Hat OpenShift GitOps 1.9.0 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-06-09
The list of security fixes that are included in this release is documented in the following advisory:
If you have installed the Red Hat OpenShift GitOps Operator, run the following command to view the container images in this release:
oc describe deployment gitops-operator-controller-manager -n openshift-operators
$ oc describe deployment gitops-operator-controller-manager -n openshift-operators
1.7.2. New features Copier lienLien copié sur presse-papiers!
The current release adds the following improvements:
With this update, you can use a custom
must-gather
tool to collect diagnostic information for project-level resources, cluster-level resources, and Red Hat OpenShift GitOps components. This tool provides the debugging information about the cluster associated with Red Hat OpenShift GitOps, which you can share with the Red Hat Support team for analysis. GITOPS-2797ImportantThe custom
must-gather
tool is a Technology Preview feature.With this update, you can add support to progressive delivery using Argo Rollouts. Currently, the supported traffic manager is only Red Hat OpenShift Service Mesh. GITOPS-959
ImportantArgo Rollouts is a Technology Preview feature.
1.7.3. Deprecated and removed features Copier lienLien copié sur presse-papiers!
-
In Red Hat OpenShift GitOps 1.7.0, the
.spec.resourceCustomizations
parameter was deprecated. The deprecated.spec.resourceCustomizations
parameter is planned to be removed in the upcoming Red Hat OpenShift GitOps GA v1.10.0 release. You can use the new formatsspec.ResourceHealthChecks
,spec.ResourceIgnoreDifferences
, andspec.ResourceActions
instead. GITOPS-2890 With this update, the support for the following deprecated
sso
anddex
fields extends until the upcoming Red Hat OpenShift GitOps GA v1.10.0 release:-
The
.spec.sso.image
,.spec.sso.version
,.spec.sso.resources
, and.spec.sso.verifyTLS
fields. The
.spec.dex
parameter along withDISABLE_DEX
.The deprecated previous
sso
anddex
fields were earlier scheduled for removal in the Red Hat OpenShift GitOps v1.9.0 release but are now planned to be removed in the upcoming Red Hat OpenShift GitOps GA v1.10.0 release. GITOPS-2904
-
The
1.7.4. Fixed issues Copier lienLien copié sur presse-papiers!
The following issues have been resolved in the current release:
-
Before this update, when the
argocd-server-tls
secret was updated with a new certificate Argo CD was not always picking up this secret. As a result, the old expired certificate was presented. This update fixes the issue with a newGetCertificate
function and ensures that the latest version of certificates is in use. When adding new certificates, now Argo CD picks them up automatically without the user having to restart theargocd-server
pod. GITOPS-2375 -
Before this update, when enforcing GPG signature verification against a
targetRevision
integer pointing to a signed Git tag, users got aTarget revision in Git is not signed
error. This update fixes the issue and lets users enforce GPG signature verification against signed Git tags. GITOPS-2418 - Before this update, users could not connect to Microsoft Team Foundation Server (TFS) type Git repositories through Argo CD deployed by the Operator. This update fixes the issue by updating the Git version to 2.39.3 in the Operator. GITOPS-2768
-
Before this update, when the Operator was deployed and running with the High availability (HA) feature enabled, setting resource limits under the
.spec.ha.resources
field did not affect Redis HA pods. This update fixes the reconciliation by adding checks in the Redis reconciliation code. These checks ensure whether thespec.ha.resources
field in the Argo CD custom resource (CR) is updated. When the Argo CD CR is updated with new CPU and memory requests or limit values for HA, now these changes are applied to the Redis HA pods. GITOPS-2404 -
Before this update, if a namespace-scoped Argo CD instance was managing multiple namespaces by using the
managed-by
label and one of those managed namespaces was in a Terminating state, the Argo CD instance could not deploy resources to all other managed namespaces. This update fixes the issue by enabling the Operator to remove themanaged-by
label from any previously managed now terminating namespace. Now, a terminating namespace managed by a namespace-scoped Argo CD instance does not block the deployment of resources to other managed namespaces. GITOPS-2627
1.7.5. Known issues Copier lienLien copié sur presse-papiers!
Currently, the Argo CD does not read the Transport Layer Security (TLS) certificates from the path specified in the
argocd-tls-certs-cm
config map resulting in thex509: certificate signed by unknown authority
error.Workaround: Perform the following steps:
Add the
SSL_CERT_DIR
environment variable:Example Argo CD custom resource
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create an empty config map in the namespace where the subscription for your Operator exists and include the following label:
Example config map
Copy to Clipboard Copied! Toggle word wrap Toggle overflow After creating this config map, the
user-ca-bundle
content from theopenshift-config
namespace automatically gets injected into this config map, even merged with the system ca-bundle. GITOPS-1482
1.8. Release notes for Red Hat OpenShift GitOps 1.8.6 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.8.6 is now available on OpenShift Container Platform 4.10, 4.11, 4.12, and 4.13.
1.8.1. Errata updates Copier lienLien copié sur presse-papiers!
1.8.1.1. RHSA-2023:6788 - Red Hat OpenShift GitOps 1.8.6 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-11-08
The list of security fixes that are included in this release is documented in the following advisory:
If you have installed the Red Hat OpenShift GitOps Operator in the default namespace, run the following command to view the container images in this release:
oc describe deployment gitops-operator-controller-manager -n openshift-gitops-operator
$ oc describe deployment gitops-operator-controller-manager -n openshift-gitops-operator
1.9. Release notes for Red Hat OpenShift GitOps 1.8.5 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.8.5 is now available on OpenShift Container Platform 4.10, 4.11, 4.12, and 4.13.
1.9.1. Errata updates Copier lienLien copié sur presse-papiers!
1.9.1.1. RHSA-2023:5030 - Red Hat OpenShift GitOps 1.8.5 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-09-08
The list of security fixes that are included in this release is documented in the following advisory:
If you have installed the Red Hat OpenShift GitOps Operator, run the following command to view the container images in this release:
oc describe deployment gitops-operator-controller-manager -n openshift-operators
$ oc describe deployment gitops-operator-controller-manager -n openshift-operators
1.9.2. Fixed issues Copier lienLien copié sur presse-papiers!
The following issue has been resolved in the current release:
-
Before this update, there was a mismatch in the RSA key for known hosts in the
argocd-ssh-known-hosts-cm
config map. This update fixes the issue by matching the RSA key with the upstream project. Now, you can use the default RSA keys on default deployments. GITOPS-3248
1.10. Release notes for Red Hat OpenShift GitOps 1.8.4 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.8.4 is now available on OpenShift Container Platform 4.10, 4.11, 4.12, and 4.13.
1.10.1. New features Copier lienLien copié sur presse-papiers!
The current release adds the following improvements:
- With this update, the bundled Argo CD has been updated to version 2.6.13.
1.10.2. Fixed issues Copier lienLien copié sur presse-papiers!
The following issues have been resolved in the current release:
- Before this update, Argo CD was becoming unresponsive when there was an increase in namespaces and applications. The functions competing for resources caused a deadlock. This update fixes the issue by removing the deadlock. Now, you should not experience crashes or unresponsiveness when there is an increase in namespaces or applications. GITOPS-3192
- Before this update, the Argo CD application controller resource could suddenly stop working when resynchronizing applications. This update fixes the issue by adding logic to prevent a cluster cache deadlock. Now, applications should resynchronize successfully. GITOPS-3052
-
Before this update, there was a mismatch in the RSA key for known hosts in the
argocd-ssh-known-hosts-cm
config map. This update fixes the issue by matching the RSA key with the upstream project. Now, you can use the default RSA keys on default deployments. GITOPS-3144 -
Before this update, an old Redis image version was used when deploying the Red Hat OpenShift GitOps Operator, which resulted in vulnerabilities. This update fixes the vulnerabilities on Redis by upgrading it to the latest version of the
registry.redhat.io/rhel-8/redis-6
image. GITOPS-3069 -
Before this update, users could not connect to Microsoft Team Foundation Server (TFS) type Git repositories through Argo CD deployed by the Operator. This update fixes the issue by updating the Git version to 2.39.3 in the Operator. Now, you can set the
Force HTTP basic auth
flag during repository configurations to connect with the TFS type Git repositories. GITOPS-1315
1.10.3. Known issues Copier lienLien copié sur presse-papiers!
Currently, Red Hat OpenShift GitOps 1.8.4 is not available in the
latest
channel of OpenShift Container Platform 4.10 and 4.11. Thelatest
channel is taken by GitOps 1.9.z, which is only released on OpenShift Container Platform 4.12 and later versions.As a workaround, switch to the
gitops-1.8
channel to get the new update. GITOPS-3158
1.11. Release notes for Red Hat OpenShift GitOps 1.8.3 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.8.3 is now available on OpenShift Container Platform 4.10, 4.11, 4.12, and 4.13.
1.11.1. Errata updates Copier lienLien copié sur presse-papiers!
1.11.1.1. RHBA-2023:3206 and RHSA-2023:3229 - Red Hat OpenShift GitOps 1.8.3 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-05-18
The list of security fixes that are included in this release is documented in the following advisories:
If you have installed the Red Hat OpenShift GitOps Operator, run the following command to view the container images in this release:
oc describe deployment gitops-operator-controller-manager -n openshift-operators
$ oc describe deployment gitops-operator-controller-manager -n openshift-operators
1.11.2. Fixed issues Copier lienLien copié sur presse-papiers!
-
Before this update, when
Autoscale
was enabled and the horizontal pod autoscaler (HPA) controller tried to edit the replica settings in server deployment, the Operator overwrote it. In addition, any changes specified to the autoscaler parameters were not propagated correctly to the HPA on the cluster. This update fixes the issue. Now the Operator reconciles on replica drift only ifAutoscale
is disabled and the HPA parameters are updated correctly. GITOPS-2629
1.12. Release notes for Red Hat OpenShift GitOps 1.8.2 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.8.2 is now available on OpenShift Container Platform 4.10, 4.11, 4.12, and 4.13.
1.12.1. Fixed issues Copier lienLien copié sur presse-papiers!
The following issues have been resolved in the current release:
Before this update, when you configured Dex using the
.spec.dex
parameter and tried to log in to the Argo CD UI by using the LOG IN VIA OPENSHIFT option, you were not able to log in. This update fixes the issue.ImportantThe
spec.dex
parameter in the ArgoCD CR is deprecated. In a future release of Red Hat OpenShift GitOps v1.9, configuring Dex using thespec.dex
parameter in the ArgoCD CR is planned to be removed. Consider using the.spec.sso
parameter instead. See "Enabling or disabling Dex using .spec.sso". GITOPS-2761-
Before this update, the cluster and
kam
CLI pods failed to start with a new installation of Red Hat OpenShift GitOps v1.8.0 on the OpenShift Container Platform 4.10 cluster. This update fixes the issue and now all pods run as expected. GITOPS-2762
1.13. Release notes for Red Hat OpenShift GitOps 1.8.1 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.8.1 is now available on OpenShift Container Platform 4.10, 4.11, 4.12, and 4.13.
1.13.1. Errata updates Copier lienLien copié sur presse-papiers!
1.13.1.1. RHSA-2023:1452 - Red Hat OpenShift GitOps 1.8.1 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-03-23
The list of security fixes that are included in this release is documented in the RHSA-2023:1452 advisory.
If you have installed the Red Hat OpenShift GitOps Operator, run the following command to view the container images in this release:
oc describe deployment gitops-operator-controller-manager -n openshift-operators
$ oc describe deployment gitops-operator-controller-manager -n openshift-operators
1.14. Release notes for Red Hat OpenShift GitOps 1.8.0 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.8.0 is now available on OpenShift Container Platform 4.10, 4.11, 4.12, and 4.13.
1.14.1. New features Copier lienLien copié sur presse-papiers!
The current release adds the following improvements:
With this update, you can add support for the ApplicationSet Progressive Rollout Strategy feature. Using this feature, you can enhance the ArgoCD ApplicationSet resource to embed a rollout strategy for a progressive application resource update after you modify the ApplicationSet spec or Application templates. When you enable this feature, applications are updated in a declarative order instead of simultaneously. GITOPS-956
ImportantApplicationSet Progressive Rollout Strategy is a Technology Preview feature.
-
With this update, the Application environments page in the Developer perspective of the OpenShift Container Platform web console is decoupled from the Red Hat OpenShift GitOps Application Manager command-line interface (CLI),
kam
. You do not have to use thekam
CLI to generate Application Environment manifests for the environments to show up in the Developer perspective of the OpenShift Container Platform web console. You can use your own manifests, but the environments must still be represented by namespaces. In addition, specific labels and annotations are still needed. GITOPS-1785 With this update, the Red Hat OpenShift GitOps Operator and the
kam
CLI are now available to use on ARM architecture on OpenShift Container Platform. GITOPS-1688Importantspec.sso.provider: keycloak
is not yet supported on ARM.-
With this update, you can enable workload monitoring for specific Argo CD instances by setting the
.spec.monitoring.enabled
flag value totrue
. As a result, the Operator creates aPrometheusRule
object that contains alert rules for each Argo CD component. These alert rules trigger an alert when the replica count of the corresponding component has drifted from the desired state for a certain amount of time. The Operator will not overwrite the changes made to thePrometheusRule
object by the users. GITOPS-2459 With this update, you can pass command arguments to the repo server deployment using the Argo CD CR. GITOPS-2445
For example:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
1.14.2. Fixed issues Copier lienLien copié sur presse-papiers!
The following issues have been resolved in the current release:
Before this update, you could set the
ARGOCD_GIT_MODULES_ENABLED
environment variable only on theopenshift-gitops-repo-server
pod and not on theApplicationSet Controller
pod. As a result, when using the Git generator, Git submodules were cloned during the generation of child applications because the variable was missing from theApplicationSet Controller
environment. In addition, if the credentials required to clone these submodules were not configured in ArgoCD, the application generation failed. This update fixes the issue; you can now add any environment variables such asArgoCD_GIT_MODULES_ENABLED
to theApplicationSet Controller
pod using the Argo CD CR. TheApplicationSet Controller
pod then successfully generates child applications from the cloned repository and no submodule is cloned in the process. GITOPS-2399For example:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Before this update, while installing the Red Hat OpenShift GitOps Operator v1.7.0, the default
argocd-cm.yml
config map file created for authenticating Dex contained the base64-encoded client secret in the format of akey:value
pair. This update fixes this issue by not storing the client secret in the defaultargocd-cm.yml
config map file. Instead, the client secret is inside anargocd-secret
object now, and you can reference it inside the configuration map as a secret name. GITOPS-2570
1.14.3. Known issues Copier lienLien copié sur presse-papiers!
-
When you deploy applications using your manifests without using the
kam
CLI and view the applications in the Application environments page in the Developer perspective of the OpenShift Container Platform web console, the Argo CD URL to the corresponding application does not load the page as expected from the Argo CD icon in the card. GITOPS-2736
1.15. Release notes for Red Hat OpenShift GitOps 1.7.4 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.7.4 is now available on OpenShift Container Platform 4.10, 4.11, and 4.12.
1.15.1. Errata updates Copier lienLien copié sur presse-papiers!
1.15.1.1. RHSA-2023:1454 - Red Hat OpenShift GitOps 1.7.4 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-03-23
The list of security fixes that are included in this release is documented in the RHSA-2023:1454 advisory.
If you have installed the Red Hat OpenShift GitOps Operator, run the following command to view the container images in this release:
oc describe deployment gitops-operator-controller-manager -n openshift-operators
$ oc describe deployment gitops-operator-controller-manager -n openshift-operators
1.16. Release notes for Red Hat OpenShift GitOps 1.7.3 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.7.3 is now available on OpenShift Container Platform 4.10, 4.11, and 4.12.
1.16.1. Errata updates Copier lienLien copié sur presse-papiers!
1.16.1.1. RHSA-2023:1454 - Red Hat OpenShift GitOps 1.7.3 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-03-23
The list of security fixes that are included in this release is documented in the RHSA-2023:1454 advisory.
If you have installed the Red Hat OpenShift GitOps Operator, run the following command to view the container images in this release:
oc describe deployment gitops-operator-controller-manager -n openshift-operators
$ oc describe deployment gitops-operator-controller-manager -n openshift-operators
1.17. Release notes for Red Hat OpenShift GitOps 1.7.1 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.7.1 is now available on OpenShift Container Platform 4.10, 4.11, and 4.12.
1.17.1. Errata updates Copier lienLien copié sur presse-papiers!
1.17.1.1. RHSA-2023:0467 - Red Hat OpenShift GitOps 1.7.1 security update advisory Copier lienLien copié sur presse-papiers!
Issued: 2023-01-25
The list of security fixes that are included in this release is documented in the RHSA-2023:0467 advisory.
If you have installed the Red Hat OpenShift GitOps Operator, run the following command to view the container images in this release:
oc describe deployment gitops-operator-controller-manager -n openshift-operators
$ oc describe deployment gitops-operator-controller-manager -n openshift-operators
1.18. Release notes for Red Hat OpenShift GitOps 1.7.0 Copier lienLien copié sur presse-papiers!
Red Hat OpenShift GitOps 1.7.0 is now available on OpenShift Container Platform 4.10, 4.11, and 4.12.
1.18.1. New features Copier lienLien copié sur presse-papiers!
The current release adds the following improvements:
- With this update, you can add environment variables to the Notifications controller. GITOPS-2313
-
With this update, the default nodeSelector
"kubernetes.io/os": "linux"
key-value pair is added to all workloads such that they only schedule on Linux nodes. In addition, any custom node selectors are added to the default and take precedence if they have the same key. GITOPS-2215 -
With this update, you can set custom node selectors in the Operator workloads by editing their
GitopsService
custom resource. GITOPS-2164 -
With this update, you can use the RBAC policy matcher mode to select from the following options:
glob
(default) andregex
.GITOPS-1975 With this update, you can customize resource behavior using the following additional subkeys:
Expand Subkey Key form Mapped field in argocd-cm resourceHealthChecks
resource.customizations.health.<group_kind>
resource.customizations.health
resourceIgnoreDifferences
resource.customizations.ignoreDifferences.<group_kind>
resource.customizations.ignoreDifferences
resourceActions
resource.customizations.actions.<group_kind>
resource.customizations.actions
NoteIn future releases, there is a possibility to deprecate the old method of customizing resource behavior by using only resourceCustomization and not subkeys.
- With this update, to use the Environments page in the Developer perspective, you must upgrade if you are using a Red Hat OpenShift GitOps version prior to 1.7 and OpenShift Container Platform 4.15 or above. GITOPS-2415
With this update, you can create applications, which are managed by the same control plane Argo CD instance, in any namespace in the same cluster. As an administrator, perform the following actions to enable this update:
-
Add the namespace to the
.spec.sourceNamespaces
attribute for a cluster-scoped Argo CD instance that manages the application. Add the namespace to the
.spec.sourceNamespaces
attribute in theAppProject
custom resource that is associated with the application.
-
Add the namespace to the
Argo CD applications in non-control plane namespaces is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
With this update, Argo CD supports the Server-Side Apply feature, which helps users to perform the following tasks:
- Manage large resources which are too big for the allowed annotation size of 262144 bytes.
Patch an existing resource that is not managed or deployed by Argo CD.
You can configure this feature at application or resource level. GITOPS-2340
1.18.2. Fixed issues Copier lienLien copié sur presse-papiers!
The following issues have been resolved in the current release:
-
Before this update, Red Hat OpenShift GitOps releases were affected by an issue of Dex pods failing with
CreateContainerConfigError
error when theanyuid
SCC was assigned to the Dex service account. This update fixes the issue by assigning a default user id to the Dex container. GITOPS-2235 -
Before this update, Red Hat OpenShift GitOps used the RHSSO (Keycloak) through OIDC in addition to Dex. However, with a recent security fix, the certificate of RHSSO could not be validated when configured with a certificate not signed by one of the well-known certificate authorities. This update fixes the issue; you can now provide a custom certificate to verify the KeyCloak’s TLS certificate while communicating with it. In addition, you can add
rootCA
to the Argo CD custom resource.spec.keycloak.rootCA
field. The Operator reconciles such changes and updates theoidc.config in argocd-cm
config map with the PEM encoded root certificate. GITOPS-2214
Example Argo CD with Keycloak configuration:
-
Before this update, the application controllers restarted multiple times due to the unresponsiveness of liveness probes. This update fixes the issue by removing the liveness probe in the
statefulset
application controller. GITOPS-2153
1.18.3. Known issues Copier lienLien copié sur presse-papiers!
-
Before this update, the Operator did not reconcile the
mountsatoken
andServiceAccount
settings for the repository server. While this has been fixed, deletion of the service account does not revert to the default. GITOPS-1873 -
Workaround: Manually set the
spec.repo.serviceaccountfield to thedefault
service account. GITOPS-2452