openstack-helm/releasenotes/notes/placement.yaml
ricolin b72f3d0f3c Avoid unrequired policy setup
OpenStack services already moved to use policy in code.
No need to have policy file at this point, at least no need to put
default policy rule to policy.yaml file anymore.
To put in duplicate rules, will cause unnecessay logs and process.
Also not healthy for policy in code maintain as the `default` rules in
openstack-helm might override actual default rules in code which we
might not even mean to change it at all.

Change-Id: I29ea57aa80444ed64673818e597c9ca346ba7b2f
2022-11-23 22:43:10 +08:00

29 lines
1.2 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
- 0.2.13 Support TLS endpoints
- 0.3.0 Remove placement-migrate
- 0.3.1 Remove support for Train and Ussuri
- 0.3.2 Remove default policy rules
...