Previously, we would publish CRDs without description to avoid issues when doing client-side applies (e.g. kubectl doesn't like long descriptions).
During the last meeting, we discussed that, with server-side applies, we don't expect to see any issues. Thus the PR.
Changes:
remove separate set of CRDs that was used for generating API documentation;
point crdoc at config/crd/bases;
adjust controller-gen commands to generate full CRDs;
use server-side apply in deploy and deploy-chainsaw.
Previously, we would publish CRDs without description to avoid issues when doing client-side applies (e.g. kubectl doesn't like long descriptions). During the last meeting, we discussed that, with server-side applies, we don't expect to see any issues. Thus the PR.
Changes:
crdocatconfig/crd/bases;controller-gencommands to generate full CRDs;deployanddeploy-chainsaw.Fixes: #1567