Skip to content
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

Add step in new minor how-to to create tickets for OpenShift changes which may impact user workloads #280

Merged
merged 1 commit into from
Oct 11, 2023
Merged

Add step in new minor how-to to create tickets for OpenShift changes which may impact user workloads #280

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
13 changes: 13 additions & 0 deletions docs/modules/ROOT/pages/how-tos/new_minor.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,19 @@ Additionally, verify that alert rules defined by other components are still pick
+
For example, we needed to update component `resource-locker` to explicitly create ServiceAccount token secrets for OpenShift 4.11 / Kubernetes 1.24.

. If there's changes with a potential impact on customer workloads (for example the switch to `cgroupv2` as default in OCP 4.13), create a ticket to research these changes.
The minimum amount of research for such a change should be to search the internet for `<feature> problems` or `<feature> issues` (or similar) and note any issues that other people have talked about.
The research ticket should have roughly the following acceptance criteria:
+
[source]
----
* We understand the impact of rolling out the change
* We understand how the change may impact customer workload
* The impact of the change is highlighted in the release notes created as part of step 1
* Follow-up tickets for the rollout are refined and estimated
** Per-customer tickets are created, if we believe it's necessary to inform customers ahead of the rollout
----

. Upgrade to a supported OpenShift Cluster Logging version on the upgraded cluster
+
TIP: Usually you'll want to upgrade to the latest OpenShift Cluster Logging version.
Expand Down