cue.dev: unclear how to find k8s.io curated module packages

[zmitchell]

In the docs for curated modules, there are conflicting modules in the Kubernetes module docs:

• Kubernetes top-level says to use cue.dev/x/k8s.io/api/core/v1
• Getting started with Kubernetes + Cue says to use cue.dev/x/k8s.io/api/apps/v1

I can't actually find cue.dev/x/k8s.io/api/apps/v1 on the Central Registry, but that could be user error. For instance, I tried finding a #Deployment definition, and couldn't find it in the cue.dev/x/k8s.io/api/core/v1 module.

[mvdan]

How did you try finding these packages in the central registry? If you tried searching, that probably didn't work, given that our search is rather basic at the moment, and lots of published schemas include "k8s" or "kubernetes" keywords.

Here you can see all the packages contained by the k8s.io curated module: https://registry.cue.works/docs/cue.dev/x/k8s.io

And it includes both packages you mention:

• https://registry.cue.works/docs/cue.dev/x/k8s.io/api/core/v1
• https://registry.cue.works/docs/cue.dev/x/k8s.io/api/apps/v1

I agree that both should mention apps/v1; it's a higher level and more generally useful package than core/v1.

I also think that our docs should link to the top-level directory view for curated modules with many packages, for the sake of clarity.

Thanks for your input!

[zmitchell]

Yeah I actually searched first, then found the curated module docs, then noticed that apps != core, went back to search and didn’t see apps.

[mxey]

apps and core are two of the API groups in Kubernetes. apps contains objects like Deployment, but you’ll need core for ConfigMaps and others.