-
Notifications
You must be signed in to change notification settings - Fork 233
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
Add keda-crd helm chart #675
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Rubén Laguna <[email protected]>
WDYT @tomkerkhove @zroubalik ? Maybe we can split the CRDs into a new fully isolated chart and deploy that chart as dependency of KEDA (managed by a flag). This could allow installing the CRDs in advantage, without losing the helm support for the chart. |
As per #226, dependency does not work properly |
No no, I meant the CRDs chart as KEDA chart dependecy, not KEDA as user dependency |
I know, but I believe the problem will be the same - There is no guarantee that CRDs are created first nor that they will be updated (biggest issue) |
This would be quite nice to have, what's between here and |
Worth mentioning that Karpenter moved away from Symlinks due to some conflict on updates across major versions. aws/karpenter-provider-aws@a69a377 (Mention since this came from an issue referring to Karpenter) |
I still think that splitting the charts could be quite easy and solves the issues from other people, WDYT @wozniakjan @zroubalik ? |
Maybe include this into a bigger effort with #20 |
Provide a description of what has been changed
Checklist
Fixes kedacore/keda#5575