-
Notifications
You must be signed in to change notification settings - Fork 903
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
karmada will support distribution of helm afterwards? #861
Comments
Sure, I knew this is in plan and the helm chart has done. |
Related issue #323 |
@lfbear sorry,Maybe my previous expression is not accurate enough. I meant to distribute the helm application to the Member cluster through Karmada, not install Karmada through helm. |
Oh, I see. That seems a good demand, @RainbowMango What do you think |
In general scenarios, users can deploy applications in the following three ways
Kubernetes yaml is usually used for the distribution of a single resource, but in real customer scenarios, applications usually include not only one workload (deployment, daemonset, etc.), but also RBAC, configmap, secret, and multiple deployments, etc. At present, the open source community already has some open source projects similar to helm CRD,such as |
Yes. Karmada will support helm chart propagating, but no clear solution yet. |
The following is an example of karmada distribution of Helm Charts by helm-operator
apiVersion: policy.karmada.io/v1alpha1
kind: ClusterPropagationPolicy
metadata:
name: crd-propagation
spec:
resourceSelectors:
- apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
name: helmreleases.helm.fluxcd.io
placement:
clusterAffinity:
clusterNames:
- member1
- member2
kind: HelmRelease
metadata:
name: jaeger-operator
namespace: default
spec:
chart:
repository: $url
name: jaeger-operator
version: 2.12.3
Which one do you prefer? @RainbowMango |
Can we consider this third-party application package management tool (such as helm) for a unified abstraction, because I know that in addition to helm, there are other management tools such as kustomzie. We should minimize the CRD definition inside karmada, They should be included in a generic CRD. |
tools:flux
Install the toolkit controllers in the flux-system namespace:
tips:
helm
kustomize
|
@RainbowMango Please Take A Look.This demo is just basic functionality, I can prepare more demos if you need to learn more about Flux's functionality. |
Pretty good after a quick look!!! |
I'll look into it and try it on my side and get back to you. Many thanks. |
I think we can add a document at
How do you think @learner0810 ? And would like to do it? |
I agree with the idea. I would be more than happy to complete this document |
Thanks, hard to say this is the only way we support helm chart propagation, but it's a very very good start! |
Hi @learner0810 |
I am very sorry. I've been very busy lately, so the document is not ready yet, can you put it in the next version? |
Really interested with |
I am very sorry that I am writing this work guide. You can look at other issues and say sorry again |
It doesn't matter. Looking Forward to your contribution. |
kindly ping @learner0810 |
Hi @learner0810 Are you still working on this? |
I see that someone has mentioned the distribution of helm PR, this document is not needed, I closed this issue, what do you think? |
#1881 is trying an experimental approach that saves the efforts to deploy flux components onto member clusters. This issue demonstrates how to integrate flux with Karmada, that's a useful option too. |
I see, thanks. I will finish the document by the weekend. |
Thanks We are going to cut a new release by the end of this week(probably this Saturday), hope this document could be included in this release. |
What would you like to be added:
Why is this needed:
karmada is doing application distribution, currently most applications are delivered via helm charts, does karmada have any plans to support distribution charts?
OCM supports installing applications as Helm Chart and loading remote Chart repositories.
The text was updated successfully, but these errors were encountered: