Broken link in API conventions documentation

[jkaye2012]

Describe the issue

In the API conventions documentation (linked in turn from the official Kubernetes documentation), there is a broken link to a description for DNS_LABEL format on line 88.

I did some brief searches around the repository for this identifiers document to attempt to fix the link myself, but I was unable to find the referenced information.

[jkaye2012]

This would be for the Docs sig, but I don't seem to have the ability to modify the labels.

[jkaye2012]

I believe this may be the correct link for replacement?

https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names

[MadhavJivrajani]

/sig architecture
@jkaye2012 please see https://github.com/kubernetes/design-proposals-archive/blob/main/architecture/identifiers.md as the intended link (design proposals were recently migrated and archived). Feel free to send in a PR!

[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

[jkaye2012]

/remove-lifecycle stale

Linked PR should ideally be merged before closing this

[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

[jkaye2012]

/remove-lifecycle stale

Linked PR should ideally be merged before closing this