-
Notifications
You must be signed in to change notification settings - Fork 336
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
feat(kuma-cp) sync policies over KDS #857
Conversation
# Conflicts: # app/kuma-cp/cmd/run.go # pkg/config/app/kuma-cp/config.go # pkg/config/app/kuma-cp/kuma-cp.defaults.yaml
# Conflicts: # app/kuma-cp/cmd/run.go # pkg/config/kds/config.go # pkg/kds/reconcile/snapshot_generator.go # pkg/kds/server/components.go # pkg/kds/server/kds.go # pkg/kds/server/server.go # pkg/kds/server/server_test.go # pkg/kds/types.go # pkg/test/kds/verifier/context.go # pkg/test/kds/verifier/executables.go
# Conflicts: # go.sum
# Conflicts: # app/kumactl/pkg/install/k8s/control-plane/templates_vfsdata.go
# Conflicts: # app/kuma-cp/cmd/run.go # app/kumactl/pkg/install/k8s/control-plane/templates_vfsdata.go # pkg/config/kds/config.go # pkg/kds/reconcile/snapshot_generator.go # pkg/kds/server/components.go # pkg/kds/server/grpc.go # pkg/kds/server/kds.go # pkg/kds/server/server_test.go # pkg/kds/types.go # pkg/test/kds/verifier/context.go # pkg/test/kds/verifier/executables.go # test/e2e/kuma_deploy_global_remote_test.go
# Conflicts: # app/kuma-cp/cmd/run.go # app/kumactl/pkg/install/k8s/control-plane/templates_vfsdata.go # pkg/kds/global/components.go # pkg/kds/global/components_test.go # pkg/kds/reconcile/snapshot_generator.go # pkg/kds/remote/components.go # pkg/kds/server/components.go # pkg/kds/util/resource.go # pkg/test/kds/setup/server.go # test/e2e/kuma_deploy_global_remote_test.go
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.
how does it work with many instances?
@@ -105,6 +105,7 @@ rules: | |||
- get | |||
- list | |||
- watch | |||
- create |
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.
Why only circuitbreaker got create
? What about for example traffictraces or trafficlog?
} | ||
|
||
func ClusterTag(r model.Resource) string { | ||
return r.GetSpec().(*mesh_proto.Dataplane).GetNetworking().GetInbound()[0].GetTags()[mesh_proto.ClusterTag] |
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.
Can we assume that there are inbounds? What if it's gateway?
// That's why we can set 'Name' like this | ||
m := util.ResourceKeyToMeta(newName, r.GetMeta().GetMesh()) | ||
r.SetMeta(m) | ||
func adjustIngressNetworking(cfg *clusters.ClusterConfig, rs model.ResourceList) { |
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.
We also need only one Ingress, when having 5 ingress instances we should only sync 1 to other clusters with LB IP
…into feat/kds-sync-policies
Add `kumactl install ingress --use-node-port` and default to using LoadBalancer in the Ingress service, when this flag is not set. Signed-off-by: Nikolay Nikolaev <[email protected]>
Add `kumactl install control-plane --use-node-port` and default to using LoadBalancer in the Ingress service, when this flag is not set. Signed-off-by: Nikolay Nikolaev <[email protected]>
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.
👌 💯
Summary
Syncing policies over KDS
Issues resolved
Fix https://github.com/Kong/kuma/issues/804
Documentation