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
14 lines
494 B
YAML
14 lines
494 B
YAML
---
|
|
senlin:
|
|
- 0.1.0 Initial Chart
|
|
- 0.1.1 Change helm-toolkit dependency version to ">= 0.1.0"
|
|
- 0.2.0 Remove support for releases before T
|
|
- 0.2.1 Use policies in yaml format
|
|
- 0.2.2 Update htk requirements repo
|
|
- 0.2.3 Add conductor & health manager
|
|
- 0.2.4 Update default image release
|
|
- 0.2.5 Migrated CronJob resource to batch/v1 API version & PodDisruptionBudget to policy/v1
|
|
- 0.2.6 Add helm.sh/hook annotations for Jobs
|
|
- 0.2.7 Added OCI registry authentication
|
|
...
|