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.

Sign up for GitHub

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

corrected link for gke-self-managed.sh #1703

Merged
merged 1 commit into from
Jun 15, 2022
Merged

corrected link for gke-self-managed.sh #1703

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/deploy/gke/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ under [core]/project is the one that contains your cluster. Second, ensure that
the current logged-in account listed under [core]/account is the owner of the project.
In other words, this account should have full project ownership permissions and be listed as
having the "Owner" role on the IAM page of your GCP project. You might ask why this
is needed? Well, the reason is that our [script](../resources/gke-self-managed.sh) invokes a kubectl command which
is needed? Well, the reason is that our [script](gke-self-managed.sh) invokes a kubectl command which
creates a new k8s RBAC role (see below for explanation why). In order to do this, the
current user must be the project owner. The "Owner" role also gives the account
permission to do basically anything so all commands the script runs should
Expand Down