Affects:
Konvoy versions 1.5 and greaterIssue:
As of Konvoy 1.5, there is a new component called Auto-Provisioning that deploys by default. If you deploy a Konvoy cluster, it is possible to disable the auto-provisioning module via the --without-auto-provisioning flag. This is useful if you are deploying somewhere that auto-provisioning is not supported such as an on premise location, or you are not using a component that has auto-provisioing as a prerequisite.However, if you intend to utilize Kommander, you must also deploy with auto-provisioning enabled. If you do not, once you attempt to navigate to the Projects page of a Kommander UI, you will be greeted by the following message:
Unauthorized access to page (401)
You are not authorized to access this page.
You will also see that some pods are not able to start correctly and log messages such as the following inside the pods:
2020-12-01T10:00:00.000Z ERROR controller-runtime.source if kind is a CRD, it should be installed before calling Start {"kind": "KonvoyCluster.kommander.mesosphere.io", "error": "no matches for kind \"KonvoyCluster\" in version \"kommander.mesosphere.io/v1beta1\""}