-
Notifications
You must be signed in to change notification settings - Fork 169
feat: add support for multiple Datastores #961
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
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for kamaji-documentation ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
prometherion
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you already figured out how to create the additional Datastore for the additional resources?
If I understood correctly, the API Server will reuse the same CA and client-based certificate for authentication, unless using a plain/non-TLS etcd which is not supported by Kamaji to be registered as Datastore.
|
I think I'll use ETCD-Operator with Cert-manager to manage the CA for both the primary and additional ETCDs. I'll then create two |
|
We recently merged a PR on Kamaji ETCD Chart which provides support to Cert Manager, it could be useful. Edit: we would need to revamp it in order to reuse the same CA and the same server certificate since these are automatically generated every time. |
Draft implementation of multiple
DatastoresperTenantControlPlane. Based on the discussion with @prometherion here. I'm opening the PR now to gather feedback.Todo: