-
Notifications
You must be signed in to change notification settings - Fork 806
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 gcr.io/k8s-staging-build-image #288
Conversation
Welcome @javier-b-perez! |
/approve i'll run the script to create the google group and whoever can create the gcs bucket, please remove the hold and then run the script for creating the bucket. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
DONE!
|
Is this the right scope? Are there going to be other artifacts that this same group of people will need to administer? |
the first item in mind is kube-cross, probably other images required to build, maybe even debian base images. |
Exactly what I was thinking. And you're happy with "build-image" as the umbrella repo for all these? |
Here are some alternate names for consideration: "k8s-staging-prelude" But I don't have strong opinions in this area because dims already created the resources and also I don't think we have an official policy on naming conventions anyway. /lgtm |
We don't have a convention here, and I don't think we need one. Just
think forward to the things that will be in here. Will "build-image"
be sufficiently descriptive that people won't be confused about its
purpose?
Maybe we should add a README in each dir explaining what the point of
that repository is?
…On Mon, Jul 8, 2019 at 10:05 AM Linus Arver ***@***.***> wrote:
Here are some alternate names for consideration:
"k8s-staging-prelude"
"k8s-staging-build-infra"
But I don't have strong opinions in this area because dims already created the resources and also I don't think we have an official policy on naming conventions anyway.
/lgtm
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@listx let's do this ... |
54e52da
to
518ec55
Compare
Added README.md |
/lgtm |
@listx can you please remove hold and run the script to create the new bucket? |
@thockin can you please create the bucket/project? |
i'll take care of this @javier-b-perez |
Created the ML
|
created the GCS bucket
|
/hold cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thockin@freakshow2 k8s.io master /infra/gcp$ ./ensure-staging-storage.sh build-image
build-image
Ensuring project exists: k8s-staging-build-image
billingAccountName: billingAccounts/018801-93540E-22A20E
billingEnabled: true
name: projects/k8s-staging-build-image/billingInfo
projectId: k8s-staging-build-image
Enabling the container registry API
Ensuring the registry exists and is readable
No changes made to gs://artifacts.k8s-staging-build-image.appspot.com/
Enabling Bucket Policy Only for gs://artifacts.k8s-staging-build-image.appspot.com...
Empowering GCR admins
Updated IAM policy for project [k8s-staging-build-image].
bindings:
- members:
- serviceAccount:service-960211007710@containerregistry.iam.gserviceaccount.com
role: roles/editor
- members:
- user:davanum@gmail.com
role: roles/owner
- members:
- group:k8s-infra-artifact-admins@kubernetes.io
role: roles/viewer
etag: BwWNQTioEZc=
version: 1
No changes made to gs://artifacts.k8s-staging-build-image.appspot.com/
No changes made to gs://artifacts.k8s-staging-build-image.appspot.com/
Empowering k8s-infra-staging-build-image@kubernetes.io to GCR
No changes made to gs://artifacts.k8s-staging-build-image.appspot.com/
No changes made to gs://artifacts.k8s-staging-build-image.appspot.com/
Enabling the GCS API
Ensuring the bucket exists and is world readable
No changes made to gs://k8s-staging-build-image/
Enabling Bucket Policy Only for gs://k8s-staging-build-image...
Ensuring the bucket has retention of 30d
Setting Retention Policy on gs://k8s-staging-build-image/...
Ensuring the bucket has auto-deletion of 30 days
Setting lifecycle configuration on gs://k8s-staging-build-image/...
Empowering GCS admins
Updated IAM policy for project [k8s-staging-build-image].
bindings:
- members:
- serviceAccount:service-960211007710@containerregistry.iam.gserviceaccount.com
role: roles/editor
- members:
- user:davanum@gmail.com
role: roles/owner
- members:
- group:k8s-infra-artifact-admins@kubernetes.io
role: roles/viewer
etag: BwWNQTlxZYM=
version: 1
No changes made to gs://k8s-staging-build-image/
No changes made to gs://k8s-staging-build-image/
Empowering k8s-infra-staging-build-image@kubernetes.io to GCS
No changes made to gs://k8s-staging-build-image/
No changes made to gs://k8s-staging-build-image/
Done
Create an staging repository where to host the build image kube-cross.
This is part of #158
/assign @dims @justinsb @thockin