Skip to content
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

Multus kubeconfig would be expired in a year #4436

Open
cyclinder opened this issue Dec 25, 2024 · 0 comments · May be fixed by #4393
Open

Multus kubeconfig would be expired in a year #4436

cyclinder opened this issue Dec 25, 2024 · 0 comments · May be fixed by #4393
Assignees
Labels

Comments

@cyclinder
Copy link
Collaborator

Spiderpool Version

all

Main CNI

all

bug description

Currently the multus kubeconfig expires after one year, which prevents the pod from being created, but multus does not provide certificate refreshment, so we need to actively update the kubeconfig.

What did you expect to happen?

No response

How to reproduce it (as minimally and precisely as possible)

No response

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant