OCPBUGS-62422: staticpod/prune: Remove tmp cert file pruning#2053
Conversation
|
@tchap: This pull request references Jira Issue OCPBUGS-62422, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
|
I am marking this as /hold to actually test this somewhere. |
|
/jira refresh |
|
@tchap: This pull request references Jira Issue OCPBUGS-62422, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
| func NewPruneController( | ||
| targetNamespace string, | ||
| podResourcePrefix string, | ||
| certDir string, |
There was a problem hiding this comment.
This is no longer needed, but it also breaks the API 🤷🏻♂️
|
Well, I am not sure extra testing is worth it as we are only removing stuff. The WIP PR I created only contains |
This is no longer needed as pruning happens in relevant sync looks that actually write these certificates atomically.
36add39 to
b9d4cad
Compare
|
@tchap: 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. |
|
/lgtm we need to update kas-o, kcm-o, etcd-o and the scheduler to pick up the change. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: p0lyn0mial, tchap 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 |
|
@tchap: Jira Issue OCPBUGS-62422: Some pull requests linked via external trackers have merged: The following pull request, linked via external tracker, has not merged: All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-62422 has not been moved to the MODIFIED state. 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. |
|
Fix included in accepted release 4.22.0-0.nightly-2026-01-14-031657 |
This is no longer needed as pruning happens in relevant sync looks that actually write these certificates atomically.