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

Kubernetes Operator Support #173

Open
vpatil-tibco opened this issue Feb 19, 2021 · 1 comment
Open

Kubernetes Operator Support #173

vpatil-tibco opened this issue Feb 19, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@vpatil-tibco
Copy link
Collaborator

Context
Need support for Kubernetes Operator. Following are the highlights around what this operator should support at the minimum,

  1. Ability to dynamically scale BE nodes (cache/inference) based on resource (memory/cpu) thresholds.
  2. Ability to distribute BE nodes evenly across resources (hardware/boxes/etc). Should apply to both scale up and scale down.
  3. Ability to replace dead/unrecoverable nodes.
  4. Ability to update Replication count.
  5. Ability to perform Back/Restore via Velero.

Alternatives
No alternatives/workarounds today.

Has the feature been requested before?
No

If the feature request is approved, would you be willing to submit a PR?
Yes

@vpatil-tibco vpatil-tibco added the enhancement New feature or request label Feb 19, 2021
@rameshpolishetti
Copy link
Collaborator

All listed asks are feasible using Kubernetes OOB capabilities and currently made available using helm chart.

Details:

  • Point 1: Made available using helm chart using K8S Horizontal Pod Auto scale feature. It can be enabled/disabled through values.yaml
  • Point 2: Made available using helm chart using K8S Affinity/Anti Affinity feature. It can be enabled/disabled through values.yaml
  • Point 3 & 4: Made available using helm chart using K8S StatefulSet replica count. It can be controlled through values.yaml (Agents replicas)
  • Point 5: User can always perform Backup/Restore using Velero directly.

Operator can be added in the future as required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants