[Feature Request]: ability to disable the service controller

[zifeo]

What feature would you like to have in the provider?

We are running our proper load balancing logic and only need the node controller to work. Is it possible to disable the service controller, or alternatively is the best approach to limit the exoscale iam used by it?

[kobajagi]

Hello @zifeo ,
We support externally managed NLBs, you can check the documentation here. Would this match your setup?

[zifeo]

@kobajagi Thanks for getting back. Not really because it would require to add the annotation to each service, which we cannot (some services are controlled by specific operators where there is no overriding possible) and we are using another cloud controller to control the services (we are not using any NLB from Exoscale, rather kube-vip internally). Currently the exoscale ccm keeps trying to update the services and fails forever, spamming the events and logs.

[simonhammes]

I haven't tried this out, but shouldn't this be possible by setting this field to true?

exoscale-cloud-controller-manager/exoscale/loadbalancer_config.go

Lines 4 to 6 in 351f54e

	type loadBalancerConfig struct {
	Disabled bool // if true, disables this controller
	}

Afaict this can be achieved by using the configuration file, I found this test case:

exoscale-cloud-controller-manager/exoscale/exoscale_config_test.go

Lines 45 to 46 in 351f54e

	loadBalancer:
	disabled: true

I'm not sure why this isn't documented in https://github.com/exoscale/exoscale-cloud-controller-manager/blob/master/docs/getting-started.md, maybe it's just an oversight :)

[zifeo]

@simonhammes Thanks, I can confirm that this works with the flag --cloud-config. I am leaving this issue open for the doc adjustment.