You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For registry storage requiring authentication (i.e. S3), it is painful to deal with static credentials, key rotations and related security concerns. Docker v3 registry supports AWS IRSA auth and seems to work great with zarf:
Migrating to Docker V3 registry will enhance security by reducing the use of static secrets, enable integration with the AWS-SDK, and provide a more Kubernetes-native way of handling authentication. This aligns with modern best practices for secure, automated container registry access. Existing workflows should be tested for compatibility, and documentation updated to reflect these changes.
Is your feature request related to a problem? Please describe.
For registry storage requiring authentication (i.e. S3), it is painful to deal with static credentials, key rotations and related security concerns. Docker v3 registry supports AWS IRSA auth and seems to work great with zarf:
https://github.com/distribution/distribution/releases/tag/v3.0.0-beta.1
Describe the solution you'd like
zarf init
with an S3 backed registryDescribe alternatives you've considered
Additional context
Migrating to Docker V3 registry will enhance security by reducing the use of static secrets, enable integration with the AWS-SDK, and provide a more Kubernetes-native way of handling authentication. This aligns with modern best practices for secure, automated container registry access. Existing workflows should be tested for compatibility, and documentation updated to reflect these changes.
Image is not currently added to IronBank: https://repo1.dso.mil/dsop/opensource/docker/registry-v2/-/issues/112
Related Issues
#375
#3001
#2273
#2758
The text was updated successfully, but these errors were encountered: