Closed malagant closed 1 month ago
I'm not on the PC at the moment so I can't analyze it. I will be back next week. But I could imagine that it is related to cilium versions conflict.
That's something I need to take a closer look at anyway... The latest kubernetes version requires cilium 1.16.0.
It is possible to customize the cilium version via parameter.
Adding the following no longer throws the error:
module "talos" {
...
cilium_version = "1.15.7"
}
The problem is:
In this module cilium is used with the latest
version. This is not a good idea, because an error like this can occur.
Version 1.16.0
was recently released and is not compatible with k8s 1.29.7
.
Cilium must always be used in combination with a suitable Kubernetes version: https://docs.cilium.io/en/stable/network/kubernetes/compatibility/
Follow up tasks:
I was wrong: It is not directly because of cilium... but it seems that in version 1.16.0
a new check of helm
is used. I can't say exactly how it works, but there is the possibility to specify a kubernetes version in the terraform resource helm_template
. This solves the problem. I make sure that from now on a default value is always set in the version.
:tada: This issue has been resolved in version 2.8.10 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
I created a
main.tf
file with the following content and did aterraform init
andterraform plan
with the following content:I changed the token for opening this issue ;)
Any hint for me where this error might come from?