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

Add secrets resource to in-line RBAC spec. #1890

Merged

Conversation

timoreimann
Copy link
Contributor

Previously only existed in the Github-hosted example file.

Fixes an oversight from #1707.

Previously only existed in the Github-hosted example file.
Copy link
Contributor

@dtomcej dtomcej left a comment

Choose a reason for hiding this comment

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

How does this differ from #1707 when we had to revert?

@timoreimann
Copy link
Contributor Author

@dtomcej you mean when we reverted #1798 through #1828? That's fairly unrelated as we only undid waiting for the secrets store to become populated (which would never happen in case RBAC access to Secrets wasn't set up).

We still need people to grant access to secrets to guarantee basic auth works. #1784 should drive watching for secrets more selectively.

Does that answer your question?

Copy link
Contributor

@dtomcej dtomcej left a comment

Choose a reason for hiding this comment

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

Good explanation.

LGTM

:shipit:

Copy link
Member

@ldez ldez left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@juliens juliens left a comment

Choose a reason for hiding this comment

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

LGTM

@timoreimann timoreimann merged commit 765c44d into traefik:master Jul 27, 2017
@timoreimann timoreimann deleted the k8s-add-secrets-to-inline-rbac-spec branch July 27, 2017 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants