You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, we can create only one celeborn cluster for flink when deploying on K8S in one namespace. In some scenarios, this is not very convenient. Supposing we have two resource pools divided by business type in the same k8s namespace,we have no way to create a celeborn cluster for both of the two resource pools.
Describe the solution you'd like
For each celeborn cluster, we introduce a single values.yaml file that contains all the necessary configs for creating it, and we can create the cluster using the following helm command
…8s namespace
### What changes were proposed in this pull request?
Use built-in helm var {{ .Release.Name }} to naming kubernetes resources, default with user input `celeborn`
close#1762
```
helm install celeborn charts/celeborn
// release name is celeborn
helm install celeborn-beta charts/celeborn
// release name is celeborn-beta
```
### Why are the changes needed?
Support multiple celeborn clusters in the same k8s namespace
### Does this PR introduce _any_ user-facing change?
Yes
### How was this patch tested?
GA and IT
Closes#1804 from zwangsheng/CELEBORN-886.
Authored-by: zwangsheng <[email protected]>
Signed-off-by: zky.zhoukeyong <[email protected]>
(cherry picked from commit 86d78d9)
Signed-off-by: zky.zhoukeyong <[email protected]>
Is your feature request related to a problem? Please describe.
Currently, we can create only one celeborn cluster for flink when deploying on K8S in one namespace. In some scenarios, this is not very convenient. Supposing we have two resource pools divided by business type in the same k8s namespace,we have no way to create a celeborn cluster for both of the two resource pools.
Describe the solution you'd like
For each celeborn cluster, we introduce a single values.yaml file that contains all the necessary configs for creating it, and we can create the cluster using the following helm command
and we can retrieve k8s pods of each celeborn cluster by using
Describe alternatives you've considered
None
The text was updated successfully, but these errors were encountered: