You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe:
It is hard to remember the format of kubeadm.conf, one can use wrong syntax and find it out
only at the last stages of the provision, when testing it locally.
Describe the solution you'd like:
If possible lets add syntax validation for the kubeadm.conf file, ,maybe its possible to use
containerized kubeadm with dry run option.
The text was updated successfully, but these errors were encountered:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
kubevirt-bot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Feb 8, 2025
Is your feature request related to a problem? Please describe:
It is hard to remember the format of kubeadm.conf, one can use wrong syntax and find it out
only at the last stages of the provision, when testing it locally.
Describe the solution you'd like:
If possible lets add syntax validation for the kubeadm.conf file, ,maybe its possible to use
containerized kubeadm with dry run option.
The text was updated successfully, but these errors were encountered: