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.

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

Create docs to create k8s-support-<project> GCS bucket with correct ACLs #47

Open
stephen-soltesz opened this issue Jun 19, 2018 · 4 comments

Comments

@stephen-soltesz
Copy link
Contributor

No description provided.

@stephen-soltesz stephen-soltesz changed the title Create script to create k8s-support-<project> GCS bucket with correct ACLs Create docs to create k8s-support-<project> GCS bucket with correct ACLs Jul 16, 2018
@nkinkade
Copy link
Contributor

@stephen-soltesz: Is this still an issue? CloudBuild needs write access to the bucket, as do Operators (when running the bootstrap_platform_cluster.sh script. This almost seems like a part of the larger issue of having adhoc ACLs manually configured throughout each project. Not sure if this issue is still relevant?

@stephen-soltesz
Copy link
Contributor Author

@nkinkade Would we have to create the buckets manually if we targeted a new GCP project? or, are there scripts that do this automatically?

@nkinkade
Copy link
Contributor

@stephen-soltesz: it is currently a manual process. I guess my question is where this sort of documentation should go, and whether this particular issue is just one small part of the larger issue that nearly all of our GCS buckets, as far as I know, were created manually and had ACLs applied manually.

@stephen-soltesz
Copy link
Contributor Author

I'm confident that our "just so" configs of gcp projects are going to bite us one day -- I just don't know which day (could be a long time). The passage of time makes this worse not better. That's the main motivation here. A secondary reason could be making k8s-support re-usable by not-us. That's under specified though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants