Harbor fails to deploy

[arkadijs]

Harbor helm chart timeouts waiting on a core pod due to TLS secret missing ca.crt key which is mounted into the pod as file. Apparently, Cert-manager succeeds installing tls.crt/key entries. Could be a race condition.

[rstreics]

@arkadijs could elaborate how previously ca.crt was provided? I reading comments that

cert manager with Let's Encrypt does not (and will not) provide "ca.crt" key

link
I can add code that would create ca.crt, but at the moment I'm not sure if this not a bug and maybe this should done by cert-manager?

[arkadijs]

I have no idea.

[rstreics]

Looking at cert-manger issues this seems a common problem. Example: Add ca.crt to TLS secret generated by ACME issuers is in backlog haven't been fixed.

I will add custom fix to helm deployment as I can't determine that this feature ever worked out of the box.

[akranga]

@rstreics are you working on this now? Or I can care of tis issue?

[akranga]

Tried to deploy with the commit: e2fef45
Still getting same error. Fully reproducible if you deploy: agilestacks/stack-ml-eks from CLI

[rstreics]

@akranga As mentioned previously, there multiple way for failure and for this to work consistently we need move control loop from helm to separate script.

[arkadijs]

OLR, people, this is resolved upstream a year ago.
https://github.com/goharbor/harbor-helm/pull/348/files

[rstreics]

Nice catch, this wasn't mentioned in any issues I found related to this problem.

[arkadijs]

Deploying from Control Plane:

helm --kube-context="arkadi-eks-happy-meal.smoke-arkadi-aws01.dev.superhub.io" --tiller-namespace="kube-system" list -q --namespace harbor | grep -E '^dev-ops-harbor$' || \
	helm --kube-context="arkadi-eks-happy-meal.smoke-arkadi-aws01.dev.superhub.io" --tiller-namespace="kube-system"	install /workspace/repo/components/harbor/aws/.helm/dev-ops-harbor \
	    --name dev-ops-harbor \
		--namespace harbor \
		--wait \
		--version 71b28b46fbb87a51bedc7d405f74167e9ee25143  \
		--values values.yaml \
		--values letsencrypt/values.yaml \
		--values local/values.yaml \
		--set "harborAdminPassword=$ADMIN_PASSWORD"  \

The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?