Skip to content

Conversation

@sanchezl
Copy link
Contributor

@sanchezl sanchezl commented May 8, 2025

  • Add the ability to start a rollback controller when a supported controller is disabled.
  • Add the openshift.io/serviceaccount-pull-secrets-rollback controller set which runs when the openshift.io/serviceaccount-pull-secrets controller set is disabled.
  • Add the legacyImagePullSecretRollbackController to the openshift.io/serviceaccount-pull-secrets controller set.

@openshift-ci openshift-ci bot requested review from Moebasim and prabhapa May 8, 2025 15:57
@sanchezl sanchezl changed the title OCPBUGS 52193 OCPBUGS 52193: legacy image pull secret rollback controller May 8, 2025
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 8, 2025
@sanchezl sanchezl changed the title OCPBUGS 52193: legacy image pull secret rollback controller OCPBUGS-52193: legacy image pull secret rollback controller May 8, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels May 8, 2025
@openshift-ci-robot
Copy link
Contributor

@sanchezl: This pull request references Jira Issue OCPBUGS-52193, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jitsingh@redhat.com), skipping review request.

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

Details

In response to this:

  • Add the ability to start a rollback controller when a supported controller is disabled.
  • Add the openshift.io/serviceaccount-pull-secrets-rollback controller set which runs when the openshift.io/serviceaccount-pull-secrets controller set is disabled.
  • Add the legacyImagePullSecretRollbackController to the openshift.io/serviceaccount-pull-secrets controller set.

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.

kc,
ctx.KubernetesInformers.Core().V1().Secrets(),
).Run(ctx.Context, 1)

Copy link
Contributor

Choose a reason for hiding this comment

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

What is up with this RunServiceAccountPullSecretsController function ? Is it used anywhere ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Dead code. I need to clean it up, but wanted to limit this PR to the issue at hand.

Copy link
Contributor

@tchap tchap May 11, 2025

Choose a reason for hiding this comment

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

Hi, I've actually just opened #381 , so we can get that merged if that is ok.

@ricardomaraschini
Copy link
Contributor

/retest

@ricardomaraschini
Copy link
Contributor

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 12, 2025

@sanchezl: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security 5f6a9dc link false /test security

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.

@ricardomaraschini
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 13, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ricardomaraschini, sanchezl

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-merge-bot openshift-merge-bot bot merged commit ed71ab5 into openshift:master May 13, 2025
13 of 14 checks passed
@openshift-ci-robot
Copy link
Contributor

@sanchezl: Jira Issue OCPBUGS-52193: All pull requests linked via external trackers have merged:

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

Details

In response to this:

  • Add the ability to start a rollback controller when a supported controller is disabled.
  • Add the openshift.io/serviceaccount-pull-secrets-rollback controller set which runs when the openshift.io/serviceaccount-pull-secrets controller set is disabled.
  • Add the legacyImagePullSecretRollbackController to the openshift.io/serviceaccount-pull-secrets controller set.

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-openshift-controller-manager
This PR has been included in build ose-openshift-controller-manager-container-v4.20.0-202505140744.p0.ged71ab5.assembly.stream.el9.
All builds following this will include this PR.

@sanchezl
Copy link
Contributor Author

/cherry-pick release-4.19

@openshift-cherrypick-robot

@sanchezl: new pull request created: #384

Details

In response to this:

/cherry-pick release-4.19

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.

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/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.

6 participants