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

cluster-workers-scaling job it's changing machineset of infra nodes instead of workers when scaling down after workload #145

Open
skordas opened this issue May 12, 2022 · 1 comment

Comments

@skordas
Copy link

skordas commented May 12, 2022

Example build:
https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/scale-ci/job/e2e-benchmarking-multibranch-pipeline/job/kube-burner/298/

Flow:

  • kube-burner is starting new cluster-workers-scaling job to scale up the cluster.
  • cluster-workers-scaling job is running cluster-post-config to create infra nodes.
  • kube-burner is running workload
  • kube-burner is starting new cluster-workers-scaling job to scale down the cluster.

When my cluster name is ex. skordas - then first machineset on list is infra node

 NAMESPACE               NAME                                   DESIRED   CURRENT   READY   AVAILABLE   AGE
 openshift-machine-api   infra-us-east-2a                       3         0                             22m
 openshift-machine-api   infra-us-east-2b                       0         0                             22m
 openshift-machine-api   infra-us-east-2c                       0         0                             22m
 openshift-machine-api   skordas-511b-fjt5x-worker-us-east-2a   0         40        40      40          3h40m
 openshift-machine-api   skordas-511b-fjt5x-worker-us-east-2b   0         40        40      40          3h40m
 openshift-machine-api   skordas-511b-fjt5x-worker-us-east-2c   0         40        40      40          3h40m
 openshift-machine-api   workload-us-east-2a                    0         1         1       1           22m

so running build to scale down to 3 nodes will set 3 nodes for infra machineset, and rest will be 0

@skordas
Copy link
Author

skordas commented May 12, 2022

Final machineset after scaling down:

 NAMESPACE               NAME                                   DESIRED   CURRENT   READY   AVAILABLE   AGE
 openshift-machine-api   infra-us-east-2a                       3         3                             36m
 openshift-machine-api   infra-us-east-2b                       0         0                             36m
 openshift-machine-api   infra-us-east-2c                       0         0                             36m
 openshift-machine-api   skordas-511b-fjt5x-worker-us-east-2a   0         0                             3h54m
 openshift-machine-api   skordas-511b-fjt5x-worker-us-east-2b   0         0                             3h54m
 openshift-machine-api   skordas-511b-fjt5x-worker-us-east-2c   0         0                             3h54m
 openshift-machine-api   workload-us-east-2a                    0         0                             36m

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

No branches or pull requests

1 participant