Summary

The old crd-puller existed because our discovery works based on GK, not like kcp's crd-puller, which works based on GR. However just dumping a CRD is not super helpful by itself and since the agent can now export multiple versions in a CRD, the difference between ours and kcp's pullers is diminishing.

So I propose we replace the puller with a more generic toolkit that offers tailormade commands for the agent. In the current iteration it supports one single command: crd.

So what was crd-puller Certificate.cert-manager.io is now pubres-toolkit crd mypubres.yaml, with a PublishedResource YAML file being the source. The main advantage here is that we do not just pull the CRD, but also project it (i.e. optionally change its Kind and whatnot). To simulate how exactly a PubRes works is kinda neat to have.

The command has two flags:

• --ars outputs an APIResourceSchema instead
• --no-projection disables the projection rules (turning it into the old crd-puller, basically)

I would also like to see a sync command, which will perform a simulated sync, outputting what resources it sees and which it will create on the local service cluster side.

What Type of PR Is This?

/kind feature

Release Notes

Replace `crd-puller` with a more powerful `pubres-toolkit`.