Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update: Apparently, the initial certificates we created for our demo IDP, they were created wrong, and that's why we were required to upload them to the machine. This means, that the requirement of uploading custom CA certs shouldn't be that important (actually, It would become a small corner case), so we can postpone this by now
Add option to import CA certificates to the cluster.
When SSO options are used and the IPD is hosted using TLS, the client (trento web in this case) must have the CA certificate installed in the system. This in helm is not a default scenario in many cases.
In order to have the option to import the CA certificates, I have added this new variable
caStoreConfigmap
that we can use for this purpose.The usage would be like:
.pem
file. Put this certificate in a new folderkubectl create configmap ca-pemstore --from-file=/folder_with_ca/
. The nameca-pemstore
can be any other stringhelm ... --set trento-web.caStoreConfigmap=ca-pemstore
With this, all the content in the
/folder_with_ca/
is imported in the pod and trento web can use them.