-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
chore: Generate standalone CRDs manifests as part of release process #4814
Conversation
Thank you for your contribution! 🙏 We will review your PR as soon as possible.
While you are waiting, make sure to:
Learn more about: |
ad5d7aa
to
7e809d0
Compare
Signed-off-by: Andy Zawada <[email protected]>
Signed-off-by: Andy Zawada <[email protected]>
7e809d0
to
ee7edcd
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.
LGTM!
Nice improvement 😄
Signed-off-by: Andy Zawada <[email protected]>
Thanks for getting back to this so quickly! And thank you for fixing the title, I think I had a bit of brain fog there. I will fix up docs PR as well |
/skip-e2e |
Thanks for the contribution! ❤️ |
…edacore#4814) Signed-off-by: Yoon Park <[email protected]>
Adding CRD generation to releases, so that they can be installed and managed independently of the helm chart.
Checklist
Fixes #2726