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

[capi] Building images using the k8s ci artifacts fails #206

Closed
detiber opened this issue Apr 14, 2020 · 2 comments · Fixed by #207
Closed

[capi] Building images using the k8s ci artifacts fails #206

detiber opened this issue Apr 14, 2020 · 2 comments · Fixed by #207
Assignees

Comments

@detiber
Copy link
Member

detiber commented Apr 14, 2020

The list of kubernetes_imgs that we have in images/capi/ansible/roles/kubernetes/defaults.main.yml includes pause.tar, coredns.tar, and etcd.tar, but they are not included in the k8s ci artifacts (since they are built, versioned and distributed separately).

If we want to automate loading of these images, we should likely use a separate variables for their source, type, versions rather than overloading the use of kubernetes_http_source, kubernetes_semver, and kubernetes_source_type

@detiber
Copy link
Member Author

detiber commented Apr 14, 2020

This is causing issues with attempting to use the k8s ci artifacts for building an image here: kubernetes-sigs/cluster-api-provider-gcp#292

/assign @codenrhoden

@codenrhoden
Copy link
Contributor

Discussed this topic with @detiber today.

He's going to try out adding a flag that, even when setting kubernetes_source_type = http, allows you to request that the images not associated with a specific K8s release ('pause', 'coredns', 'etcd') not be pre-loaded. An image built in this way would fall-back to pulling those images on-demand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants