Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-02-14-214710_amd64-2024-02-14_arm64-2024-02-16 #3029

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.15.0-0.nightly-2024-02-14-214710
arm64: 4.15.0-0.nightly-arm64-2024-02-16-015018
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1758355556076097536

  • kubernetes image-arm64 f1618d54a81f9f1bc0c3bf326454ab8e107eea87 to 6216ea1e51a2126f5b843a4ae7c1f414161cca8b
    • d9ac8bc14 2024-02-13T17:15:56-05:00 UPSTREAM: 123165: Add AudienceMatchPolicy and support multiple audiences in AuthenticationConfiguration
    • 47cdefa50 2024-02-13T17:15:56-05:00 UPSTREAM: 121622: add StructuredAuthenticationConfiguration feature to kube feature gates file
    • 232906ad7 2024-02-13T15:23:51-05:00 UPSTREAM: 120183: [StructuredAuthnConfig] use local variables in oidc pkg
    • 6042f241d 2024-02-13T15:23:28-05:00 UPSTREAM: 119142: [StructuredAuthenticationConfig] Add feature flag and wire up --authentication-config flag
    • 2fe9b7959 2024-02-13T15:22:02-05:00 UPSTREAM: 118984: [StructuredAuthenticationConfig] Create struct for authn config and re-wire OIDC flags to use it
    • 5aa64c6fa 2024-01-18T12:42:45+00:00 UPSTREAM: : Update management webhook pod admission logic

/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 16, 2024
@openshift-ci-robot
Copy link

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

In response to this:

amd64: 4.15.0-0.nightly-2024-02-14-214710
arm64: 4.15.0-0.nightly-arm64-2024-02-16-015018
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1758355556076097536

  • kubernetes image-arm64 f1618d54a81f9f1bc0c3bf326454ab8e107eea87 to 6216ea1e51a2126f5b843a4ae7c1f414161cca8b
  • d9ac8bc14 2024-02-13T17:15:56-05:00 UPSTREAM: 123165: Add AudienceMatchPolicy and support multiple audiences in AuthenticationConfiguration
  • 47cdefa50 2024-02-13T17:15:56-05:00 UPSTREAM: 121622: add StructuredAuthenticationConfiguration feature to kube feature gates file
  • 232906ad7 2024-02-13T15:23:51-05:00 UPSTREAM: 120183: [StructuredAuthnConfig] use local variables in oidc pkg
  • 6042f241d 2024-02-13T15:23:28-05:00 UPSTREAM: 119142: [StructuredAuthenticationConfig] Add feature flag and wire up --authentication-config flag
  • 2fe9b7959 2024-02-13T15:22:02-05:00 UPSTREAM: 118984: [StructuredAuthenticationConfig] Create struct for authn config and re-wire OIDC flags to use it
  • 5aa64c6fa 2024-01-18T12:42:45+00:00 UPSTREAM: : Update management webhook pod admission logic

/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug

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 added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Feb 16, 2024
Copy link
Contributor

openshift-ci bot commented Feb 16, 2024

@microshift-rebase-script[bot]: all tests passed!

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/test-infra repository. I understand the commands that are listed here.

Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 16, 2024
Copy link
Contributor

openshift-ci bot commented Feb 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: microshift-rebase-script[bot], pacevedom

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:

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 Feb 16, 2024
@dhellmann
Copy link
Contributor

/label staff-eng-approved

@openshift-ci openshift-ci bot added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Feb 16, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit e781225 into release-4.15 Feb 16, 2024
10 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.15-4.15.0-0.nightly-2024-02-14-214710_amd64-2024-02-14_arm64-2024-02-16 branch February 16, 2024 13:30
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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants