Closed aojea closed 1 year ago
Yeah, I found out that this new controller is enabled in our E2E tests. It's already behind the flag, correlated with but we are not setting it.
Actually, it's worse, as the env RUN_CONTROLLERS
is broken (it's also used by KCM), so we need to fix also that. In upstream K/K, as here we are mirroring /cluster
from K/K.
We need to productionise part of https://github.com/kubernetes/cloud-provider-gcp/pull/458 related to controllers
do we need to fix it in k/k?
We need to, right now we have a broken situation when we can't set different controllers between KCM and CCM.
Temporarily we can have an in-repo patch, but let's not plan to have this situation permanently.
see in the logfile
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/cloud-provider-gcp/452/cloud-provider-gcp-e2e-full/1623042678595784704/artifacts/cluster-logs/kt2-84e756a9-a71e-master/cloud-controller-manager.log
maybe it should have a flag to enable it?
@jprzychodzen @shouri007