Skip to content

Conversation

@everettraven
Copy link

Updates the loopback certificate generation logic to extend the certificate validity to three years as a basis to fix both https://issues.redhat.com/browse/OCPBUGS-61760 and https://issues.redhat.com/browse/OCPBUGS-61759.

@openshift-ci openshift-ci bot requested review from deads2k and tkashem October 23, 2025 15:15
// - https://issues.redhat.com/browse/OCPBUGS-61760
// - https://issues.redhat.com/browse/OCPBUGS-61759
// Achieves the same result as the upstream change in https://github.com/kubernetes/kubernetes/pull/130047
maxAge := time.Hour * 24 * (3 * 365 + 1) // one year self-signed certs

Choose a reason for hiding this comment

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

Suggested change
maxAge := time.Hour * 24 * (3 * 365 + 1) // one year self-signed certs
maxAge := time.Hour * 24 * (3 * 365 + 1) // three year self-signed certs

Comment on lines 97 to 104
// NOTE: As part of the work to resolve https://issues.redhat.com/browse/OCPBUGS-61760
// and https://issues.redhat.com/browse/OCPBUGS-61759 it was decided that copying
// the loopback certification creation utility function to a local
// utility function would save significant effort over cherry-picking
// the fix from https://github.com/kubernetes/kubernetes/pull/130047 to
// https://github.com/openshift/kubernetes-client-go .
// We don't expect to backport many changes on top of this and it seemed
// lower risk than switching impacted modules to our fork of client-go.

Choose a reason for hiding this comment

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

I think I'd introduce a brand new file in this directory to contain the source of the forked function to isolate the diff surface here to just the line that calls GenerateSelfSignedCertKey.

Comment on lines 117 to 121
// NOTE: Modified from the original of 1 year to 3 years to fix
// - https://issues.redhat.com/browse/OCPBUGS-61760
// - https://issues.redhat.com/browse/OCPBUGS-61759
// Achieves the same result as the upstream change in https://github.com/kubernetes/kubernetes/pull/130047
maxAge := time.Hour * 24 * (3 * 365 + 1) // one year self-signed certs
Copy link
Author

Choose a reason for hiding this comment

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

This line is the only one changed from the copy-pasted client-go code.

@everettraven everettraven force-pushed the bugfix/loopback-cert-3years branch from 5ef7fd2 to 66e0441 Compare October 23, 2025 15:23
@everettraven everettraven changed the title UPSTREAM: <carry>: extend loopback certificate validity to three years OCPBUGS-63482: UPSTREAM: <carry>: extend loopback certificate validity to three years Oct 23, 2025
@openshift-ci-robot openshift-ci-robot added 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 Oct 23, 2025
@openshift-ci-robot
Copy link

@everettraven: This pull request references Jira Issue OCPBUGS-63482, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-63482 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

In response to this:

Updates the loopback certificate generation logic to extend the certificate validity to three years as a basis to fix both https://issues.redhat.com/browse/OCPBUGS-61760 and https://issues.redhat.com/browse/OCPBUGS-61759.

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.

Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
@everettraven everettraven force-pushed the bugfix/loopback-cert-3years branch from 66e0441 to 3771ecd Compare October 24, 2025 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants