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
Pods could/should be scheduled on nodes via pod affinities, these affinities are defined by node labels (key/value pairs).
It will help scheduling pods on the destinations where they should be in a Gitops/declarative manner
Adding the option to assign node labels in CivoKubernetes cluster manifests could look like this:
kind: CivoKubernetes apiVersion: cluster.civo.crossplane.io/v1alpha1 metadata: name: my-production-cluster labels: argocd.civo.crossplane.io/cluster: my-production-cluster-production spec: name: my-production-cluster pools: - id: "app-pool" count: 3 size: g3.k3s.medium labels: - myKey: value - role: worker - id: "data-pool" count: 3 size: g3.k3s.small labels: - myOtherKey: someOtherValue - role: edge
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What problem are you facing?
Pods could/should be scheduled on nodes via pod affinities, these affinities are defined by node labels (key/value pairs).
How could Crossplane help solve your problem?
It will help scheduling pods on the destinations where they should be in a Gitops/declarative manner
Adding the option to assign node labels in CivoKubernetes cluster manifests could look like this:
The text was updated successfully, but these errors were encountered: