When attaching clusters to Kommander, you may experience issues where nothing seems to happen. The Kubernetes cluster appears in the Kommander UI as "attached" but there are no pods in kommander-system federated, there is no information in the Karma UI and there are no errors indicating what the problem is. In this scenario, you most likely have an issue reaching your docker registry. Check the pod logs of the kommander federation utility apiserver:
kubectl logs -n kommander kommander-federation-utility-apiserver-7c7f57c5c-856ct
kommander-federation-utility-apiserver "msg"="unable to get the manifest for tag - skipping" "error"={"errors":[{"code":"TOOMANYREQUESTS","message":"You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit"}]} "tag"="v1.8.2_ubi8"
To resolve this issue, ensure that you have properly configured the utility server under the Kommander addon in cluster.yaml to include docker credentials for either docker hub or your private registry:
- configRepository: https://github.com/mesosphere/kubeaddons-kommander
configVersion: stable-1.20-1.4.1
addonsList:
- name: kommander
enabled: true
values: |2
kommander-federation:
utilityApiserver:
extraArgs:
docker-registry-url: https://registry-1.docker.io
docker-registry-username: "user"
docker-registry-password: "password"
After this just run ./konvoy deploy addons to change the configuration. Your Federated Addons and Pods should now deploy properly!