📖 book: Use relative links in generate CRDs doc

[sbueringer]

Signed-off-by: Stefan Büringer [email protected]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[sbueringer]

@fabriziopandini I've opened this PR to get the discussion started on how we want to fix it.

I think we don't have to backport the whole #6018 PR as we don't want to v1.1=>v1.2 doc and we don't have to rename the old migration guides.

Instead I propose to make the links in the generate CRDs doc relative. This fix is cherry-pick'able to release-0.3 and release-0.4 as this section of the generate CRDs doc didn't change since release-0.3.

WDYT?

[fabriziopandini]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [fabriziopandini]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sbueringer]

/cherry-pick release-0.3

[sbueringer]

/cherry-pick release-1.0

[k8s-infra-cherrypick-robot]

@sbueringer: #6030 failed to apply on top of branch "release-0.3":

Applying: book: make links in generate CRDS relative
Using index info to reconstruct a base tree...
M	docs/book/src/developer/providers/implementers-guide/generate_crds.md
Falling back to patching base and 3-way merge...
Auto-merging docs/book/src/developer/providers/implementers-guide/generate_crds.md
CONFLICT (content): Merge conflict in docs/book/src/developer/providers/implementers-guide/generate_crds.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 book: make links in generate CRDS relative
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-0.3
/cherry-pick release-0.4

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.

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #6034

In response to this:

/cherry-pick release-1.0

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.

[sbueringer]

/cherry-pick release-0.4

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #6035

In response to this:

/cherry-pick release-0.4

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.