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

Question Regarding Cluster API #5

Open
itamar-marom opened this issue May 11, 2023 · 0 comments
Open

Question Regarding Cluster API #5

itamar-marom opened this issue May 11, 2023 · 0 comments

Comments

@itamar-marom
Copy link

There is a problem with CRDs:

  • They are very big and may get to a point where Kubernetes will not allow them (will reach limits like annotation limit)
  • It is very hard to maintain such an object

In my opinion, we need to use Kubernetes' power and capabilities in this:

  • Using ConfigMap and Secret objects for configuration (and adding a Ref to them in the CRD)
  • Creating CRD for a Node and letting the cluster hold only Cluster Level configuration and state

For example in Druid, the DruidCluster should hold the external, the deploymentOrder.
We will have a DruidNode CRD that will hold refs to Configmaps for configuration (like appConfigGroup) and also the Kubernetes relevant spec.

We will need to watch more resources like ConfigMap but this is much more Kubernetes native

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

1 participant