New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRD List Generation #25910
CRD List Generation #25910
Conversation
81336f2
to
f0425a8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Preview at https://deploy-preview-25910--docs-cilium-io.netlify.app/internals/cilium_operator.html#crd-registration: it works great, thanks for this!
There's the CI check missing (see below), but looks good otherwise.
becb089
to
3342a57
Compare
PR #25824 will introduce another CRD ( |
2a58d87
to
83906b2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding the check!
I'm thinking of additional details now, apologies for missing them on the first pass.
-
Can we mark
Documentation/crdlist.rst
as a generated file to GitHub, so that changes are folded by default in the diffs? We need a new entry for the file in.gitattributes
for that, just like forhelm-values.rst
for example. -
Can we also remove ownership for this generated file in
CODEOWNERS
, to avoid team docs-structure to be pulled for review each time the list changes? Again, see the example ofhelm-values.rst
inCODEOWNERS
. Given that CI should catch missing updates, we shouldn't need manual validation for this file.
Please, also rebase your PR on |
83906b2
to
f54cfec
Compare
f54cfec
to
6a8102b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just had the time to observe that the CI check works as expected :) Thanks a lot!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
/test |
6a8102b
to
f523c67
Compare
/test Job 'Cilium-PR-K8s-1.26-kernel-net-next' hit: #25958 (85.99% similarity) |
/test-1.26-net-next Job 'Cilium-PR-K8s-1.26-kernel-net-next' hit: #25958 (94.11% similarity) |
f523c67
to
3b1d6aa
Compare
Running `make generate-crd-docs` in the root project or `make update-crdlist` in Documentation will run the crdlistgen tool. This tool rebuilds the Documentation/crdlist.rst file by looking at the pkg/k8s/apis/cilium.io/client package's CRD List. It will also scan the rst files of Documentation to see if the CRD is being used as a header anywhere to generate a link to it. Signed-off-by: Daniel Hawton <daniel.hawton@solo.io>
3b1d6aa
to
3d5725a
Compare
/test Job 'Cilium-PR-K8s-1.25-kernel-4.19' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.25-kernel-4.19/605/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
/test-1.25-4.19 |
/test-1.25-4.19 |
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: <commit-id>
tag, thenplease add the commit author[s] as reviewer[s] to this issue.
Replaces a manually edited list of CRDs with an automatically generated and included RST.
Running
make generate-crd-docs
in the root project ormake update-crdlist
in Documentation will run the crdlistgen tool. This tool rebuilds the Documentation/crdlist.rst file by looking at the pkg/k8s/apis/cilium.io/client package's CRD List. It will also scan the rst files of Documentation to see if the CRD is being used as a header anywhere to generate a link to it.Fixes: #25750