Skip to content

[release-4.17] OCPBUGS-66229: UPSTREAM <carry>: bump kubernetes-apiserver to pick up loopback certificate expiration update#584

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.17from
dinhxuanvu:cert-4.17
Jan 23, 2026
Merged

[release-4.17] OCPBUGS-66229: UPSTREAM <carry>: bump kubernetes-apiserver to pick up loopback certificate expiration update#584
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.17from
dinhxuanvu:cert-4.17

Conversation

@dinhxuanvu
Copy link
Copy Markdown
Contributor

Authored-by: Bryce Palmer bpalmer@redhat.com
Signed-off-by: Vu Dinh vdinh@redhat.com

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Dec 1, 2025

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from benluddy and dgrisonnet December 1, 2025 15:53
@dinhxuanvu dinhxuanvu changed the title UPSTREAM <carry>: bump kubernetes-apiserver to pick up loopback certificate expiration update OCPBUGS-66229: UPSTREAM <carry>: bump kubernetes-apiserver to pick up loopback certificate expiration update Dec 2, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important 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 Dec 2, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@dinhxuanvu: This pull request references Jira Issue OCPBUGS-66229, which is invalid:

  • expected dependent Jira Issue OCPBUGS-65842 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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:

Authored-by: Bryce Palmer bpalmer@redhat.com
Signed-off-by: Vu Dinh vdinh@redhat.com

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.

…ficate expiration update

Authored-by: Bryce Palmer <bpalmer@redhat.com>
Signed-off-by: Vu Dinh <vudinh@outlook.com>
@everettraven
Copy link
Copy Markdown

/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 Jan 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@everettraven: This pull request references Jira Issue OCPBUGS-66229, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-65842 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-65842 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

Requesting review from QA contact:
/cc @gangwgr

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.

@openshift-ci openshift-ci Bot requested a review from gangwgr January 19, 2026 18:53
@everettraven everettraven changed the title OCPBUGS-66229: UPSTREAM <carry>: bump kubernetes-apiserver to pick up loopback certificate expiration update [release-4.17] OCPBUGS-66229: UPSTREAM <carry>: bump kubernetes-apiserver to pick up loopback certificate expiration update Jan 19, 2026
@benluddy
Copy link
Copy Markdown
Contributor

/lgtm
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 19, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jan 19, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy, dinhxuanvu

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 19, 2026
@everettraven
Copy link
Copy Markdown

/retest-required

@everettraven
Copy link
Copy Markdown

Verified with a clusterbot cluster with this PR:

$ oc rsh -n openshift-apiserver apiserver-79f6c487cd-4v4mw curl --resolve apiserver-loopback-client:8443:127.0.0.1 https://apiserver-loopback-client:8443 -v -k|grep "Server certificate" -A 5

Defaulted container "openshift-apiserver" out of: openshift-apiserver, openshift-apiserver-check-endpoints, fix-audit-permissions (init)
* Server certificate:
*  subject: CN=apiserver-loopback-client@1768917011
*  start date: Jan 20 12:50:10 2026 GMT
*  expire date: Jan 20 12:50:10 2029 GMT
*  issuer: CN=apiserver-loopback-client-ca@1768917011
*  SSL certificate verify result: self-signed certificate in certificate chain (19), continuing anyway.

@everettraven
Copy link
Copy Markdown

/verified by @everettraven

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 20, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@everettraven: This PR has been marked as verified by @everettraven.

Details

In response to this:

/verified by @everettraven

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.

@benluddy
Copy link
Copy Markdown
Contributor

benluddy commented Jan 20, 2026

/override ci/prow/e2e-aws-serial
https://issues.redhat.com/browse/OCPBUGS-72531

@benluddy
Copy link
Copy Markdown
Contributor

/override ci/prow/e2e-aws-ovn-serial

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 4b8cb33 and 2 for PR HEAD 3a2fb81 in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 20, 2026

@benluddy: Overrode contexts on behalf of benluddy: ci/prow/e2e-aws-ovn-serial

Details

In response to this:

/override ci/prow/e2e-aws-ovn-serial

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.

@gangwgr
Copy link
Copy Markdown
Contributor

gangwgr commented Jan 22, 2026

oc rsh -n openshift-apiserver apiserver-5dc76969bb-555v4 curl --resolve apiserver-loopback-client:8443:127.0.0.1 https://apiserver-loopback-client:8443 -v -k|grep "Server certificate" -A 5
Defaulted container "openshift-apiserver" out of: openshift-apiserver, openshift-apiserver-check-endpoints, fix-audit-permissions (init)

  • Server certificate:
  • subject: CN=apiserver-loopback-client@1769074304
  • start date: Jan 22 08:31:44 2026 GMT
  • expire date: Jan 22 08:31:44 2029 GMT
  • issuer: CN=apiserver-loopback-client-ca@1769074304
  • SSL certificate verify result: self-signed certificate in certificate chain (19), continuing anyway.
    rgangwar@rgangwar-mac release % oc get clusterversion
    NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
    version 4.17.0-0-2026-01-22-083245-test-ci-ln-v54yd62-latest True False 106m Cluster version is 4.17.0-0-2026-01-22-083245-test-ci-ln-v54yd62-latest
    rgangwar@rgangwar-mac release %
    Pre-merge verification

@gangwgr
Copy link
Copy Markdown
Contributor

gangwgr commented Jan 22, 2026

/verified by #584 (comment)

@openshift-ci-robot
Copy link
Copy Markdown

@gangwgr: This PR has been marked as verified by https://github.com/openshift/openshift-apiserver/pull/584#issuecomment-3783924086.

Details

In response to this:

/verified by #584 (comment)

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.

@wangke19
Copy link
Copy Markdown
Contributor

/test e2e-aws-ovn-serial

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 23, 2026

@dinhxuanvu: 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.

@openshift-merge-bot openshift-merge-bot Bot merged commit 9016b23 into openshift:release-4.17 Jan 23, 2026
11 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@dinhxuanvu: Jira Issue Verification Checks: Jira Issue OCPBUGS-66229
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-66229 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Authored-by: Bryce Palmer bpalmer@redhat.com
Signed-off-by: Vu Dinh vdinh@redhat.com

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

Fix included in accepted release 4.17.0-0.nightly-2026-01-23-160148

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-important Referenced Jira bug's severity is important 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants