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.

Sign up for GitHub

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

Jump to bottom

Guidance about Registries for production clusters #39815

Open
dims opened this issue Mar 6, 2023 · 12 comments
Open

Guidance about Registries for production clusters #39815

dims opened this issue Mar 6, 2023 · 12 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/docs Categorizes an issue or PR as relevant to SIG Docs.

Comments

@dims
Copy link
Member

dims commented Mar 6, 2023

In https://kubernetes.io/docs/setup/production-environment/ page (or somewhere), we should have guidance around:

  • Why folks should have their own registries?
  • What are the options?
  • What are the risks of not doing so?
  • How to set up mirrors in their CRI runtime etc.

thanks!
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 6, 2023
@chris-short
Copy link
Contributor

/label sig-docs

@k8s-ci-robot
Copy link
Contributor

@chris-short: The label(s) /label sig-docs cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label sig-docs

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.

@mengjiao-liu
Copy link
Member

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 7, 2023
@sftim
Copy link
Contributor

sftim commented Mar 8, 2023

@chrisnegus FYI

@sftim
Copy link
Contributor

sftim commented Mar 8, 2023

/sig cluster-lifecycle
/triage accepted
/priority important-soon

@k8s-ci-robot k8s-ci-robot added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 8, 2023
@sftim
Copy link
Contributor

sftim commented Mar 8, 2023

/sig docs

@k8s-ci-robot k8s-ci-robot added the sig/docs Categorizes an issue or PR as relevant to SIG Docs. label Mar 8, 2023
@chrisnegus
Copy link
Contributor

@sftim I'd be glad to take this on if you want to assign it to me.

@sftim
Copy link
Contributor

sftim commented Mar 8, 2023

You're very welcome to work on this @chrisnegus

Anyone else who wants to work on this: you're also welcome; please try to liaise with @chrisnegus rather than working solo - that's strongly encouraged, but not mandatory.

@jeremyrickard
Copy link
Contributor

I would love to help on this @chrisnegus .

@chrisnegus
Copy link
Contributor

@jeremyricka Excellent. I'll contact you.

@sftim
Copy link
Contributor

sftim commented May 2, 2023

/remove-priority important-soon
/priority important-longterm

The registry change has largely happened.

@k8s-ci-robot k8s-ci-robot added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels May 2, 2023
@k8s-triage-robot
Copy link

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/accepted Indicates an issue or PR is ready to be actively worked on. labels May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/docs Categorizes an issue or PR as relevant to SIG Docs.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@dims @chris-short @chrisnegus @k8s-ci-robot @sftim @jeremyrickard @mengjiao-liu @k8s-triage-robot