
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
10 lines
337 B
YAML
10 lines
337 B
YAML
---
|
|
masakari:
|
|
- 0.1.0 Initial Chart
|
|
- 0.1.1 Seperate node labels for monitors
|
|
- 0.1.2 Added halm hook and fix for hostmonitors to support pacemaker remote
|
|
- 0.1.3 Mount sudoers file for masakari hostmonitors
|
|
- 0.1.4 Migrated PodDisruptionBudget resource to policy/v1 API version
|
|
- 0.1.5 Added OCI registry authentication
|
|
...
|