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

Bug 1794885: UPSTREAM: <carry>: bootstrap user - make tokens have implicit audiences #24503

Merged

Conversation

stlaz
Copy link
Member

@stlaz stlaz commented Feb 5, 2020

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 5, 2020
@stlaz stlaz changed the title UPSTREAM: <carry>: bootstrap user - make tokens have implicit audiences Bug 1794885: UPSTREAM: <carry>: bootstrap user - make tokens have implicit audiences Feb 5, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Feb 5, 2020
@openshift-ci-robot
Copy link

@stlaz: This pull request references Bugzilla bug 1794885, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Bug 1794885: UPSTREAM: : bootstrap user - make tokens have implicit audiences

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.

@sttts
Copy link
Contributor

sttts commented Feb 5, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 5, 2020
@sttts
Copy link
Contributor

sttts commented Feb 5, 2020

/approve

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stlaz, sttts

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 5, 2020
@marun
Copy link
Contributor

marun commented Feb 5, 2020

@stlaz @sttts Why does this code need to be duplicated from #24461 ? Seems like an opportunity to factor out the common code to avoid this class of error in the future.

@sttts
Copy link
Contributor

sttts commented Feb 5, 2020

It's actually copied from upstream (service account authn). If we want to factor it out, then in upstream.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@marun
Copy link
Contributor

marun commented Feb 5, 2020

It's actually copied from upstream (service account authn). If we want to factor it out, then in upstream.

In an ideal world, yes, the openshift patches for tokenauthenticator and bootstrapauthenticator would derive from better-factored upstream code. I'm not sure why it would be necessary to wait for that, though, to remove the potential source of errors represented by tokenauthenticator and bootstrapauthenticator being independently implemented given that their functionality is largely common.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@marun
Copy link
Contributor

marun commented Feb 5, 2020

/test all

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

5 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@stlaz
Copy link
Member Author

stlaz commented Feb 6, 2020

/retest
looks like KAS couldn't reach etcd in the upgrade job, not good

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 2cdd923 into openshift:master Feb 6, 2020
@openshift-ci-robot
Copy link

@stlaz: All pull requests linked via external trackers have merged. Bugzilla bug 1794885 has been moved to the MODIFIED state.

In response to this:

Bug 1794885: UPSTREAM: : bootstrap user - make tokens have implicit audiences

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.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants