This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Add guide to use GKE workload identity with private GCR registry #3023
Conversation
This file contains 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
|
@hiddeco care to review? :-) |
|
@marratj won’t be before Monday next week as I am enjoying time off. |
hiddeco
reviewed
May 11, 2020
There was a problem hiding this comment.
The guide is detailed but easy to follow! 💯
To actually make it appear in the guides menu you need to add an entry to mkdocs.yaml.
marratj
force-pushed
the
gke-workload-identity-docs
branch
from
4cecf31
to
4f9d866
Compare
hiddeco
force-pushed
the
gke-workload-identity-docs
branch
from
e8188ca
to
9b153b9
Compare
hiddeco
force-pushed
the
gke-workload-identity-docs
branch
from
9b153b9
to
aedc807
Compare
added 5 commits
May 12, 2020 12:16
hiddeco
force-pushed
the
gke-workload-identity-docs
branch
from
aedc807
to
28655d6
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR is for adding a guide to the docs on how to configure the Flux service account for use with GKE Workload Identity if using a private Google Container Registry.
When Workload Identity is enabled and private images are being used for workloads in the cluster, Flux needs to be authenticated against GCR (actually the GCS bucket beneath it) to be able to scan for new images.
This is a guide that "fixes" #2379