-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.13, 4.12, 4.11, 4.14, 4.15
-
Critical
-
No
-
3
-
OTA 241, OTA 242
-
2
-
Proposed
-
False
-
-
Release Note Not Required
-
In Progress
How reproducible:
Always
Steps to Reproduce:
1. the Kubernetes API introduces a new Pod Template parameter (`ephemeral`) 2. this parameter is not in the allowed list of the default SCC 3. customer is not allowed to edit the default SCCs nor we have a mechanism in place to update the built in SCCs AFAIK 4. users of existing clusters cannot use the new parameter without creating manual SCCs and assigning this SCC to service accounts themselves which looks clunky. This is documented in https://access.redhat.com/articles/6967808
Actual results:
Users of existing clusters cannot use ephemeral volumes after an upgrade
Expected results:
Users of existing clusters *can* use ephemeral volumes after an upgrade
Current status
- blocks
-
OCPBUGS-19465 Cluster Version Operator does not correctly reconcile SCC resources
- Closed
- is cloned by
-
OCPBUGS-19465 Cluster Version Operator does not correctly reconcile SCC resources
- Closed
- links to
-
RHEA-2023:7198 rpm