ced30abead
Based on spec support-OCI-image-registry-with-authentication-turned-on.rst Each Helm chart can configure an OCI image registry and credentials to use. A Kubernetes secret is then created with this info. Service Accounts then specify an imagePullSecret specifying the Secret with creds for the registry. Then any pod using one of these ServiceAccounts may pull images from an authenticated container registry. Related OSH-infra change: https://review.opendev.org/c/openstack/openstack-helm-infra/+/848142 Change-Id: I54540f14fed29622bc5af8d18939afd06d65e2d8 |
||
---|---|---|
.. | ||
bin | ||
certificates.yaml | ||
configmap-bin.yaml | ||
configmap-etc.yaml | ||
deployment.yaml | ||
ingress.yaml | ||
job-db-drop.yaml | ||
job-db-init.yaml | ||
job-db-migrate.yaml | ||
job-db-sync.yaml | ||
job-image-repo-sync.yaml | ||
job-ks-endpoints.yaml | ||
job-ks-service.yaml | ||
job-ks-user.yaml | ||
network_policy.yaml | ||
pdb.yaml | ||
secret-db.yaml | ||
secret-ingress-tls.yaml | ||
secret-keystone.yaml | ||
secret-registry.yaml | ||
service-ingress.yaml | ||
service.yaml |