-
Notifications
You must be signed in to change notification settings - Fork 202
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
Kured v.1.2 fails on Kubernetes v.1.16 (on prem, kubeadm created) #89
Comments
Hi @HansK-p Did you get it to run on 1.16? |
seems to work if you enable this on your api-servers |
It worked well for me on a kubeadm 1.16 created K8s cluster after I compiled kured using the latest source code. Kured have rebooted my kubernetes nodes more than once without any issues related to kured running on K8s v. 1.16. |
@awh Is it possible to get a new release tagged so kured works on K8s 1.16? |
we need both image and helm chart update. |
Thanks all. You can specify this image tag as an override for the current helm chart Related. |
Please also watch #97 |
@stealthybox . The last docker image seems locked.
|
New error on the image
|
Ok, it seems that we cannot use flags like described in the doc.
This is ok
|
On kubernetes 1.14 I had to add a permission on the Cluster role: - apiGroups: ["apps"]
resources: ["daemonsets"]
verbs: ["get"] |
@nicolas-marcq you can use flags like described in the doc. It looks like you have done the equivalent of
you did:
|
You are right @SerialVelocity |
This does not seem to be working even with the right yaml syntax in 1.2.0. See issue #101 |
@archmangler Why would it work with 1.2.0? It says above you need to use |
I just tested this with 2 node cluster with kubeadm 1.16.2 and kured (master-f6e4062). Any more feedback from other testers? Please speak up, as we'd like to get 1.3.0 out some time soon. |
@dholbach I am currently running Kubernetes |
@onedr0p I know people have tested this already and gave their 👍, but as you'd run this from |
I've been running weaveworks/kured:master-f6e4062 on a v1.17.0 cluster for a few days with start-time and end-time set. Things seems to be working as they should, but so far there has been no reason reboot. So it's not really much of a test - yet. but at least all logs from Kured so far indicates that Kured is working as it should in a Kubeadm configured K8s v1.17.0 cluster. |
Same with @HansK-p post. I have it deployed and the logs don't indicate an issue. Won't know for sure until a reboot is triggered by a security update. |
1.3.0 is out now: https://github.com/weaveworks/kured/releases/tag/1.3.0 🎆 |
awesome thanks! |
Kured v.1.2 fails on my kubeadm created K8s v.1.16.0 cluster. It seems that this issue has been solved by fix #75, which isn't a part of a release yet.
The error message I received before compiling kubed from the latest source was:
It would be really nice to get a kubed release v.1.3 including an updated stable helm chart. This will hopefully make the stable kured helm chart work on a K8s v.1.16 clusters without modifications.
I have not used Kured on older Kubernetes versions (yet).
The text was updated successfully, but these errors were encountered: