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
Currently kk automatically create a built-in etcd cluster on master nodes when creating a k8s cluster.
In some scenarios, users may have their own etcd cluster and want to use it in k8s. Can kk support such scenarios?
Describe the solution you'd like
kk should support etcd endpoints configuration.
If there is such a configuration, kk skips the creation of etcd cluster and sets the endpoints to k8s apiserver.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Your current KubeKey version
No response
Describe this feature
Currently kk automatically create a built-in etcd cluster on master nodes when creating a k8s cluster.
In some scenarios, users may have their own etcd cluster and want to use it in k8s. Can kk support such scenarios?
Describe the solution you'd like
kk should support etcd endpoints configuration.
If there is such a configuration, kk skips the creation of etcd cluster and sets the endpoints to k8s apiserver.
Additional information
No response
The text was updated successfully, but these errors were encountered: