Skip to content

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

Conversation

jimmidyson
Copy link
Member

Update documentation to specify the version when creating the cluster.

@jimmidyson jimmidyson requested review from dkoshkin and msdolbey May 9, 2024 13:50
@jimmidyson jimmidyson enabled auto-merge (squash) May 9, 2024 13:50
@@ -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
Copy link
Contributor

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.

Copy link
Member Author

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

Copy link
Member Author

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

Copy link
Member Author

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

Copy link
Member Author

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...

Copy link
Member Author

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.

Copy link
Member Author

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.
@jimmidyson jimmidyson force-pushed the jimmi/default-e2e-k8s-version branch from 25f86e2 to 1abca11 Compare May 9, 2024 19:38
@jimmidyson jimmidyson changed the base branch from main to jimmi/containerd-unprivileged-ports May 9, 2024 19:38
@jimmidyson jimmidyson merged commit b210baf into jimmi/containerd-unprivileged-ports May 9, 2024
18 checks passed
@jimmidyson jimmidyson deleted the jimmi/default-e2e-k8s-version branch May 9, 2024 19:38
jimmidyson added a commit that referenced this pull request May 14, 2024
Update documentation to specify the version when creating the cluster.
jimmidyson added a commit that referenced this pull request May 20, 2024
Update documentation to specify the version when creating the cluster.
jimmidyson added a commit that referenced this pull request May 21, 2024
Update documentation to specify the version when creating the cluster.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants