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.

Sign up for GitHub

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

Jump to bottom

Scale tornado #1742

Closed
alex-dabija opened this issue Dec 6, 2022 · 1 comment
Closed

Scale tornado #1742

alex-dabija opened this issue Dec 6, 2022 · 1 comment
Assignees
@AverageMarcus
Labels
area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service kind/task provider/cluster-api-aws Cluster API based running on AWS topic/capi

Comments

@alex-dabija
Copy link

alex-dabija commented Dec 6, 2022 •
edited
Loading

Task

Scale tornado because the worker nodes are running out of CPU. Either bump the instance type to the next size or add additional nodes.

The following instance types are used by the cluster:

  • control plane nodes: m5.xlarge;
  • worker nodes: m5.xlarge.

Resources
@alex-dabija alex-dabija added area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service team/hydra topic/capi provider/cluster-api-aws Cluster API based running on AWS kind/task labels Dec 6, 2022
@alex-dabija alex-dabija changed the title Scale up tornado Scale tornado Dec 6, 2022
@AverageMarcus
Copy link
Member

Scaled all three machinepools to have a min of 2 replicas (needed anyway for upgrade stability).

@alex-dabija alex-dabija mentioned this issue Dec 13, 2022
Closed
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AverageMarcus AverageMarcus

Labels
area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service kind/task provider/cluster-api-aws Cluster API based running on AWS topic/capi
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alex-dabija @AverageMarcus