8000 Kured works in kube-system namespace but not with kured namespace · Issue #1131 · kubereboot/kured · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Kured works in kube-system namespace but not with kured namespace #1131

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll 8000 occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
anuas opened this issue May 26, 2025 · 1 comment
Open

Kured works in kube-system namespace but not with kured namespace #1131

anuas opened this issue May 26, 2025 · 1 comment
Labels
help wanted The Kured crew waits for your PR on this topic

Comments

@anuas
Copy link
anuas commented May 26, 2025 •
edited
Loading

I have installed Kured in kube-system namespace in AKS . it works. but I want to intall kured in kured namespace.
Kured installed using

helm install my-release kubereboot/kured --namespace kured --set controller.nodeSelector."kubernetes\.io/os"=linux --version 5.3.2 --set configuration.period=1m

With kured namespace it is just displaying the initial logs as below. not displaying no reboot required

time="2025-05-26T08:10:48Z" level=info msg="Binding node-id command flag to environment variable: KURED_NODE_ID"
time="2025-05-26T08:10:48Z" level=info msg="Kubernetes Reboot Daemon: 1.14.2"
time="2025-05-26T08:10:48Z" level=info msg="Node ID: aks-nodepool02-36406134-vmss00000e"
time="2025-05-26T08:10:48Z" level=info msg="Lock Annotation: kured/my-kured:weave.works/kured-node-lock"
time="2025-05-26T08:10:48Z" level=info msg="Lock TTL not set, lock will remain until being released"
time="2025-05-26T08:10:48Z" level=info msg="Lock release delay not set, lock will be released immediately after rebooting"
time="2025-05-26T08:10:48Z" level=info msg="PreferNoSchedule taint: "
time="2025-05-26T08:10:48Z" level=info msg="Blocking Pod Selectors: []"
time="2025-05-26T08:10:48Z" level=info msg="Reboot schedule: SunMonTueWedThuFriSat between 00:00 and 23:59 UTC"
time="2025-05-26T08:10:48Z" level=info msg="Reboot check command: [test -f /var/run/reboot-required] every 1m0s"
time="2025-05-26T08:10:48Z" level=info msg="Concurrency: 1"
time="2025-05-26T08:10:48Z" level=info msg="Reboot command: [/bin/systemctl reboot]"
time="2025-05-26T08:17:12Z" level=fatal msg="Error testing lock: timed out trying to get daemonset my-kured in namespace kured: Timed out trying to get daemonset my-kured in namespace kured: Get \"[https://192.169.0.1:443/apis/apps/v1/namespaces/kured/daemonsets/my-kured\":](https://192.169.0.1/apis/apps/v1/namespaces/kured/daemonsets/my-kured/%22:) EOF"
@evrardjp
Copy link
Collaborator

One customer of mine is deploying from the helm chart on a kured ns. It works.

We should drill deeper into what's going on.

Are you sure the rbac for the sa is correct ?

@evrardjp evrardjp added question not-bugged This was triaged as not being a bug help wanted The Kured crew waits for your PR on this topic and removed question not-bugged This was triaged as not being a bug labels May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted The Kured crew waits for your PR on this topic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@evrardjp @anuas
0