-
Notifications
You must be signed in to change notification settings - Fork 38
Open
Labels
area/devopsNeeds devops code changesNeeds devops code changesbugSomething isn't workingSomething isn't working
Description
To see how your Operator works, is really strange for me.
In the one side it has Cluster Roles but in the other side it is hard connected with one Kestra.
How is your thought about to run multiple kestra with Operator into one Kuberneres?
Solutions
One Operator be instance
This is your current way.
When you still want to use this setup, please change the RBAC away from an ClusterRole and ClusterRoleBinding to Role and RoleBinding.
If you want "watch" multiple Namespace, so set this up with an for-loop over an array of namespaces.
PS: Is your Operator ready to just read a few Manifests of your CRDs not cluster wide?
One Operator for Multiple Instances
Some suggestion:
- Gravitee Operator has a ContextManagement manifest and all other Manifest has an
contextReffields - Prometheus-Operator search Manifest with Labels (and the Prometheus Manifest setup an Instance and the whole part of which namespace and labels are used as selector for e.g PodMonitor or PrometheusRules)
- GrafanaOperator where the Dashboard Manifest has Label Selector which instance (crossNamespace) are selected to deploy. Here an Instance could be just remote Credentials with API-Endpoint
Metadata
Metadata
Assignees
Labels
area/devopsNeeds devops code changesNeeds devops code changesbugSomething isn't workingSomething isn't working