-
Notifications
You must be signed in to change notification settings - Fork 236
Add two options to handle self-signed certificates registries #327
Add two options to handle self-signed certificates registries #327
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hey @antechrestos, thanks for the contribution! added some feedback here, once it's addressed I'll have another look and then merge
pkg/util/transport_builder.go
Outdated
for registry := range registriesToCertificates { | ||
tlsConfiguration.registriesCertificates[registry] = registriesToCertificates[registry] | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we not just set tlsConfig.certifiedRegistries = certifiedRegistries
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was to force a copy and ensure a immutable pattern. I am open minded on this point
@nkubala Thank you for your feedback. |
@nkubala are you ok with the changes? Let me know if you're ok with letting opened the last discussion |
* 'skip-tls-verify-registry <registry name>' will skip tls verification for given registry name * 'registry-certificate <registry name>=<path to the certificate>' will give certificate for the given registry. This might be usefull for self-signed certificates Fixes #326
@antechrestos thanks for the contribution! |
Two options:
skip-tls-verify-registry <registry name>
will skip tls verification for given registry nameregistry-certificate <registry name>=<path to the certificate>
will give certificate for the given registryFixes #326