ProviderID for nodes should conform to the general format

[kaoet]

The providerID for nodes is in the format <region>.<instance id> now, but it should be in form <cloudProvider>://<optional>/<segments>/<provider id> as specified in https://github.com/kubernetes/cloud-provider/blob/master/cloud.go#L94.

Other cloud providers are all following this convention:

• AWS: aws:///<zone>/<awsInstanceId>
• GCE: gce://${project-id}/${zone}/${instance-name}
• Tencent Cloud: tencentcloud:///<zone>/<instance-id>

[bittopaz]

This is definitely worth to take a look.

I'm currently working on Alicloud integration with kops, and have to do a hack like this.

[fejta-bot]

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-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.