We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Configurable operator meta issue and design proposal.
As described in the design proposal, we need some tooling to generate yaml specifications of the operator(s) to deploy, including RBAC permissions.
An example (just a draft, can be implemented differently):
# cli sample usage (exact specification TBD) > ./elastic-operator generate --config=operators.yaml # generates one or multiple yaml files ready-to-deploy, including Deployment, ServiceAccount, (Cluster)Roles, (Cluster)RoleBindings, etc.
# sample configuration (exact specification TBD) operators: # manage clusters in namespace "team-A-production" - image: docker.elastic.co/k8s-operators:1.0 roles: ["elasticsearch", "kibana"] managedNamespaces: ["team-A-production"] namespace: "team-A-production" # manage clusters in namespace "team-A-development" - image: docker.elastic.co/k8s-operators:1.1-alpha1 roles: ["elasticsearch", "kibana"] managedNamespaces: ["team-A-development"] namespace: "team-A-development" # manage enterprise licenses in all namespaces - image: docker.elastic.co/k8s-operators:1.0 roles: ["licensing"] clusterWide: true namespace: "elastic-system" # manage CCS/CCR in namespaces "team-A-production" and "team-B-production" - image: docker.elastic.co/k8s-operators:1.0 roles: ["cross-cluster"] managedNamespaces: ["team-A-production", "team-B-production"] namespace: "elastic-system"
The text was updated successfully, but these errors were encountered:
Closing this in favour of #2406
Sorry, something went wrong.
charith-elastic
No branches or pull requests
Configurable operator meta issue and design proposal.
As described in the design proposal, we need some tooling to generate yaml specifications of the operator(s) to deploy, including RBAC permissions.
An example (just a draft, can be implemented differently):
The text was updated successfully, but these errors were encountered: