When trying to deploy KIND Clusters in the submariner-addon repo (latest devel), the KIND clusters come up fine, but Submariner connections are not established.
Steps executed:
- make clusters
- make demo
As part of make demo, the scripts annotate the submarinerConfig of both the ManagedClusters with SkipOperatorGroup="" and override the image of submariner-operator on the ManagedCluster to 0.15.0-m4. This will change the image of the operator on the ManagedCluster, but the associated Roles/ClusterRoles are not updated and point to 0.11.0 bundle. It looks like the default Operator image of the latest bundle published to the community operator hub is 0.11.0.
Due to the missing ClusterRole, we see the following error in the submariner-operator pods.
2023-03-20T12:34:53.344Z ERR .._networkdiscovery.go:41 ..troller_submariner Error trying to discover network error="error listing the Daemonsets for flannel discovery: daemonsets.apps is forbidden: User \"system:serviceaccount:submariner-operator:submariner-operator\" cannot list resource \"daemonsets\" in API group \"apps\" in the namespace \"kube-system\""
When trying to deploy KIND Clusters in the submariner-addon repo (latest devel), the KIND clusters come up fine, but Submariner connections are not established.
Steps executed:
As part of
make demo, the scripts annotate the submarinerConfig of both the ManagedClusters withSkipOperatorGroup=""and override the image of submariner-operator on the ManagedCluster to0.15.0-m4. This will change the image of the operator on the ManagedCluster, but the associated Roles/ClusterRoles are not updated and point to0.11.0bundle. It looks like the default Operator image of the latest bundle published to the community operator hub is0.11.0.Due to the missing ClusterRole, we see the following error in the submariner-operator pods.