search

redhat-cop / keepalived-operator

An operator to manage VIPs backed by keepalived
Apache License 2.0
118 stars 36 forks source link

KeepalivedGroup should be a cluster-level resource #8

Open raffaelespazzoli opened 4 years ago

raffaelespazzoli commented 4 years ago

Currently the KeepalivedGroup CRD is a namespaced resource, but it makes more sense for it to be a cluster-level resource.

osirisstar-hub commented 4 years ago

Perhaps I am confused but this seems to only work in a single namespace. So each namespace would have to have their own operator rather than their being a cluster operator. However, when installing two operators I get a port conflict. Do I just simply change the port number used to avoid the conflict?

osirisstar-hub commented 4 years ago

In order to get more than one operator running in a cluster so that multiple namespaces can get external IPs, I had to change the Prometheus port number in the daemonset.

Warning FailedScheduling pod/keepalivedgroup-workers-zpx8f 0/11 nodes are available: 10 node(s) didn't match node selector, 8 node(s) didn't have free ports for the requested pod ports.
raffaelespazzoli commented 4 years ago

I am not sure I am following. Anyway the operator is designed to be a cluster-wide operator, but due to an issue with the last release, OLM installs it as a namespaced operator. If you deploy the operator with watch_namespace="", it will work as expected. This will be fixed in the next release.

osirisstar-hub commented 4 years ago

watch_namespace goes into the operator yaml or into the subscription yaml?

raffaelespazzoli commented 4 years ago

watch namespace is in the args of the operator deployment. Unfortunately OLM will override whatever you change. A way around it is to deploy the operator via the helm chart as described in the docs.

On Tue, Jul 21, 2020 at 9:20 PM osirisstar-hub notifications@github.com wrote:

watch_namespace goes into the operator yaml or into the subscription yaml?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/redhat-cop/keepalived-operator/issues/8#issuecomment-662187236, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABPERXGH6TYG6IWJIMRBLL3R4Y5G5ANCNFSM4K7WANMA .

-- ciao/bye Raffaele

raffaelespazzoli commented 4 years ago

the latest release should have solved the issue with OLM.

slauger commented 4 years ago

When could we expect a new release in the OperatorHub @raffaelespazzoli?

Furthermore it would be great if you could create a "real" release on GH (not just a tag). That would allow us to get notified when a new release is available.

raffaelespazzoli commented 4 years ago

Today

On Tue, Jul 28, 2020, 5:22 PM Simon Lauger notifications@github.com wrote:

When could we expect a new release in the OperatorHub @raffaelespazzoli https://github.com/raffaelespazzoli?

Furthermore it would be great if you could create a "real" release on GH (not just a tag). That would allow us to get notified when a new release is available.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/redhat-cop/keepalived-operator/issues/8#issuecomment-665290215, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABPERXCE2SWURBCSYCQOMQDR546QHANCNFSM4K7WANMA .