--cloud-provider cannot be empty

Question

--cloud-provider cannot be empty

paullaffitte opened this issue 4 years ago · comments

Using one of the sample main results in an error --cloud-provider cannot be empty with an exit status 1. Specifying this flag doesn't change anything.

Andrew Sy Kim · Answer 1 · Thu Jan 14 2021 20:53:43 GMT+0800 (China Standard Time)

/assign @cici37

Marc Falzon · Answer 2 · Tue Mar 23 2021 00:37:16 GMT+0800 (China Standard Time)

Any news on this issue @cici37 @andrewsykim?

Cici Huang · Answer 3 · Tue Mar 23 2021 01:48:28 GMT+0800 (China Standard Time)

The fix is merged in upstream (kubernetes/kubernetes#98210)
There are some workaround samples in this issue: #44
Without the fix, this issue could be addressed by reconstruct cobra command in cloud provider repo.

Cici Huang · Answer 4 · Fri Apr 09 2021 04:33:36 GMT+0800 (China Standard Time)

Update: The fix was cherry picked to 1.20 release: kubernetes/kubernetes#100722

fejta-bot · Answer 5 · Thu Jul 08 2021 05:17:20 GMT+0800 (China Standard Time)

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

Kubernetes Triage Robot · Answer 6 · Sat Aug 07 2021 06:17:21 GMT+0800 (China Standard Time)

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

Kubernetes Triage Robot · Answer 7 · Mon Sep 06 2021 06:19:56 GMT+0800 (China Standard Time)

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:

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

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

/close

Kubernetes Prow Robot · Answer 8 · Mon Sep 06 2021 06:20:12 GMT+0800 (China Standard Time)

@k8s-triage-robot: Closing this issue.

In response to this:

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:

Reopen this issue or PR with /reopen

Mark this issue or PR as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

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

/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.