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

control-plane-size flag is inconsistent #15559

Closed
prateekgogia opened this issue Jun 29, 2023 · 5 comments
Closed

control-plane-size flag is inconsistent #15559

prateekgogia opened this issue Jun 29, 2023 · 5 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@prateekgogia
Copy link
Contributor

prateekgogia commented Jun 29, 2023

/kind bug

control-plane-size flag is inconsistent in e2e tests deployer vs kops cli - for test deployer it is the number of control plane instance and for kops cli it denotes the instance type (large or 2xlarge etc.)

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 29, 2023
@prateekgogia
Copy link
Contributor Author

Feel free to close in case this is intentional

justinsb added a commit to justinsb/kops that referenced this issue Jul 19, 2023
For consistency with kops create cluster.

It doesn't appear to be used outside this repo, although test-infra
declares KOPS_CONTROL_PLANE_SIZE and that is then passed to our
e2e/scenarios scripts.

Issue kubernetes#15559
justinsb added a commit to justinsb/kops that referenced this issue Jul 19, 2023
For consistency with kops create cluster.

It doesn't appear to be used outside this repo, although test-infra
declares KOPS_CONTROL_PLANE_SIZE and that is then passed to our
e2e/scenarios scripts.

Issue kubernetes#15559
justinsb added a commit to justinsb/kops that referenced this issue Jul 19, 2023
For consistency with kops create cluster.

It doesn't appear to be used outside this repo, although test-infra
declares KOPS_CONTROL_PLANE_SIZE and that is then passed to our
e2e/scenarios scripts.

Issue kubernetes#15559
justinsb added a commit to justinsb/kops that referenced this issue Jul 19, 2023
For consistency with kops create cluster.

It doesn't appear to be used outside this repo, although test-infra
declares KOPS_CONTROL_PLANE_SIZE and that is then passed to our
e2e/scenarios scripts.

Issue kubernetes#15559
justinsb added a commit to justinsb/kops that referenced this issue Jul 29, 2023
For consistency with kops create cluster.

It doesn't appear to be used outside this repo, although test-infra
declares KOPS_CONTROL_PLANE_SIZE and that is then passed to our
e2e/scenarios scripts.

Issue kubernetes#15559
justinsb added a commit to justinsb/kops that referenced this issue Jul 29, 2023
For consistency with kops create cluster.

It doesn't appear to be used outside this repo, although test-infra
declares KOPS_CONTROL_PLANE_SIZE and that is then passed to our
e2e/scenarios scripts.

Issue kubernetes#15559
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 23, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 22, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants