kubefed icon indicating copy to clipboard operation
kubefed copied to clipboard

Add ability to set kind config in create-clusters.sh

Open mvaalexp opened this issue 3 years ago • 12 comments

What this PR does / why we need it: The create-clusters.sh script only allows for the creation of clusters with a single node. Sometimes there is not enough resources on a single node for testing purposes.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged): Fixes #1472

Special notes for your reviewer:

mvaalexp avatar Nov 10 '21 19:11 mvaalexp

Welcome @mvaalexp!

It looks like this is your first PR to kubernetes-sigs/kubefed 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubefed has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. :smiley:

k8s-ci-robot avatar Nov 10 '21 19:11 k8s-ci-robot

I did not change anything that should have broke the tests here. I seem to not have permissions to re-run either.

mvaal avatar Feb 07 '22 21:02 mvaal

I did not change anything that should have broke the tests here. I seem to not have permissions to re-run either.

try to reopen the pr, then you will trigger the test.

swiftslee avatar Feb 14 '22 07:02 swiftslee

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mvaalexp To complete the pull request process, please ask for approval from hectorj2f after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

k8s-ci-robot avatar Feb 14 '22 15:02 k8s-ci-robot

Anything else I need to do to get this one in? Thanks.

mvaalexp avatar May 03 '22 19:05 mvaalexp

@mvaalexp please rebase this on latest, which is needed for the tests to pass.

irfanurrehman avatar May 10 '22 09:05 irfanurrehman

New changes are detected. LGTM label has been removed.

k8s-ci-robot avatar May 10 '22 15:05 k8s-ci-robot

@mvaalexp Please squash the commits also. Thanks!

irfanurrehman avatar May 11 '22 01:05 irfanurrehman

@mvaalexp Squash commits needed, Thanks!

irfanurrehman avatar May 18 '22 00:05 irfanurrehman

Squashed

mvaalexp avatar May 18 '22 01:05 mvaalexp

@mvaalexp Please rebase.

jimmidyson avatar Aug 10 '22 10:08 jimmidyson

@mvaalexp: PR needs rebase.

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 avatar Aug 10 '22 10:08 k8s-ci-robot

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Nov 08 '22 11:11 k8s-triage-robot

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Dec 08 '22 11:12 k8s-triage-robot

Rebased several times with no response /close

mvaalexp avatar Dec 08 '22 19:12 mvaalexp

@mvaalexp: Closed this PR.

In response to this:

Rebased several times with no response /close

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 avatar Dec 08 '22 19:12 k8s-ci-robot