To mimic k8s behavior with pull secrets, we might want to support multiple auth secrets in the WorkloadScan configuration.
Open point: We need to decide how to handle multiple URIs that are identical across secrets.
This way, users get a smoother config experience instead of having to bundle all credentials into a single secret. For the Registry resource, when we create the config, we'll parse the .dockerconfigjson, pick the matching secret, or create a new secret in the same namespace and keep it in sync.
To mimic k8s behavior with pull secrets, we might want to support multiple auth secrets in the WorkloadScan configuration.
Open point: We need to decide how to handle multiple URIs that are identical across secrets.
This way, users get a smoother config experience instead of having to bundle all credentials into a single secret. For the Registry resource, when we create the config, we'll parse the
.dockerconfigjson, pick the matching secret, or create a new secret in the same namespace and keep it in sync.