f3ed56cc18
Strictly speaking, open socket doesn't mean working API. We experienced API stopped responding and the socket was still open so API was unhealthy actually but kubernetes did not restart. HTTP probe will fix this issue. Change-Id: I95bb3ad3123d8a4a784d260477f037fa5506d290
25 lines
1.0 KiB
YAML
25 lines
1.0 KiB
YAML
---
|
|
placement:
|
|
- 0.1.0 Initial Chart
|
|
- 0.1.1 Change helm-toolkit dependency version to ">= 0.1.0"
|
|
- 0.1.2 Establish Nova/Placement dependencies
|
|
- 0.1.3 Use proper default placement image
|
|
- 0.1.4 Add null check condition in placement deployment manifest
|
|
- 0.1.5 Change Issuer to ClusterIssuer
|
|
- 0.1.6 Revert - Change Issuer to ClusterIssuer
|
|
- 0.1.7 Change Issuer to ClusterIssuer
|
|
- 0.2.0 Remove support for releases before T
|
|
- 0.2.1 Add Ussuri release support
|
|
- 0.2.2 Add Victoria and Wallaby releases support
|
|
- 0.2.3 Added helm.sh/hook annotations for Jobs
|
|
- 0.2.4 Helm 3 - Fix Job Labels
|
|
- 0.2.5 Update htk requirements repo
|
|
- 0.2.6 Enable taint toleration for Openstack services
|
|
- 0.2.7 Add helm hook annotations for db-sync job
|
|
- 0.2.8 Migrated PodDisruptionBudget resource to policy/v1 API version
|
|
- 0.2.9 Add Xena and Yoga values overrides
|
|
- 0.2.10 Added OCI registry authentication
|
|
- 0.2.11 Distinguish between port number of internal endpoint and binding port number
|
|
- 0.2.12 Use HTTP probe instead of TCP probe
|
|
...
|