Skip to content

Commit b77bdd1

Browse files
wtam2018wtam2018
committed
add gitops v1.2 release notes.
1 parent 9852675 commit b77bdd1

File tree

2 files changed

+135
-0
lines changed

2 files changed

+135
-0
lines changed

‎cicd/gitops/gitops-release-notes.adoc‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,4 +23,6 @@ For an overview of {gitops-title}, see xref:../../cicd/gitops/understanding-open
2323
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 link:https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language[Red Hat CTO Chris Wright's message].
2424

2525
// Modules included, most to least recent
26+
include::modules/gitops-release-notes-1-2.adoc[leveloffset=+1]
27+
2628
include::modules/gitops-release-notes-1-1.adoc[leveloffset=+1]

‎modules/gitops-release-notes-1-2.adoc‎

Lines changed: 133 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,133 @@
1+
// Module included in the following assembly:
2+
//
3+
// * gitops/gitops-release-notes.adoc
4+
5+
[id="gitops-release-notes-1-2_{context}"]
6+
= Release notes for {gitops-title} 1.2
7+
8+
{gitops-title} 1.2 is now available on {product-title} 4.7 and 4.8.
9+
10+
[id="support-matrix-1-2_{context}"]
11+
== Support matrix
12+
13+
Some features in this release are currently in Technology Preview. These experimental features are not intended for production use.
14+
15+
link:https://access.redhat.com/support/offerings/techpreview[Technology Preview Features Support Scope]
16+
17+
In the table below, features are marked with the following statuses:
18+
19+
- *TP*: _Technology Preview_
20+
21+
- *GA*: _General Availability_
22+
23+
Note the following scope of support on the Red Hat Customer Portal for these features:
24+
25+
.Support matrix
26+
[cols="1,1",options="header"]
27+
|===
28+
| Feature | {gitops-title} 1.2
29+
| Argo CD
30+
| GA
31+
| Argo CD ApplicationSet
32+
| TP
33+
| {gitops-title} Application Manager (kam)
34+
| TP
35+
| {gitops-title} Service
36+
| TP
37+
|===
38+
39+
[id="new-features-1-2_{context}"]
40+
== New features
41+
In addition to the fixes and stability improvements, the following sections highlight what is new in {gitops-title} 1.2:
42+
43+
* If you do not have read or write access to the openshift-gitops namespace, you can now use the `DISABLE_DEFAULT_ARGOCD_INSTANCE` environment variable in the GitOps Operator and set the value to `TRUE` to prevent the default Argo CD instance from starting in the `openshift-gitops` namespace.
44+
* Resource requests and limits are now configured in Argo CD workloads. Resource quota is enabled in the `openshift-gitops` namespace. As a result, out-of-band workloads deployed manually in the openshift-gitops namespace must be configured with resource requests and limits and the resource quota may need to be increased.
45+
* Argo CD authentication is now integrated with Red Hat SSO and it is automatically configured with OpenShift 4 Identity Provider on the cluster. This feature is disabled by default. To enable Red Hat SSO, add SSO configuration in `ArgoCD` CR as shown below. Currently,`keycloak` is the only supported provider.
46+
47+
+
48+
[source,yaml]
49+
----
50+
apiVersion: argoproj.io/v1alpha1
51+
kind: ArgoCD
52+
metadata:
53+
name: example-argocd
54+
labels:
55+
example: basic
56+
spec:
57+
sso:
58+
provider: keycloak
59+
server:
60+
route:
61+
enabled: true
62+
----
63+
* You can now define hostnames using route labels to support router sharding. Support for setting labels on the `server` (argocd server), `grafana`, and `prometheus` routes is now available. To set labels on a route, add `labels` under the route configuration for a server in the `ArgoCD` CR.
64+
+
65+
.Example `ArgoCD` CR YAML to set labels on argocd server
66+
[source,yaml]
67+
----
68+
apiVersion: argoproj.io/v1alpha1
69+
kind: ArgoCD
70+
metadata:
71+
name: example-argocd
72+
labels:
73+
example: basic
74+
spec:
75+
server:
76+
route:
77+
enabled: true
78+
labels:
79+
key1: value1
80+
key2: value2
81+
----
82+
* The GitOps Operator now automatically grants permissions to Argo CD instances to manage resources in target namespaces by applying labels. Users can label the target namespace with the label `argocd.argoproj.io/managed-by: <source-namespace>`, where the `source-namespace` is the namespace where the argocd instance is deployed.
83+
84+
[id="fixed-issues-1-2_{context}"]
85+
== Fixed issues
86+
The following issues were resolved in the current release:
87+
88+
* Previously, if a user created additional instances of Argo CD managed by the default cluster instance in the openshift-gitops namespace, the application responsible for the new Argo CD instance would get stuck in an `OutOfSync` status. This issue has now been resolved by adding an owner reference to the cluster secret. link:https://issues.redhat.com/browse/GITOPS-1025[GITOPS-1025]
89+
90+
[id="known-issues-1-2_{context}"]
91+
== Known issues
92+
These are the known issues in {gitops-title} 1.2:
93+
94+
* When an Argo CD instance is deleted from the source namespace, the `argocd.argoproj.io/managed-by` labels in the target namespaces are not removed. link:https://issues.redhat.com/browse/GITOPS-1228[GITOPS-1228]
95+
96+
* Resource quota has been enabled in the openshift-gitops namespace in {gitops-title} 1.2. This can affect out-of-band workloads deployed manually and workloads deployed by the default Argo CD instance in the `openshift-gitops` namespace. When you upgrade from {gitops-title} `v1.1.2` to `v1.2` such workloads must be configured with resource requests and limits. If there are any additional workloads, the resource quota in the openshift-gitops namespace must be increased.
97+
98+
+
99+
Current Resource Quota for `openshift-gitops` namespace.
100+
+
101+
[cols="1,1,1",options="header"]
102+
|===
103+
| *Resource* | *Requests* | *Limits*
104+
105+
| CPU
106+
| 6688m
107+
| 13750m
108+
109+
| Memory
110+
| 4544Mi
111+
| 9070Mi
112+
113+
|===
114+
+
115+
You can use the below command to update the CPU limits.
116+
+
117+
[source,terminal]
118+
----
119+
$ oc patch resourcequota openshift-gitops-compute-resources -n openshift-gitops --type='json' -p='[{"op": "replace", "path": "/spec/hard/limits.cpu", "value":"9000m"}]'
120+
----
121+
+
122+
You can use the below command to update the CPU requests.
123+
+
124+
[source,terminal]
125+
----
126+
$ oc patch resourcequota openshift-gitops-compute-resources -n openshift-gitops --type='json' -p='[{"op": "replace", "path": "/spec/hard/cpu", "value":"7000m"}]
127+
----
128+
+
129+
You can replace the path in the above commands from `cpu` to `memory` to update the memory.
130+
131+
132+
133+

0 commit comments

Comments
 (0)