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

Revert "limit forbidden error to details of what was forbidden" #70314

Merged
merged 2 commits into from
Oct 30, 2018

Conversation

sambdavidson
Copy link
Contributor

Reverts changes from #67617.

The main justification for the original change (#67617) was the confusing "Unknown user" authorizer response returned by the GKE authorizor when an authorize request is made with a non-Google/GCP service account identity. This was leading to confusion. However one big down side in removing the authorizer's reason is users never get constructive feedback on how to fix 403 Forbidden issues, e.g. "Required permission container.pods.get" for the GKE authorizer.

Recently the GKE "Unknown user" error has been removed which should mitigate user confusion once this PR is submitted. At this point I think returning authorizer _reason_s is valuable and should be re-enabled.

/kind design
/assign liggitt

NONE

@k8s-ci-robot
Copy link
Contributor

@samdamana: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. kind/design Categorizes issue or PR as related to design. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. area/apiserver sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Oct 26, 2018
Copy link
Contributor

@fejta fejta left a comment

Choose a reason for hiding this comment

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

Consider creating a test/integration/OWNERS and/or test/integration/master/OWNERS file so PRs like this are delegated correctly.

/approve
for test changes

@idealhack
Copy link
Member

/ok-to-test
/release-note-none

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 29, 2018
@liggitt
Copy link
Member

liggitt commented Oct 29, 2018

if we want to revert this, we should also revert the RBAC change from #65906 in the same PR

@sambdavidson
Copy link
Contributor Author

if we want to revert this, we should also revert the RBAC change from #65906 in the same PR

#65906 just contains some tiny improvements to the reason logic that look like they could stay in. Why do you think it should get reverted as well?

@liggitt
Copy link
Member

liggitt commented Oct 29, 2018

#65906 just contains some tiny improvements to the reason logic that look like they could stay in. Why do you think it should get reverted as well?

as pointed out in https://github.com/kubernetes/kubernetes/pull/65906/files#r210048853, always echoing "No RBAC policy matched" isn't really an improvement

@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 29, 2018
@sambdavidson
Copy link
Contributor Author

Yeah makes sense.

Alright I have also reverted #65906 within this PR. :)

@sambdavidson
Copy link
Contributor Author

/retest

@liggitt
Copy link
Member

liggitt commented Oct 29, 2018

/approve
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 29, 2018
@liggitt
Copy link
Member

liggitt commented Oct 29, 2018

/retest

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fejta, liggitt, samdamana

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 29, 2018
@k8s-ci-robot k8s-ci-robot merged commit 361f8c3 into kubernetes:master Oct 30, 2018
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. area/apiserver cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/design Categorizes issue or PR as related to design. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants