-
Notifications
You must be signed in to change notification settings - Fork 6
build: Use k8s v1.29.4 as default Kubernetes version #640
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
build: Use k8s v1.29.4 as default Kubernetes version #640
Conversation
@@ -44,7 +44,7 @@ For example, the following command will create a Docker cluster with Cilium CNI | |||
```shell | |||
export CLUSTER_NAME=docker-cluster-cilium-helm-addon | |||
export CLUSTER_FILE=examples/capi-quick-start/docker-cluster-cilium-helm-addon.yaml | |||
export KUBERNETES_VERSION=v1.28.7 | |||
export KUBERNETES_VERSION=v1.29.4 |
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.
Thanks for the reminder, last time I checked the DNS pod was not coming up in a CAPA cluster, I didn't get a chance to debug.
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.
Ah ok. I'll run the e2e and have a look
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.
Yep failure - but why???
$ k --kubeconfig workload-kubeconfig logs -n kube-system coredns-76f75df574-lvqsr
Listen: listen tcp :53: bind: permission denied
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.
I think this is the issue - kubernetes/minikube#18421
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.
I wonder if we should patch containerd config with kubernetes-sigs/kind#2748 (comment) - this is the default in containerd 2.0 btw when it gets released...
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 fixed the issue. I'll open a PR for discussion.
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.
See #645
Update documentation to specify the version when creating the cluster.
25f86e2
to
1abca11
Compare
b210baf
into
jimmi/containerd-unprivileged-ports
Update documentation to specify the version when creating the cluster.
Update documentation to specify the version when creating the cluster.
Update documentation to specify the version when creating the cluster.
Update documentation to specify the version when creating the cluster.