-
Story
-
Resolution: Done
-
Undefined
-
ACM 2.11.0
Value Statement
The IAM Policy Controller has been deprecated since ACM 2.9 and can now be removed for 2.11+.
Definition of Done for Engineering Story Owner (Checklist)
- The governance-policy-addon-controller no longer deploys the IAM policy controller.
- Ensure that the governance-policy-addon-controller removes the existing ManifestWork deploying the IAM policy controller. This should lead to the IAM policy controller being removed.
- Modify the governance-policy-framework-addon's template-sync controller to send a template error compliance event stating it is no longer supported. Confirm with docs on the message.
- Remove the release-2.11 and main branches on the github.com/stolostron/iam-policy-controller and set the default branch to release-2.10. Ensure the Prow configuration for these branches is removed.
- Ensure the branching script is updated to not reference the IAM policy controller repo. Other scripts will also apply. Reach out to dhaiduce for a list.
- Remove the IAM policy templates in the console.
- Remove IAM policies from policy-collection.
- Remove the governance-policy-framework (integration) tests related to IAM.
- Make sure the ClusterManagementAddOn is no longer created for IAM policy controller. Probably in the klusterlet-addon-controller (or something similar).
- Notify HYPBLD team that we are decomisioning it.
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the [Customer
Portal_doc_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.