You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dev/release.md
+46Lines changed: 46 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,6 +195,52 @@ git push
195
195
196
196
If the release is a new minor version, then the CLI must be updated with the new version (and any new CRDs) [here](https://github.com/mongodb/mongodb-atlas-cli/blob/master/internal/kubernetes/operator/features/crds.go).
197
197
198
+
# Updating the ROSA cluster
199
+
200
+
For the Openshift upgrade tests we rely on a service account to be present in the OpenShift cluster and its login token to be present in CI.
201
+
202
+
## Setup Kubectl against the new cluster
203
+
204
+
1. Go to https://console.redhat.com/openshift
205
+
1. Use your RedHat account credentials to log in, see Pre-requisites on the RedHat Connect account you need to setup before this.
206
+
1. Form the list of Clusters, click of the name of the one to be used now.
207
+
1. CLick the `Open Console` in the top right of the page.
208
+
1. Use the cluster `htpasswd` credentials you should have been given beforehand to login to the cluster itself.
209
+
1. On the landing page, click the account drop down on the top right corner if the page and click on `Copy login command` there.
210
+
1. Login again with the `htpasswd`credentials.
211
+
1. On the white page click `Display token`.
212
+
1. Copy the `oc` command there and run it. You need to have [oc installed](https://docs.openshift.com/container-platform/4.8/cli_reference/openshift_cli/getting-started-cli.html) for this step to work.
213
+
214
+
After that if you do `kubectl config current-context` it should display you are connected to your new cluster.
215
+
216
+
## Create the cluster managing service account
217
+
218
+
Using the kubectl context against the new cluster, create the service account and its token:
0 commit comments