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

external etcd path/prefix #7311

Closed
SiimToo opened this issue Nov 20, 2024 · 2 comments
Closed

external etcd path/prefix #7311

SiimToo opened this issue Nov 20, 2024 · 2 comments

Comments

@SiimToo
Copy link

SiimToo commented Nov 20, 2024

Is your feature request related to a problem? Please describe.
Path/prefix is needed for external centralised ETCD. It is for every cluster writes to different path.
Example: /cluster1 /cluster2 etc

Describe the solution you'd like
I would like a parameter like "--datastore-prefix"

Describe alternatives you've considered

Additional context

@dereknola
Copy link
Member

The etcd configuration in RKE2 is for the embedded etcd. If you want to run an external etcd, you can use the experimental Kine option if you want (docs are currently in review for this on the RKE2 docs site), but configuration is completely handled by via standard etcd configuration docs.

@brandond
Copy link
Member

brandond commented Nov 20, 2024

It sounds like you're asking to have the --etcd-prefix apiserver arg respected for keys that RKE2 manages internally, such as the bootstrap key and apiserver endpoints key?

--etcd-prefix string     Default: "/registry"
  | The prefix to prepend to all resource paths in etcd.

This is NOT meant to be used to share a single etcd cluster over multiple Kubernetes clusters, and we do not intend to support use of a single external cluster for multiple RKE2 clusters.

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

No branches or pull requests

3 participants