cloud-provider-azure icon indicating copy to clipboard operation
cloud-provider-azure copied to clipboard

Support VMSS with Flexible orchestration

Open feiskyer opened this issue 3 years ago • 9 comments

Is your feature request related to a problem? Please describe.

VMSS provides flexible orchestration, which would have different behavior from current uniform orchestration. Some changes are required inside cloud provider to ensure it is supported as well.

Describe the solution you'd like in detail

Ensure VMSS Flex virtual machines are characterized as "vmss" type for node pool related features while still using VM APIs to perform disk attach/detach and network profile updates.

Describe alternatives you've considered

Additional context

  • VMSS Flex would be supported in compute API version 2021-03-01
  • Refer VMSS docs https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes#scale-sets-with-flexible-orchestration.

feiskyer avatar May 27 '21 09:05 feiskyer

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 Aug 25 '21 10:08 k8s-triage-robot

/remove-lifecycle stale

feiskyer avatar Aug 25 '21 13:08 feiskyer

this is still pending on new VMSS Flex APIs (together with Go SDK)

feiskyer avatar Aug 25 '21 13:08 feiskyer

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 23 '21 13:11 k8s-triage-robot

Hey, any news on supporting flexible orchestration vmss?

varnastadeus avatar Jan 21 '22 13:01 varnastadeus

/assign

zarvd avatar Feb 24 '22 09:02 zarvd

/unassign

zarvd avatar Apr 12 '22 06:04 zarvd

Hey folks, any progress on this issue?

SnowmanCharles avatar May 09 '22 19:05 SnowmanCharles

/assign

zmyzheng avatar Jul 20 '22 00:07 zmyzheng

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 Oct 18 '22 01:10 k8s-triage-robot

/remove-lifecycle stale

zmyzheng avatar Oct 18 '22 01:10 zmyzheng