-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Update KIND to v0.21.0 and document upgrade process #8977
Comments
/assign |
/triage accepted |
/unassign /help This should be done during the next KIND release to ensure we have a single PR linked somewhere showing how to bump the KIND version. |
@killianmuldoon: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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. |
@kubernetes-sigs/cluster-api-release-team maybe a task someone might be interested in picking up? |
/assign |
/reopen Do we have to improve docs (as the title / description says)? |
@chrischdi: Reopened this issue. 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. |
ah right -- i can open a followup PR, will update the k8s upgrade issue template with a link to this most recent kind bump pr. anything else that should be added? maybe some note about incrementing the Mode in the mapper file when there is a code change required in the Docker provider? |
👍 That sounds awesome. Thanks! |
Since changes made to support KIND
v0.20.0
- #8908 - the process for updating KIND as a dependency has gotten more complicated. This process should be correctly documented so the change can be done in future in a single PR.This should include:
I may have forgotten / missed something in the above. My intention is to complete this work as part of the update to KIND v0.21.0 - the resulting documentation is likely to just be that PR and a link to the PR in some relevant place - possibly the release guide.
Note: KIND v0.21.0 has now been released https://github.com/kubernetes-sigs/kind/releases/tag/v0.21.0
/kind documentation
The text was updated successfully, but these errors were encountered: