giantswarm / roadmap

Giant Swarm Product Roadmap
https://github.com/orgs/giantswarm/projects/273
Apache License 2.0
3 stars 0 forks source link

Alignment on how to provide CAPZ machine types information #2165

Open marians opened 1 year ago

marians commented 1 year ago

From the discussion in https://github.com/giantswarm/config/pull/1646, we learned that the machine types used for CAPZ differ significantly from the machine types used for Azure.

We currently maintain a list of machine types for Azure in the config repo that is used by happa, and this is used to provide support for displaying machine statistics in the web UI. We should discuss with Team Clippy on how to update and maintain this list (or a separate list), so that we can provide the same support in the web UI for CAPZ.

Suggestions from the issue linked above:

  • expand this list and keep the current ones in
  • update the list and remove/hide what is old and make no sense ( but what impact might this have on existing pools ? )
  • split vintage from capz , have a new list and face this problem again in a year when instances change again ?
marians commented 1 year ago

@weatherhog Will take care of cross-team alignment

kuosandys commented 1 year ago

We discussed this more with Team Clippy in on Slack and have started with a separate list for CAPZ in https://github.com/giantswarm/config/pull/1714

marians commented 1 year ago

I feel this needs some internal documentation so the next person will be able to create and maintain such list. What does the team think?

vvondruska commented 1 year ago

Reopening to add internal docs

marians commented 1 year ago

This is still open because we have practically no documentation on this topic:

As Giant Swarm, i want to make additional instance types / VM sizes / machine types available to the customer/user.

We have a bit of tooling available in https://github.com/giantswarm/machine-types-util for Azure and GCP and there is a bit of instructions, but the entire process needs more explanation.

weatherhog commented 1 year ago

@alex-dabija we need some kind of process for this task. At the moment it causes a lot of work to make additional instance types / VM Sizes / machine types available.

in the end this issue is not urgent

alex-dabija commented 1 year ago

@alex-dabija we need some kind of process for this task. At the moment it causes a lot of work to make additional instance types / VM Sizes / machine types available.

@T-Kukawka Could you take this to Phoenix? I'm not familiar with the differences of Azure instance types on Vintage Azure vs CAPZ.