Add Azure releases to docs

giantswarm / docs

The Giant Swarm documentation site

http://docs.giantswarm.io

Apache License 2.0

4 stars 8 forks source link

Add Azure releases to docs #2261

Closed yulianedyalkova closed 3 months ago

yulianedyalkova commented 3 months ago

What this PR does / why we need it

Now that we have release v25.0.0 for Azure, we also need to start generating docs for it.

Things to check/remember before submitting

If you made content changes
- Run make lint dev to render and proofread content changes locally.
- Bump last_review_date in the front matter header if you reviewed the entire page.

T-Kukawka commented 3 months ago

cc @pipo02mix

pipo02mix commented 3 months ago

wait, but is this CAPZ? Why don't we name the folder capz? That way, we follow the convention capa, capv,...

pipo02mix commented 3 months ago

@yulianedyalkova ?

yulianedyalkova commented 3 months ago

@pipo02mix I was afk :) The longterm plan is to use the names of the providers rather than capa/capz/etc. CAPA was used because of conflicts with vintage but even there we want to eventually go back to just using aws.

pipo02mix commented 3 months ago

and what happens with AKS and pure Azure? or aws and eks?

yulianedyalkova commented 3 months ago

That is a conversation that started in this rfc but there is no final decision yet. Azure vs capz is certain though as capz is just an implementational detail that shouldn't reach customers. So can we move forward with this PR as it's currently blocking us from announcing the azure releases we already have out?