-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
kops: test alternative registry for periodics-distros #25155
kops: test alternative registry for periodics-distros #25155
Conversation
I also would like to extend this to other periodics for kops. cc @justinsb |
@@ -752,6 +752,7 @@ def generate_distros(): | |||
kops_channel='alpha', | |||
name_override=f"kops-aws-distro-image{distro}", | |||
extra_dashboards=['kops-distros'], | |||
extra_flags=['--set=spec.assets.containerProxy=registry-sandbox.k8s.io'], |
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.
This will require networking='kubenet'
to work, as any Calico assets will b missing from sandbox.k8s.io
, right?
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.
The only assets concerned are the kubernetes container images from k8s.gcr.io
. PR updated.
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.
Yes, but this setting affects all assets, not just the k8s.gcr.io ones
. Thanks for updating.
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.
@hakman What's the best approach if I want to extend this change to other periodic jobs ? Is this change enough or do I need to make changes per use ?
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.
Most jobs use CNIs (as kubenet style networking is not really a production use case). This means that setting this proxy will not work for that case, unless the proxy is made to proxy CNI repos too.
Most likely path is to decide on a final dns name for the CDN cached registry and switch all kOps manifests to use it during the kOps 1.24 development cycle. We can decide later during that cycle if we want to keep it or revert to k8s.gcr.io
.
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.
Thanks for the help!
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.
My pleasure. Thanks for trying to improve this. I think it will become a huge improvement for many k8s users in the future if successful.
Related: - kubernetes/k8s.io#1834 Test different AWS AMI with registry-sandbox.k8s.io Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
593e796
to
8abf16c
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ameukam, hakman 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 |
@ameukam: Updated the
In response to this:
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. |
Related:
Test different AWS AMI with registry-sandbox.k8s.io
Signed-off-by: Arnaud Meukam ameukam@gmail.com