-
Bug
-
Resolution: Unresolved
-
Minor
-
4.15.0
-
No
-
5
-
OSDOCS Sprint 250, OSDOCS Sprint 251, OSDOCS Sprint 257, OSDOCS Sprint 258, OSDOCS Sprint 259, OSDOCS Sprint 260, OSDOCS Sprint 261, OSDOCS Sprint 262
-
8
-
False
-
-
N/A
-
Release Note Not Required
Description of problem:
In 4.6, we wanted to drop some default capabilities from the capability set to better secure the platform. However, we didn't want to break existing workloads on upgrade. We came up with a solution where we'd create an MC on upgrade that would add the old default capabilities: https://github.com/openshift/machine-config-operator/pull/2050. However, it seems we never really documented we did that. There were a couple of other similar changes https://github.com/openshift/machine-config-operator/pull/3352 and https://github.com/openshift/machine-config-operator/pull/3563
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Check documentation 2. 3.
Actual results:
we don't mention we've done this with machine configs on changes that potentially risk upgrades
Expected results:
we should mention them
Additional info:
