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

Sort out GCR repository for pre-CNCF owned releases #303

Closed
randomvariable opened this issue Oct 23, 2018 · 4 comments
Closed

Sort out GCR repository for pre-CNCF owned releases #303

randomvariable opened this issue Oct 23, 2018 · 4 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Milestone

Comments

@randomvariable
Copy link
Member

/kind bug
/priority critical-urgent

What steps did you take and what happened:
[A clear and concise description of what the bug is.]
CRD migration changed the GCR repo that images are pushed to along the lines of GCP,
but the repository does not exist.

We will not have proper GCR repositories which are owned by the CNCF within the 1.13 release cycle, so will need a temporary home for the images.

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api-provider-aws version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Oct 23, 2018
@detiber
Copy link
Member

detiber commented Oct 23, 2018

/assign

@detiber detiber added this to the 20181025 milestone Oct 23, 2018
@detiber
Copy link
Member

detiber commented Oct 23, 2018

/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Oct 23, 2018
@detiber
Copy link
Member

detiber commented Oct 24, 2018

There is now a gcr.io repo created using the currently referenced name in the Makefile. It is currently a Heptio owned repository, but we are happy to transfer to CNCF ownership once that is a possibility.

@detiber detiber closed this as completed Oct 24, 2018
@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 lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels Apr 26, 2019
enxebre pushed a commit to enxebre/cluster-api-provider-aws-2 that referenced this issue Apr 15, 2020
…ey_id

support KMS key for EBS encryption
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

4 participants