-
Notifications
You must be signed in to change notification settings - Fork 1
Local Setup: Secure the registry with HTTPS cert #27
Copy link
Copy link
Open
Labels
area/dev-productivityDeveloper productivity related (how to improve development)Developer productivity related (how to improve development)area/securitySecurity relatedSecurity relatedkind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extensionlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.teamsize/smallA team of 1-2 people.A team of 1-2 people.
Description
Metadata
Metadata
Assignees
Labels
area/dev-productivityDeveloper productivity related (how to improve development)Developer productivity related (how to improve development)area/securitySecurity relatedSecurity relatedkind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extensionlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.teamsize/smallA team of 1-2 people.A team of 1-2 people.
Type
Fields
Give feedbackNo fields configured for issues without a type.
How to categorize this topic?
/area dev-productivity security
/kind enhancement
/label teamsize/small
What is the topic about?:
With gardener/gardener#13751 Gardener is adding support for registries using custom CA, this would allow registry.local.gardener.cloud to be served over HTTPS instead of HTTP, respectively all configurations configuring the registry as insecure can be removed. Other components, like lakom, will be able to remove the insecure option allowing registries served in plain text.
ref: https://github.com/gardener/gardener-extension-shoot-lakom-service/blob/6105f5edaad1dcaedb5ceb503964032355dc7ddd/pkg/lakom/verifysignature/verifier.go#L30