Skip to content

setup-project.sh should skip keys creation step for noauth overlay #639

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

Closed
saikat-royc opened this issue Oct 27, 2020 · 5 comments · Fixed by #879
Closed

setup-project.sh should skip keys creation step for noauth overlay #639

saikat-royc opened this issue Oct 27, 2020 · 5 comments · Fixed by #879
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@saikat-royc
Copy link
Member

In https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/master/deploy/setup-project.sh,
gcloud iam service-accounts keys create step should be skipped when using a noauth overlay.

@mattcary
Copy link
Contributor

We already have a CREATE_SA variable to control the project setup.

I was under the impression that this script would only be run once, and rarely, and might be used across multiple deployment overlays. eg it's not run by the test harness like the deploy script is.

I don't know if we can plumb the noauth overlay selection through to here anyway.

Definitely the documentation around this can be improved.

@saikat-royc
Copy link
Member Author

saikat-royc commented Oct 27, 2020

@mattcary I was thinking more for a first time setup on GCE cluster, where we would like to use the noauth style ADC. The current script, will detect there is no existing SA, and set CREATE_SA=true, and proceed with SA creation and key creation(we could take a new flag SKIP_SA_KEY_CREATE which is false by default). Thoughts?

@mattcary
Copy link
Contributor

mattcary commented Nov 4, 2020

Yeah, that makes sense. I think we should make the noauth method the default one and nudge everyone towards a streamlined setup. So maybe have SA_KEY_CREATE = false by default

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 2, 2021
@mattcary
Copy link
Contributor

mattcary commented Feb 2, 2021 via email

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants