Update obsolete links to kubernetes.io/docs/user-guide in Go structs descriptions in apps packages

[aerfio]

What type of PR is this?

/kind cleanup
/kind documentation

What this PR does / why we need it:

Partly supersedes #116107

This PR updates the links to http://kubernetes.io/docs/user-guide in various resources/structs' descriptions which are no longer valid, to their new equivalents. Those descriptions are useful because:

• they are part of documentation, duh
• developers that use k8s.io/api structs in their own CRDs "inherit" those docs too
• those links are visible in the output of kubectl explain, which is now broken, see example, rg used only to highlight the link

The issue was found when we were validating the links in the documentation generated from CRD yamls (generated via controller-gen, and I suspect that a lot of projects generate those docs too, see

• https://github.com/ahmetb/gen-crd-api-reference-docs#current-users
• https://github.com/elastic/crd-ref-docs
• https://doc.crds.dev/
• etc

All of the links have been also updated to use https instead of http.

Those links used to work, but the kubernetes/website#39143 removed those redirects.

Which issue(s) this PR fixes:

Special notes for your reviewer:

I used make update to regenerate the .proto and openapi files, I hope that's enough. If this PR is too big I can split it into smaller parts

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Hi @aerfio. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-triage-robot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[alculquicondor]

/ok-to-test

[alculquicondor]

/label api-review

[alculquicondor]

Suggested change

	// actual number of observed instances of the scaled object.
	// replicas is the number of observed instances of the scaled object.

If you find other instances like this, please fix. The first word should match the name of the field (in lowerCamelCase)

[aerfio]

Sure, I'll fix it in the next week 👍🏻

[aerfio]

Hmm I've updated most of the prefixes in that file, but this review suggestion seems to enlarge this PR several times 😢 I've left some comment like they were because they are the same throughout the whole codebase, e.g

kubernetes/staging/src/k8s.io/api/apps/v1beta1/types.go

Line 67 in d1877f5

// Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata.

is the same in 20+ places, but technically should be adjusted.

Should I fix also the v1beta2 file or just revert the d1877f5 and introduce only fixes to the links? I've 3 other PRs where I only fix the links:

1. Update obsolete links to kubernetes.io/docs/user-guide in Go structs descriptions in kubelet packages #116115
2. Update obsolete links to kubernetes.io/docs/user-guide in Go structs descriptions in corev1 packages #116113
3. Update obsolete links to kubernetes.io/docs/user-guide in Go structs descriptions in autoscaling packages #116109
   and 2 of them got LGTM'd.

I'm also fine with fixing those comments but I'd like to know the scope of this :D

[cici37]

/remove-sig api-machinery

[liggitt]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 4d33bc8059e9ecc982a7d4acd537afe1dfc6e71a

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aerfio, liggitt

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:

• pkg/generated/openapi/OWNERS [liggitt]
• staging/src/k8s.io/api/OWNERS [liggitt]

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

[fedebongio]

/triage accepted