-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Object Names and IDs - Add section for qualified names #47869
Comments
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the The 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-sigs/prow repository. |
/language en |
/sig docs |
I think we should document this, but it belongs elsewhere. https://kubernetes.io/docs/concepts/overview/working-with-objects/names/ is about the |
@sftim is the "qualified name" used elsewhere? Or is it specific to object status type naming? If the latter I agree but if the former, it might be beneficial to stick it in this section. |
I cannot think of a better location for this concept. |
I'd put the explanation in https://kubernetes.io/docs/reference/glossary/ and transclude (eg |
I was having a really rough time trying to figure out where the rules were defined for the
type
property of aPodCondition
. I know underscores are allowed but I didn't find a rule in this part of the docs that mention that_
is allowed.Turns out this is the code that validates that property,
https://github.com/kubernetes/kubernetes/blob/abc056843c030ead11551e13171a4447701db24e/staging/src/k8s.io/apimachinery/pkg/util/validation/validation.go#L42
(via https://github.com/kubernetes/kubernetes/blob/abc056843c030ead11551e13171a4447701db24e/pkg/apis/core/validation/validation.go#L5390)
Which has a really nice explanation of what a qualified name is right above it,
It would be great if this information was included in this particular doc.
The text was updated successfully, but these errors were encountered: