Uses the trust certificate overlay to ensure that Harbor components
trust Let's Encrypt as a CA (fixes #120)
Details
Allows using a custom URL/issuer for the Okta endpoint signed by
Let's Encrypt. Ran into the same issue with Harbor (#120) as with
Dex whereby the OIDC integration would fail if the Okta endpoint
was signed with Let's Encrypt (see #119 for that change). This
change applies the overlay overlay/trust-certificate to the Harbor
extension to make sure the Let's Encrypt CA certificate is trusted
by all Harbor components.
As a bonus, while validating this change I found an issue where
the TKG extension for Harbor does not work when specifying an S3
backend. I added an additional overlay to make sure that works.
TL;DR
Uses the trust certificate overlay to ensure that Harbor components trust Let's Encrypt as a CA (fixes #120)
Details
Allows using a custom URL/issuer for the Okta endpoint signed by Let's Encrypt. Ran into the same issue with Harbor (#120) as with Dex whereby the OIDC integration would fail if the Okta endpoint was signed with Let's Encrypt (see #119 for that change). This change applies the overlay
overlay/trust-certificate
to the Harbor extension to make sure the Let's Encrypt CA certificate is trusted by all Harbor components.As a bonus, while validating this change I found an issue where the TKG extension for Harbor does not work when specifying an S3 backend. I added an additional overlay to make sure that works.