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

Moving images away from quay.io? #86

Closed
xing-yang opened this issue May 19, 2020 · 21 comments
Closed

Moving images away from quay.io? #86

xing-yang opened this issue May 19, 2020 · 21 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@xing-yang
Copy link
Contributor

CI is failing because quay.io is down. It's reported in this issue:
kubernetes/kubernetes#91242

Should we move our images to a different repo, i.e., the community infra?

CC @msau42 @pohly

@xing-yang
Copy link
Contributor Author

One update from https://status.quay.io/ says that "The number of open connections to the Quay.io database increased significantly causing an outage of the service, we are still investigating the root cause of this spike in DB connections. "

@xing-yang
Copy link
Contributor Author

We have staging repos for CSI in GCR and the image promotion process. It's used for node-driver-registrar only right now. Should we do this for all sidecar repos?
https://github.com/kubernetes-csi/node-driver-registrar/blob/master/cloudbuild.yaml

@justaugustus
Copy link
Member

Thanks for opening this, @xing-yang!
I poked @hasheddan to get the conversation started in kubernetes/kubernetes#91242 / https://kubernetes.slack.com/archives/CJH2GBF7Y/p1589887799251500.

Where possible, images that are used by that community should be on community infra.
I'd suggest moving anything currently hosted at quay.io/k8scsi be moved in a CSI staging repository and then promoted to our prod registry.

Let me know how I can help and feel free to assign me in reviews. :)

@xing-yang
Copy link
Contributor Author

Thanks @justaugustus!

@pohly
Copy link
Contributor

pohly commented May 19, 2020

Work is in progress. It's not just about pushing to some other registry, but also about using an entirely different build infrastructure and producing images for multiple different architectures, ideally including Windows.

As a next step it would help if someone could approve kubernetes-csi/node-driver-registrar#82. As I said in the review of that PR, we need to figure out how building of Windows images can be unified with the approach taken for all other platforms (i.e. build the binary inside the multi-stage Dockerfile, using the same base images if possible).

/cc @vitt-bagal @jingxu97 @ddebroy

@pohly
Copy link
Contributor

pohly commented May 27, 2020

@pohly
Copy link
Contributor

pohly commented May 27, 2020

/assign

pohly added a commit to pohly/test-infra that referenced this issue May 28, 2020
This is part of rolling out multi-architecture image building for GCR,
see kubernetes-csi/csi-release-tools#86
pohly added a commit to pohly/test-infra that referenced this issue May 28, 2020
This is part of rolling out multi-architecture image building for GCR,
see kubernetes-csi/csi-release-tools#86
chizhg pushed a commit to chizhg/kubernetes-test-infra that referenced this issue Jun 6, 2020
This is part of rolling out multi-architecture image building for GCR,
see kubernetes-csi/csi-release-tools#86
@pohly
Copy link
Contributor

pohly commented Aug 3, 2020

The vanity domain switch has completed: https://groups.google.com/forum/#!msg/kubernetes-dev/Z-y1EK-XBQM/-fehCfLpAAAJ

@pohly
Copy link
Contributor

pohly commented Aug 3, 2020

k8s.gcr.io works for "docker pull" but only redirects to https://cloud.google.com/container-registry/ when used in a web browser. To list images, use https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/US/sig-storage

@jingxu97
Copy link

jingxu97 commented Aug 4, 2020

@pohly for the multi-arch image of node-driver-registar, when can it be promoted from staging to release? https://console.cloud.google.com/gcr/images/k8s-staging-sig-storage/GLOBAL/csi-node-driver-registrar?gcrImageListsize=30

@pohly
Copy link
Contributor

pohly commented Aug 4, 2020

node-driver-registrar needs a formal new release. We don't promote rc or canary images to the production repo. According to https://github.com/orgs/kubernetes-csi/projects/29#card-42709613, it's "not ready".

@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 Dec 1, 2020
@xing-yang
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 1, 2020
@msau42
Copy link
Collaborator

msau42 commented Dec 1, 2020

I believe the last thing that's still remaining is to turn down our travis jobs that push to quay. I think we can do this once those minor versions are out of our support window.

@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-contributor-experience at kubernetes/community.
/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 Mar 1, 2021
@pohly
Copy link
Contributor

pohly commented Mar 2, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 2, 2021
@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-contributor-experience at kubernetes/community.
/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 Jun 29, 2021
@xing-yang
Copy link
Contributor Author

@msau42 @pohly do we still need to keep this issue open?

@msau42
Copy link
Collaborator

msau42 commented Jul 19, 2021

Yes travis jobs are disabled, so I think we're done here.

/close

@k8s-ci-robot
Copy link
Contributor

@msau42: Closing this issue.

In response to this:

Yes travis jobs are disabled, so I think we're done here.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

7 participants