community
community copied to clipboard
kubernetes
Broken link in API conventions documentation
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.
This would be for the Docs sig, but I don't seem to have the ability to modify the labels.
I believe this may be the correct link for replacement?
https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names
/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!
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
/remove-lifecycle stale
Linked PR should ideally be merged before closing this
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
/remove-lifecycle stale
Linked PR should ideally be merged before closing this
@divya-mohan0209: Closing this issue.
In response to this:
Per this comment on the linked PR that has been closed now, the redirect is intentional. /close
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.
