-
Notifications
You must be signed in to change notification settings - Fork 114
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
CI fix: switch flannel images from docker to quay.io #826
base: master
Are you sure you want to change the base?
CI fix: switch flannel images from docker to quay.io #826
Conversation
This is to handle the rate limit of docker Signed-off-by: Sebastian Sch <[email protected]>
Thanks for your PR,
To skip the vendors CIs, Maintainers can use one of:
|
Pull Request Test Coverage Report for Build 12570289902Details
💛 - Coveralls |
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.
LGTM
@@ -105,6 +105,43 @@ kcli create cluster generic --paramfile ./${cluster_name}-plan.yaml $cluster_nam | |||
export KUBECONFIG=$HOME/.kcli/clusters/$cluster_name/auth/kubeconfig | |||
export PATH=$PWD:$PATH | |||
|
|||
# w/a switch flannel images to use quay repo to avoid dockerhub pull limit | |||
# [SchSeba] there is a cronjob in place to make a copy of the image between dockerhub and quay account | |||
ds=`kubectl -n kube-flannel get daemonset kube-flannel-ds -oyaml` |
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.
we already have a local registry set right ?
can we deploy k8s without flannel with kcli ?
i wonder if its better to build our own flannel image (make image) from a given release tag of the repo.
then reference it in the flannel ds and deploy. that way we dont rely on private repo (and cron job).
WDYT?
This is to handle the rate limit of docker