Skip to content

Operator: Support multiple instances o kestra #147

@wrenix

Description

@wrenix

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 contextRef fields
  • 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

No one assigned

    Labels

    area/devopsNeeds devops code changesbugSomething isn't working

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions