-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Add a Mechanism to Label all Pods in the Control Plane Namespace
-
BU Product Work
-
False
-
None
-
False
-
OCPSTRAT-1657 - Add a Mechanism to Label all Pods for a Hosted Cluster in the Control Plane Namespace
-
-
75% To Do, 25% In Progress, 0% Done
-
S
-
8
-
8
-
0
-
0
-
Backlog Refinement
Goal
- Hypershift has a mechanism for Labeling Control Plane Pods
- Cluster service should be able to set the label for a given hosted cluster
Why is this important?
- As part of being a first party Azure offering, ARO HCP needs to adhere to Microsoft secure supply chain software requirements. In order to do this, we require setting a label on all pods that run in the hosted cluster namespace.
See Documentation: https://eng.ms/docs/more/containers-secure-supply-chain/other
Scenarios
- Given a subscriptionID of "1d3378d3-5a3f-4712-85a1-2485495dfc4b", there needs to be the following label on all pods hosted on behalf of the customer:
kubernetes.azure.com/managedby: sub_1d3378d3-5a3f-4712-85a1-2485495dfc4b
Acceptance Criteria
- Dev - Has a valid enhancement if necessary
- CI - MUST be running successfully with tests automated
- QE - covered in Polarion test plan and tests implemented
- Release Technical Enablement - Must have TE slides
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Technical Enablement <link to Feature Enablement Presentation>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Enhancement merged: <link to meaningful PR or GitHub Issue>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
- is blocked by
-
HOSTEDCP-1801 Refactor CPO
-
- Closed
-
