Use kubectl and RBAC to look up zone for broker.rack #56
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:kafka
but kubectl solved that and also makes it handy to extract a label value.