Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

Bump sigs.k8s.io/kind from 0.7.0 to 0.8.1 #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link

Bumps sigs.k8s.io/kind from 0.7.0 to 0.8.1.

Release notes

Sourced from sigs.k8s.io/kind's releases.

v0.8.1

This is a tiny patch release to pick up the fix for Can't create ipv4 clusters if ipv6 is disabled at kernel level.

For full release notes please see v0.8.0.

Most users will not need to upgrade to this release, this bug is only known to occur on hosts with the ipv6.disable=1 kernel parameter.

v0.8.0

v0.8.0 Most importantly brings persistent clusters that automatically come back up after dockerd / host restarts. It also brings a number of fixes to networking in general, experimental podman backend support, improved failure output, and more.

Breaking Changes

  • The default node image is a Kubernetes v1.18.2 image: kindest/node:v1.18.2@sha256:7b27a6d0f2517ff88ba444025beae41491b016bc6af573ba467b70c5e8e0d85f
  • KIND v0.8.0 requires node images built with v0.8.0+.
    • These new images should be mostly backwards compatible for kind v0.5.0+
  • The default docker network for nodes is now kind instead of the default docker bridge
    • This enabled many fixes, however if you were running things alongside kind you may need to pass --net=kind
    • Your host DNS resolver should just work now ™️ in many cases
    • IPv6 clusters no longer require modifying docker daemon config
    • Docker networks must have a free IPv6 /64 in the [ULA] range, that is you may not create other docker networks consuming the entire ULA range. You can work around this by precreating the kind network with some totally other range if you wish.
  • You may need to migrate to the new featureGates config field when setting feature gates, this should be easier to use though!

NOTE: If you've been experimenting with kind > v0.7.0 installed from HEAD, you may need to docker network rm kind before creating IPv6 clusters.

New Features

  • Clusters should not be broken by dockerd restarts / restarting your host!
  • Host DNS should just work ™️
  • IPv6 Clusters no longer require modifying docker daemon settings
  • Kubernetes 1.18+ should work on hosts using the iptables nft backend
  • kind delete clusters --all for deleting all your clusters
  • New top level featureGates field in Cluster config for enabling feature gates
  • Upgraded dependencies broadly, including library packages, go, containerd, CNI, etc...
  • NO_COLOR ([no-color.org]) support
  • Experimental podman support
    • These clusters do not survive host reboots
    • Requires rootful mode
    • Experimental
  • Improved output on failures, including command output without needing to set -v
  • Experimentally cross-building the base image for AMD64 + ARM by default
  • More Documentation! Guide to working with KIND offline, Ingress and more!
  • New download host and experimental nightly builds
  • Support for Dynamic PV in Kubernetes 1.11.X
  • New top level featureGates config option for controlling cluster featuregates
... (truncated)
Commits
  • 1170b6b version v0.8.1
  • e1388af Merge pull request #1545 from BenTheElder/ipv6-whee
  • 903ad95 handle hosts that cannot create ipv6 networks by falling back to ipv4 only
  • 1a93b0d Merge pull request #1542 from BenTheElder/fix-registry
  • e05fb15 add tilt docs link
  • daa1c81 simplify script for v0.8
  • 4f9eca2 annotate nodes for tilt
  • ab3205d fix kind-with-registry for v0.8
  • 38f9bf5 Merge pull request #1528 from ameukam/update-base-image
  • ea8bec8 bump base image
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [sigs.k8s.io/kind](https://github.com/kubernetes-sigs/kind) from 0.7.0 to 0.8.1.
- [Release notes](https://github.com/kubernetes-sigs/kind/releases)
- [Commits](kubernetes-sigs/kind@v0.7.0...v0.8.1)

Signed-off-by: dependabot-preview[bot] <[email protected]>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label May 4, 2020
@cf-gitbot
Copy link
Collaborator

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/172647307

The labels on this github issue will be updated when the story is started.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file unscheduled
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant