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.

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

Update ACS PolicySet to replace expired init-bundle #439

Conversation

brian-jarvis
Copy link
Contributor

Updates to existing stable ACS PolicySet for OpenShift+ includes:

  • Replacing Job with v2 as Job definition is immutable. Removes original Job if it exists
  • Creating policy to remove init-bundle created secrets and v2 Job if CertificatePolicy is in NotCompliant state. Set logner evaluation period to give time for init-bundle Job to recreate and move CertificatePolicy to Compliant state.
  • Corrected Policy dependencies such that CertificatePolicy is dependent on init-bundle creation and not sync of secrets. Removal of init-bundle output breaks sync policy until they are recreated
  • Corrected Policy dependencies such that secret sync is dependent on init-bundle creation and not central install

Refs:

@gparvin
Copy link
Member

gparvin commented Dec 14, 2023

/approve
/hold

@gparvin
Copy link
Member

gparvin commented Dec 14, 2023

I added a hold while I test this. I do see a Pending policy which means I need to update the OPP QE script that tests this policy set. We just made an update last week to validate the policies aren't in the pending state 😄

@brian-jarvis
Copy link
Contributor Author

The side effect of using a NonCompliant dependency, it will always show as Pending.

I was just talking with cstark about this earlier. The policy showing as "pending" seems wrong to me. Yes technically the dependency is not met and it is pending to execute. But in this case it is expected to be in that state. The policy executing means another Policy is in an out of compliance state. If out of compliance is a red (bad) icon, then the dependency being satisfied should also be reflected as bad.

The overview page for Governance calls out pending policies as if something is incorrect and needs attention. But in this use case that assumption seems incorrect since the policy is in the expected state.

@gparvin
Copy link
Member

gparvin commented Dec 14, 2023

We have an ignorePending=true flag that can be added which I think is what we want here. That effectively keeps the policy in a Pending mode but the state is reported as Compliant. So far it seems to be working anyway...

…ficatePolicy is in NotCompliant state

Signed-off-by: Brian Jarvis <bjarvis@redhat.com>
@brian-jarvis
Copy link
Contributor Author

@gparvin I added ignorePending

Copy link
Member

@gparvin gparvin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks so much Brian! This looks good to me and I love the new contribution.

Copy link

openshift-ci bot commented Dec 15, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brian-jarvis, gparvin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gparvin
Copy link
Member

gparvin commented Dec 18, 2023

/unhold

@openshift-merge-bot openshift-merge-bot bot merged commit 6790c95 into open-cluster-management-io:main Dec 18, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants