Code change:
it is required by kubectl. When present, the value of this annotation must be a comma separated list of the group-kinds, in the fully-qualified name format, i.e. `<resource>.<group>`. <ins> ### applyset.kubernetes.io/contains-group-resources (deprecated) {#applyset-kubernetes-io-contains-group-resources} Type: Annotation Example: `applyset.kubernetes.io/contains-group-resources: "certificates.cert-manager.io,configmaps,deployments.apps,secrets,services"` Used on: Objects being used as ApplySet parents. For Kubernetes version {{< skew currentVersion >}}, you can use this annotation on Secrets, ConfigMaps, or custom resources if the CustomResourceDefinition defining them has the `applyset.kubernetes.io/is-parent-type` label. Part of the specification used to implement [ApplySet-based pruning in kubectl](/docs/tasks/manage-kubernetes-objects/declarative-config/#alternative-kubectl-apply-f-directory-prune). This annotation is applied to the parent object used to track an ApplySet to optimize listing of ApplySet member objects. It is optional in the ApplySet specification, as tools can perform discovery or use a different optimization. However, in Kubernetes version {{< skew currentVersion >}}, it is required by kubectl. When present, the value of this annotation must be a comma separated list of the group-kinds, in the fully-qualified name format, i.e. `<resource>.<group>`. {{< note >}} This annotation is currently deprecated and replaced by [`applyset.kubernetes.io/contains-group-kinds`](#applyset-kubernetes-io-contains-group-kinds), support for this will be removed in applyset beta or GA. {{< /note >}} </ins> ### applyset.kubernetes.io/id (alpha) {#applyset-kubernetes-io-id} Type: Label

Related discussion:
text: I'm not entirely sure if this is a bug, or if the documentation is just inaccurate/lacking some context, but it's at the very least a bit confusing. If you check the documentation for the well-known labels, etc., you can find the documentation for the annotation . ! However, when I try to reference a parent object with the option to without this annotation, it complains about the annotation missing: At this point my parent resource is declared as: It appears that I can set either one of the two ( or ) on the resource and will accept it; only in the latter case it appears to be copying the "resources" annotation to the add the "kinds" annotation. To phrase it another way: Setting the "kinds" annotation seems like the right way to go (but not what the documentation suggests), and setting the "resources" annotation works as well but you'll also end up with the "kinds" annotation afterwards. I expect the documentation and kubectl to align. Point at a resource that doesn't have the required annotations. No response <details</detailsnocloud No response No response No response No response
/sig docs /sig cli
This was changed in the code by and it seems that document needs changes to reflect this. Thank you bringing this issue /triage accepted
I think this should be transferred to the k/website so that the right annotation is recorded. /transfer wbsite
Something went wrong or the destination repo kubernetes/wbsite does not exist. <detailsIn response to : I think this should be transferred to the k/website so that the right annotation is recorded. /transfer wbsite Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
my bad !! /transfer website
/assign
Due to an implementation error with , in k8s v1.29 release this annotation was deprecated and the same is replaced by annotation. made this changes.
PR Raised .