Open rguske opened 4 years ago
Thanks for the detailed explanation
Thanks Raiko :)
@rmesterheide Thanks for the detailed explanation
Hi Raiko, Thanks for a wonderful explanation. I was wondering if there is a necessity in installing harbor inside the supervisor cluster namespace? I have installed harbor in the TKG cluster which is inside the supervisor cluster. I updated the image-fetcher-ca-bundle with the certificate of harbor as given in your explanation inside the supervisor cluster where harbor is not running. However, it is not taking any effect. Any idea, how I can get this to work when harbor is deployed on TKG cluster as against the supervisor cluster? Is there a different config map/ secret that can be applied to get the certificate to work?
@deepakj6 Hi Raiko, Thanks for a wonderful explanation. I was wondering if there is a necessity in installing harbor inside the supervisor cluster namespace? I have installed harbor in the TKG cluster which is inside the supervisor cluster. I updated the image-fetcher-ca-bundle with the certificate of harbor as given in your explanation inside the supervisor cluster where harbor is not running. However, it is not taking any effect. Any idea, how I can get this to work when harbor is deployed on TKG cluster as against the supervisor cluster? Is there a different config map/ secret that can be applied to get the certificate to work?
Hi DJ,
thanks for your kind feedback. I'm not quiet sure if I understood the first part correctly because I installed Harbor inside a TKG cluster. Please correct my misunderstanding if I got it wrong.
Did you pay attention to the correct position of the ca.crt
when adding it to your configmap? It should look similar to my example.
https://rguske.github.io/post/vsphere-7-with-kubernetes-supercharged-helm-harbor-tkg/?code=0cc92799b5b789121278