-
Notifications
You must be signed in to change notification settings - Fork 109
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
CRDs helm subchart #2035
CRDs helm subchart #2035
Conversation
Hi @cheina97. Thanks for your PR! I am @adamjensenbot.
Make sure this PR appears in the liqo changelog, adding one of the following labels:
|
a891e37
to
abc84fd
Compare
742a55d
to
4bff11d
Compare
/hold |
Waiting for #1994 |
abc84fd
to
760021d
Compare
402343d
to
9e2d69f
Compare
0b3f082
to
5a75336
Compare
a595693
to
d4a4834
Compare
d4a4834
to
4a6ecfe
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.
You should include the crd chart as a subchart of the main one.
Additionally, we should add the action to publish the chart.
4a6ecfe
to
42ed829
Compare
The crds chart is included inside the original chart, this means that is not necessary to publish another chart |
/test |
42ed829
to
1ab488b
Compare
/test |
1ab488b
to
a998d8e
Compare
/test |
5a75336
to
63e2afd
Compare
a998d8e
to
a5148fb
Compare
Description
This PR creates a dedicated Helm Sub Chart for Liqo CRDS.
This avoids problems with Helm Chart Size Limitations encountered with new network API.
https://azure.github.io/azure-service-operator/design/adr-2023-02-helm-chart-size-limitations/