OCPBUGS-54208: UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver

[vrutkovs]

Extend loopback certificate validity to 3 years to match upstream

[openshift-ci-robot]

@vrutkovs: This pull request references Jira Issue OCPBUGS-54208, 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.19.0) matches configured target version for branch (4.19.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

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

In response to this:

Extend loopback certificate validity to 3 years to match upstream

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-robot]

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• cc36c72|adjusting loopback certificate validity in kube-apiserver: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[vrutkovs]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@vrutkovs: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.18

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.

[wangke19]

/retest-required

[vrutkovs]

/retest-required

[openshift-ci-robot]

@vrutkovs: the contents of this pull request could be automatically validated.

The following commits are valid:

• ba07fe1|UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver: the upstream PR kubernetes/kubernetes#130047 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[benluddy]

/lgtm

[benluddy]

/retest-required

[vrutkovs]

/test verify-deps

[openshift-ci-robot]

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits are valid:

• ba07fe1|UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver: the upstream PR kubernetes/kubernetes#130047 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 68e39f0|UPSTREAM: : make update: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits are valid:

• ba07fe1|UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver: the upstream PR kubernetes/kubernetes#130047 has merged

The following commits could not be validated and must be approved by a top-level approver:

• a5408c9|UPSTREAM: : make update: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits are valid:

• ba07fe1|UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver: the upstream PR kubernetes/kubernetes#130047 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 7b1a993|UPSTREAM: : make update: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits are valid:

• ba07fe1|UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver: the upstream PR kubernetes/kubernetes#130047 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 0a7dd02|UPSTREAM: : make update: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[vrutkovs]

/retest-required

[vrutkovs]

/retest-required

[openshift-ci-robot]

@vrutkovs: the contents of this pull request could be automatically validated.

The following commits are valid:

• ba07fe1|UPSTREAM: 130047: adjusting loopback certificate validity in kube-apiserver: the upstream PR kubernetes/kubernetes#130047 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[bertinatto]

/override ci/prow/verify-deps
This was removed.

[openshift-ci]

@bertinatto: Overrode contexts on behalf of bertinatto: ci/prow/verify-deps

In response to this:

/override ci/prow/verify-deps
This was removed.

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.

[bertinatto]

Matches upstream.

/lgtm

[bertinatto]

/retest-required

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy, bertinatto, vrutkovs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS [benluddy,bertinatto]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vrutkovs]

/cherry-pick release-4.19

[openshift-cherrypick-robot]

@vrutkovs: once the present PR merges, I will cherry-pick it on top of release-4.19 in a new PR and assign it to you.

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.

[openshift-ci]

@vrutkovs: The following tests 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/verify-deps	53d7e6d	link	false	/test verify-deps
ci/prow/e2e-agnostic-ovn-cmd	ba07fe1	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-techpreview-serial	ba07fe1	link	false	/test e2e-aws-ovn-techpreview-serial
ci/prow/okd-scos-e2e-aws-ovn	ba07fe1	link	false	/test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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-ci-robot]

@vrutkovs: Jira Issue OCPBUGS-54208: All pull requests linked via external trackers have merged:

• openshift/kubernetes#2277

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

In response to this:

Extend loopback certificate validity to 3 years to match upstream

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-cherrypick-robot]

@vrutkovs: new pull request created: #2297

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.

[openshift-cherrypick-robot]

@vrutkovs: new pull request created: #2298

In response to this:

/cherry-pick release-4.18

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.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-pod
This PR has been included in build openshift-enterprise-pod-container-v4.20.0-202505130412.p0.gda947ef.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: kube-proxy
This PR has been included in build kube-proxy-container-v4.20.0-202505130412.p0.gda947ef.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-hyperkube
This PR has been included in build openshift-enterprise-hyperkube-container-v4.20.0-202505130412.p0.gda947ef.assembly.stream.el9.
All builds following this will include this PR.

[openshift-cherrypick-robot]

@wangke19: new pull request could not be created: failed to create pull request against openshift/kubernetes#release-4.19 from head openshift-cherrypick-robot:cherry-pick-2277-to-release-4.19: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-2277-to-release-4.19."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

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.