-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Extensions to machine status errors #14
Comments
/assign @roberthbailey Can you comment on this issue? Is this still relevant? It's blocking the stable API milestone. |
jayunit100
pushed a commit
to jayunit100/cluster-api
that referenced
this issue
Jan 31, 2020
In the near future we may make selection of CNI available to the users The choice of weave for CNI is based on some available comparison here: https://chrislovecnm.com/kubernetes/cni/choosing-a-cni-provider/ Another factor for choosing weave here is that you don't need to run an additional etcd for the CNI
anusha94
pushed a commit
to anusha94/cluster-api
that referenced
this issue
Jun 29, 2021
…BYOMachine-reconcile-loop Implement byo machine reconcile loop
ykakarap
referenced
this issue
in ykakarap/cluster-api
Mar 31, 2022
Signed-off-by: Stefan Büringer buringerst@vmware.com
abhinavmpandey08
pushed a commit
to abhinavmpandey08/cluster-api
that referenced
this issue
Mar 2, 2023
…i-1.3 ✨ Set hostname for BR nodes
palexster
pushed a commit
to palexster/cluster-api
that referenced
this issue
Mar 21, 2023
…tes-sigs#14) Signed-off-by: Tarun Gupta Akirala <takirala@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @roberthbailey on January 16, 2018 7:13
Extracted from kubernetes-retired/kube-deploy#298 (comment):
Should we add a new
MachineStatusError
ofJoinClusterTimeoutMachineError
(or similar)?Copied from original issue: kubernetes-retired/kube-deploy#503
The text was updated successfully, but these errors were encountered: