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

clusterctl: Replica count env vars are not used #2560

Closed
wfernandes opened this issue Mar 6, 2020 · 3 comments · Fixed by #2597
Closed

clusterctl: Replica count env vars are not used #2560

wfernandes opened this issue Mar 6, 2020 · 3 comments · Fixed by #2597
Assignees
Labels
area/clusterctl Issues or PRs related to clusterctl kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.
Milestone

Comments

@wfernandes
Copy link
Contributor

What steps did you take and what happened:

  1. Use the following cluster-template.yaml
  2. Move this file to the appropriate location in the overrides directory
    • /Users/wfernandes/.cluster-api/overrides/infrastructure-aws/v0.5.0/cluster-template-kcp.yaml
  3. Set the aws provider url in ~/.cluster-api/clusterctl.yaml
    •   name: "aws"
        url: "/Users/wfernandes/.cluster-api/overrides/infrastructure-aws/v0.5.0/infrastructure-components.yaml"
        type: "InfrastructureProvider"
      
  4. After setting all the required env vars including CONTROL_PLANE_MACHINE_COUNT and WORKER_MACHINE_COUNT, run clusterctl config cluster kcp-test --flavor kcp.
  5. Notice that the values of the replicas are 1 and 0 respectively. Which are the defaults of the flags --control-plane-machine-count and --worker-machine-count.
  6. If the flags are used, then the replicas are set correctly.

What did you expect to happen:
Expected that the COUNT env var values to be used.

/kind bug
/area clusterctl

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. area/clusterctl Issues or PRs related to clusterctl labels Mar 6, 2020
@vincepri
Copy link
Member

vincepri commented Mar 6, 2020

/milestone v0.3.x

@k8s-ci-robot k8s-ci-robot added this to the v0.3.x milestone Mar 6, 2020
@gab-satchi
Copy link
Member

/assign

@gab-satchi
Copy link
Member

/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Mar 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/clusterctl Issues or PRs related to clusterctl kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.
Projects
None yet
4 participants