we are trying out submariner in azure aks environment in two clusters, after following the helm installation steps provided in link
We have not yet executed the post installation steps specific to calico CNI. assume that gateway should be up regardless.
we observe the deployed resources are not properly up in both cluster.
I0810 17:56:36.097872 1 main.go:71] Starting the submariner gateway engine
W0810 17:56:36.098404 1 client_config.go:543] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I0810 17:56:36.098649 1 main.go:99] Creating the cable engine
I0810 17:56:36.311212 1 syncer.go:51] CableEngine syncer started
I0810 17:56:36.311821 1 main.go:263] Gateway leader election config values: main.leaderConfig{LeaseDuration:10, RenewDeadline:5, RetryPeriod:2}
I0810 17:56:36.311991 1 main.go:280] Using namespace "submariner-operator" for the leader election lock
I0810 17:56:36.312011 1 leaderelection.go:242] attempting to acquire leader lease submariner-operator/submariner-engine-lock...
I0810 17:56:36.345107 1 leaderelection.go:252] successfully acquired lease submariner-operator/submariner-engine-lock
I0810 17:56:36.345144 1 main.go:133] Creating the tunnel controller
I0810 17:56:36.345143 1 event.go:281] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"submariner-operator", Name:"submariner-engine-lock", UID:"5730b78c-c596-43d2-b1a5-6212f62ec983", APIVersion:"v1", ResourceVersion:"1074527", FieldPath:""}): type: 'Normal' reason: 'LeaderElection' aks-devfecpool-17806234-vmss000000-submariner-engine became leader
I0810 17:56:36.345184 1 main.go:141] Creating the kubernetes central datastore
Any pointers in resolving this error is appreciated.