Open bdecoste opened 3 years ago
This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.
I would like to see Kuma support this so that we don't have to operate a completely separate Kubernetes cluster for the global control plane.
This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.
This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.
This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.
xrefs:
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This is planned but we first need to move all the policies to be namespace scoped.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
Policies still needing to be migrated:
deployments/charts/kuma/crds/kuma.io_externalservices.yaml: (talked about removing tags for example or at least do something better here). deployments/charts/kuma/crds/kuma.io_meshes.yaml: deployments/charts/kuma/crds/kuma.io_meshgatewayconfigs.yaml: --> Required by GatewayAPI shouldn't change deployments/charts/kuma/crds/kuma.io_meshgateways.yaml: deployments/charts/kuma/crds/kuma.io_serviceinsights.yaml: deployments/charts/kuma/crds/kuma.io_virtualoutbounds.yaml: deployments/charts/kuma/crds/kuma.io_zoneinsights.yaml: deployments/charts/kuma/crds/kuma.io_zones.yaml:
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
Random thoughts we had with @jakubdyszkiewicz :
kuma.io/system-namespace: true
The only reason for not having mesh cluster scope seems to be able to do this, which in the end might possible even with cluster scoped policies.
Though you'd only be able to run 1 zone per cluster. To be able to run multiple zones you'd probably need to say which zone your namespace is managed by (with an annotation for example).
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
Isn't this partly solved by https://github.com/kumahq/kuma/issues/5907 ? The original issue did not say that both of them have to be backed by k8s storage.
Triage: it's about deploying global and zone cp with k8s storage
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
Is this something people still ask for?
Summary
Id like to be able to deploy multizone global CP and remote CP to the same k8s cluster
Steps To Reproduce
Additional Details & Logs