Add CRD support to k8s parser#22459
Conversation
2524d58 to
66f6715
Compare
|
hi @tim-werner ; thank you the contribution. I've approved the workflow to run. It looks like there are some minor lint/format errors. You will also need to include a (brief) release note. |
|
hi @cburroughs, |
|
Thanks a lot for this contribution, it does look like something we'd like to have. A couple of things though:
|
|
Hi @alonsodomin , thank you very much for your comment.
|
|
yeah I like the idea, it's something I knew it would come up someday but avoided getting into that can of worms. Regarding the list of CRDs, since you also need to know the class name, maybe a Hashmap is a better option. |
|
Thx. I will look into it. |
|
Hi @alonsodomin, @cburroughs , I have changed the code in such a way that it is now possible to register multiple crds. In addition I have added a section to the Helm Deployment documentation. Please review. Thx. |
|
(hit the CI approval button again)
|
|
Thanks for the contribution. We've just branched for 2.29.x, so merging this pull request now will come out in 2.30.x, please move the release notes updates to |
|
Ahh s... I accidently closed the pull request by trying to sync my fork with the main branch... |
|
I have openend a new pull request with the same name and the fixed conflicts. Maybe you can reopen this pull request as a admin. THx. |
Accidentaly closed: #22459 --------- Co-authored-by: A. Alonso Dominguez <2269440+alonsodomin@users.noreply.github.com>
This will close issue 22445.
It is now possible to add a custom resource definition to the k8s-parser.
In the
crd.pyfile a new CRD has to be defined according to the Hikaru documentation. The base class has to be namedCRD.