CCO-819: Add TLSAdherence tracking#13
CCO-819: Add TLSAdherence tracking#13openshift-merge-bot[bot] merged 2 commits intoopenshift:mainfrom
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
This PR is a draft until openshift/api/pull/2680 has merged |
jstuever
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@jstuever: This pull request references CCO-819 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-merge-robot
added
the
needs-rebase
Add InitialTLSAdherencePolicy and OnAdherencePolicyChange callback to the SecurityProfileWatcher to detect and handle changes to the APIServer's TLS adherence policy. This enables the operator to react appropriately when the TLS adherence policy is modified. Tests have been updated to cover the new policy tracking behavior. Assisted-by: gemini-3.1-pro-preview
Add the FetchAPIServerTLSAdherencePolicy function to the tls package to allow retrieving the TLS adherence policy configured in the APIServer resource. This enables consumers to determine the expected TLS adherence behavior directly from the OpenShift cluster configuration. Assisted-by: gemini-3.1-pro-preview
openshift-merge-robot
removed
the
needs-rebase
|
/cc @damdo |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
@jstuever: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
I tested this locally using openshift/cloud-credential-operator#965 and it works as I would expect. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damdo, jstuever The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
4 participants
This change adds the ability to track and fetch the TLSAdherence from the apiserver configuration.
Assisted-by: gemini-3.1-pro-preview