-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fork all files needed for kindbase and specify snapshot #9225
Conversation
This is for reference, to be able to combine them
Also fix the 19.10 comment, it hadn't been updated
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund 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 |
---------------- 4 Failures :( ---------------------------- Not sure what those were all about... Flakes ? |
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.
do we really need to bring the kind base docker file ? I feel like it is better to just strart from ubuntu
@@ -47,6 +48,7 @@ BUILD_IMAGE ?= us.gcr.io/k8s-artifacts-prod/build-image/kube-cross:v$(GO_VERSIO | |||
ISO_BUILD_IMAGE ?= $(REGISTRY)/buildroot-image | |||
KVM_BUILD_IMAGE ?= $(REGISTRY)/kvm-build-image:$(GO_VERSION) | |||
|
|||
KIND_BASE_IMAGE_GCR ?= $(REGISTRY)/kindbase:$(KIND_VERSION) |
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 probably makes it more confusing
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.
As I mentioned above, it was a refactoring base
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.
Trying do all changes at once (like in the previous PR), makes it much harder to test - or see what happened.
Hard enough to see what changed between the KIND entrypoint and the new KIC entrypoint, if you ask me ?
I tested this locally using:
and it seems to work properly. |
Yeah, that is the usual story... |
Included in PR #9330 |
This is for reference, to be able to combine them
Copied from https://github.com/kubernetes-sigs/kind/tree/2c0eee40/images/base
Currently the "entrypoint" is overridden with a more recent, and modified, version:
https://github.com/kubernetes/minikube/blob/v1.13.0/deploy/kicbase/entrypoint
Changed from latest greatest 20.04 to a snapshot
Upstream KIND has moved away from Ubuntu LTS and moved on to 20.10 already
Fixes #7788
There is no difference to the actual size being done here, that is a separate story.
Here is the result that comes from rebuilding the image with later apt packages:
This can be used as a refactoring base, together with PR #9135, to combine into one image...
Avoiding the intermediate steps for containerd makes the image smaller and more maintainable.