Bump sigs.k8s.io/kind from 0.8.1 to 0.9.0

[dependabot]

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

Release notes

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

v0.9.0

v0.9.0 Focuses on stability enhancements following v0.8.0 / v0.8.1, a new wave of features will ship in v0.10.0.

Breaking changes have been kept to a minimum, primarily that Kubernetes v1.12.X is no longer supported to make way for some fixes requiring beta-grade kubeadm.

• The default node image is a Kubernetes v1.19.1 image: kindest/node:v1.19.1@sha256:98cf5288864662e37115e362b23e4369c8c4a408f99cbc06e58ac30ddc721600
• Node images built with kind v0.9.0 require using kind v0.9.0+.
  • These images should mostly work with older releases but may not work offline.
  • Images from kind v0.8.0+ should still work but lack some internal improvements
• Support has been dropped for Kubernetes older than v1.13.0.
  • A detailed support policy is in the works. The Kubernetes project only supports v1.16+ currently.
• Building Kubernetes with bazel will only work with Kubernetes v1.15+
  • Building without bazel still works back to v1.13.0
• v1alpha3 kind config is no longer supported. Please upgrade to v1alpha4 (which was already the current version in previous releases)
• Capital letters in cluster names are explicitly rejected by kind, in order to prevent encountering upstream issues with name validation

• NFS volumes should now work
• Kubernetes RuntimeConfig is now first class in kind config
• Upgraded dependencies across the board
• Nodes now have a tenative providerID value set. We commit to the kind:// prefix but the rest of the contents may change.
• The base image is tentatively multi-arch by default. The node image is still not as of yet.
• More values are automatically included in no_proxy when proxies are detected
• The default CNI shoult automatically match MTU to the underlying bridge
• Binaries are now stripped of debugger (not stacktrace) info for smaller binaries

New Node images have been built for kind v0.9.0, please use these exact images (IE like v1.19.1:@sha256:98cf5288864662e37115e362b23e4369c8c4a408f99cbc06e58ac30ddc721600 including the digest) or build your own as we may need to change the image format again in the future 😅

Images built for this release:

• 1.19: kindest/node:v1.19.1@sha256:98cf5288864662e37115e362b23e4369c8c4a408f99cbc06e58ac30ddc721600
• 1.18: kindest/node:v1.18.8@sha256:f4bcc97a0ad6e7abaf3f643d890add7efe6ee4ab90baeb374b4f41a4c95567eb
• 1.17: kindest/node:v1.17.11@sha256:5240a7a2c34bf241afb54ac05669f8a46661912eab05705d660971eeb12f6555
• 1.16: kindest/node:v1.16.15@sha256:a89c771f7de234e6547d43695c7ab047809ffc71a0c3b65aa54eda051c45ed20
• 1.15: kindest/node:v1.15.12@sha256:53ca8a3f446b0751019d522066ce844f6281ffb5b15e9605cd8940176abf4c76
• 1.14: kindest/node:v1.14.10@sha256:ce4355398a704fca68006f8a29f37aafb49f8fc2f64ede3ccd0d9198da910146
• 1.13: kindest/node:v1.13.12@sha256:1c1a48c2bfcbae4d5f4fa4310b5ed10756facad0b7a2ca93c7a4b5bae5db29f5

• Limited fixes related to HA mode and restart support
• Fixed issues with ipv6 network overlap
• Fixed bugs with NO_PROXY generation
• Mitigated issues with concurrent cluster creation on clean hosts
• KUBECONFIG writing has retries to mitigate concurrency / locking issues
• Docker data root on ZFS should be fixed
• Fixed building with bazel in kubernetes 1.20 development

Commits

• 0ff469a version v0.9.0
• 8a77854 bump base image to v1.19.1
• 295318a Merge pull request #1831 from BenTheElder/no-dupe-networks
• 0fc4229 fix minor parsing bug, add unit test for network sorting, minor cleanup and docs
• c4359a9 Merge pull request #1844 from mikedanese/bzl
• 5be1881 explicitly ignore best-effort cleanup in integration test
• 4a98c10 drop parsing / comparing created time
• 4be20e2 use kube::util::find-binary to find kubectl
• 37c741d use inspect to sort networks
• 017b19b add network integration test
• Additional commits viewable in compare view

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

[Zerpet]

Kind 0.9.0 defaults to Kubernetes 1.19. We should make sure we are compatible before merging this PR.

[coro]

Looks like the system tests no longer pass when targeting a 1.19 cluster:

STEP: updating enabled plugins when additionalPlugins are modified
• Failure [32.520 seconds]
Operator
/home/coro/workspace/cluster-operator/system_tests/system_tests.go:30
RabbitMQ configurations
/home/coro/workspace/cluster-operator/system_tests/system_tests.go:118
keeps rabbitmq server related configurations up-to-date [It]
/home/coro/workspace/cluster-operator/system_tests/system_tests.go:136
Unexpected error:                
<*errors.StatusError | 0xc000324460>: {
ErrStatus: {
TypeMeta: {Kind: "", APIVersion: ""},
ListMeta: {
SelfLink: "",
ResourceVersion: "",
Continue: "",
RemainingItemCount: nil,
},
Status: "Failure",
Message: "configmaps \"config-rabbit-rabbitmq-plugins-conf\" not found",
Reason: "NotFound",
Details: {
Name: "config-rabbit-rabbitmq-plugins-conf",
Group: "",
Kind: "configmaps",
UID: "",
Causes: nil,
RetryAfterSeconds: 0,
},
Code: 404,
},
}
configmaps "config-rabbit-rabbitmq-plugins-conf" not found
occurred
/home/coro/workspace/cluster-operator/system_tests/system_tests.go:146

[coro]

I can now no longer reproduce this.

[Zerpet]

@dependabot merge