Skip to content

OCPBUGS-62422: staticpod/prune: Remove tmp cert file pruning#2053

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
tchap:staticpod-pruner-tmp-certs
Jan 8, 2026
Merged

OCPBUGS-62422: staticpod/prune: Remove tmp cert file pruning#2053
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
tchap:staticpod-pruner-tmp-certs

Conversation

@tchap
Copy link
Copy Markdown
Contributor

@tchap tchap commented Nov 18, 2025

This is no longer needed as pruning happens in relevant sync looks that actually write these certificates atomically.

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 18, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@tchap: This pull request references Jira Issue OCPBUGS-62422, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is no longer needed as pruning happens in relevant sync looks that actually write these certificates atomically.

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.

@tchap
Copy link
Copy Markdown
Contributor Author

tchap commented Nov 18, 2025

I am marking this as

/hold

to actually test this somewhere.

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 18, 2025
@tchap
Copy link
Copy Markdown
Contributor Author

tchap commented Nov 18, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 18, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@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
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

Details

In response to this:

/jira refresh

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,
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is no longer needed, but it also breaks the API 🤷🏻‍♂️

@tchap
Copy link
Copy Markdown
Contributor Author

tchap commented Nov 20, 2025

Well, I am not sure extra testing is worth it as we are only removing stuff. The WIP PR I created only contains Nothing to prune log entries.

Comment thread pkg/operator/staticpod/prune/cmd.go Outdated
Comment thread pkg/operator/staticpod/prune/cmd.go Outdated
This is no longer needed as pruning happens in relevant sync looks that
actually write these certificates atomically.
@tchap tchap force-pushed the staticpod-pruner-tmp-certs branch from 36add39 to b9d4cad Compare January 8, 2026 09:46
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 8, 2026

@tchap: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

@p0lyn0mial
Copy link
Copy Markdown
Contributor

/lgtm

we need to update kas-o, kcm-o, etcd-o and the scheduler to pick up the change.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jan 8, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 8, 2026

[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

Details 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 8, 2026
@tchap
Copy link
Copy Markdown
Contributor Author

tchap commented Jan 8, 2026

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 8, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit db8dbd6 into openshift:master Jan 8, 2026
4 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@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 refresh.

Jira Issue OCPBUGS-62422 has not been moved to the MODIFIED state.

Details

In response to this:

This is no longer needed as pruning happens in relevant sync looks that actually write these certificates atomically.

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.

@tchap tchap deleted the staticpod-pruner-tmp-certs branch January 8, 2026 14:29
@openshift-merge-robot
Copy link
Copy Markdown
Contributor

Fix included in accepted release 4.22.0-0.nightly-2026-01-14-031657

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants