Use kubectl and RBAC to look up zone for broker.rack #56
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adding myself to cluster-admin clusterrole
instead of curl. Could it be that curl is based on Alpine?
but be prepared for misleading error messages (for an RBAC noob like me) when your operation does not match the Role's rights: ``` root@test-rack-awareness-267009956-k0ffs:/opt/kafka# kubectl get pod $HOSTNAME NAME READY STATUS RESTARTS AGE test-rack-awareness-267009956-k0ffs 1/1 Running 0 14m root@test-rack-awareness-267009956-k0ffs:/opt/kafka# kubectl get pods Error from server (Forbidden): User "system:serviceaccount:kafka:kafka" cannot list pods in the namespace "kafka".: "Unknown user \"system:serviceaccount:kafka:kafka\"" (get pods) ```
and service account for debugging
Merged
|
Without |
This was referenced Aug 3, 2017
|
With #59 RBAC has no effect on core manifests, and works in-container with curl. |
solsson
added a commit
that referenced
this pull request
Jan 8, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
API use from within pods gets permission denied with Kubernetes 1.7 on GKE. RBAC makes sense and we should learn to use it. Docs are ok but thin on conventions. I searched around but I guess the role and service account naming needs discussion.
I failed to get curl calls like in #39 to auth as
system:serviceaccount:kafka:kafkabut kubectl solved that and also makes it handy to extract a label value.