Book has documentation for features not yet released

[mjnovice]

According to the document, we can specify vnets in a separate resourceGroup but that doesn't seem to be the case.

[CecileRobertMichon]

The book is currently published from the main branch. This feature is available in the main branch but not yet in the latest release (release ETA is this week https://github.com/kubernetes-sigs/cluster-api-provider-azure/milestone/28).

[mjnovice]

@CecileRobertMichon thanks for the clarity, however I see that in the same doc we are referring to

1.2.4, is that just by chance ?

[CecileRobertMichon]

@mjnovice not sure I agree that those two things are in the same doc: one screenshot seems to be coming from https://capz.sigs.k8s.io/ while the other is part of https://cluster-api.sigs.k8s.io/user/quick-start.html, those are two different Netlify websites with each their own publishing pipeline

Since the book is meant to be user-facing, it makes sense to change the default to point to the latest release docs.

[mjnovice]

Sure, thanks @CecileRobertMichon again for the clarification.

[CecileRobertMichon]

/retitle Book has documentation for features not yet released

[CecileRobertMichon]

Previous discussion on the topic for CAPI: kubernetes-sigs/cluster-api#6017

[CecileRobertMichon]

@mjnovice not sure if you're on slack, couldn't find your username, but here's the thread about this: https://kubernetes.slack.com/archives/CEX9HENG7/p1667858516778029

Would love to hear your thoughts as a user who experienced this confusion

[mjnovice]

@CecileRobertMichon added my thoughts on the thread.

[k8s-triage-robot]

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]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[dtzar]

We now have the process to only update the book website for what is current for the last shipped version of CAPZ. The documentation in the main repo itself contains docs for whatever is current in the code repo which gets published at minor release.

It would be nice to have a versioned website, but this is quite a bit of work and out of scope for this issue.

Closing since this is technically resolved now.