openstack/openstack-helm
Code Issues Proposed changes
1483987d2e
openstack-helm/releasenotes/notes/designate.yaml

24 lines
1.1 KiB
YAML
Raw Normal View History

Add reno job to Openstack-Helm With OSH now publishing charts regularly with each change, there needs to be a way to track these changes in order to track the changes between chart versions. This proposed change adds in a reno check job to publish notes based from the changes to each chart by version as a way to track and document all the changes that get made to OSH and published to tarballs.o.o. Change-Id: Iff8681c697957e4711754fc20b07fa6b728eb584
2021-01-06 16:22:46 -06:00
---
designate:
- 0.1.0 Initial Chart
Update aodh, barbican, designate, ironic, magnum, mistral, octavia, panko, rally, senlin and tempest release notes to current Change-Id: Id2d0911969b571d86512a6a803050ee56bd57134
2021-02-10 08:55:55 -06:00
- 0.1.1 Change helm-toolkit dependency version to ">= 0.1.0"
Added post-install and post-upgrade hook on jobs in designate chart Chart upgrading was failing due to some immutable fields are needed to upgrade before the jobs can be upgraded. For solving this issue, we have added the helm.sh/hook annotations with post-install and post-upgrade values. As for hook-weight annotations, we have added these to control the flow of the jobs with hook creation as the jobs are dependent. Like, db-init jobs need to run before db-sync and so on. Change-Id: Idca6ee2422769ccb5c8a87812b4fb564b283d44b
2021-03-24 19:10:51 +05:45
- 0.1.2 Added post-install and post-upgrade helm hooks on Jobs
Remove support for openstack releases older than T This change bumps each openstack chart version up to the next greatest minor version of 0.2.0, signifying that openstack-helm will no longer support older, EOL releases for each chart. Change-Id: I7ce80c7bdc779c1de4472079f18102f506bfbb90
2021-04-27 20:05:11 -05:00
- 0.2.0 Remove support for releases before T
Changing all policies to yaml format In the Victoria cycle oslo.policy decided to change all default policies to yaml format. Today on openstack-helm we have a mix of json and yaml on projects and, after having a bad time debugging policies that should have beeing mounted somewhere but was being mounted elsewhere, I'm proposing this change so we can unify the delivery method for all policies across components on yaml (that is supported for quite some time). This will also avoid having problems in the future as the services move from json to yaml. [1] https://specs.openstack.org/openstack/oslo-specs/specs/victoria/policy-json-to-yaml.html Signed-off-by: Thiago Brito <thiago.brito@windriver.com> Change-Id: Id170bf184e44fd77cd53929d474582022a5b6d4f
2021-05-17 19:16:54 -03:00
- 0.2.1 Use policies in yaml format
Update htk requirements repo As part of the move to helm v3, all the charts in the OSH repos will no longer lint/build properly due to a lack of helm serve in helm v3. This change modifies the helm-toolkit repo location to the osh-infra repo in order to account for the removal oh helm serve. This work is part of the migration to helm v3 and will be utilized in future changes. Change-Id: I90d25943d69ad6c76455f7778a4894f00c525c46
2021-10-10 18:45:28 -05:00
- 0.2.2 Update htk requirements repo
designate: Fix extra volume mounts This patch fixes the code for adding extra mounts for the Designate pods, it would otherwise generate invalid YAML. Change-Id: I7126e20090714db85f571a3a6a80ea2fc4e069d5
2021-11-12 01:32:37 -05:00
- 0.2.3 Fix extra volume mounts
Update default image values for designate This change updates the default image values for the designate chart from queens to wallaby. Change-Id: Iedab57743f7acce5af88d90e029ac9c6b6af3fe8
2022-04-27 09:08:23 -05:00
- 0.2.4 Update default image values to Wallaby
Migrate CronJob resources to batch/v1 and PodDisruptionBudget resources to policy/v1 This change updates the following charts to migrate CronJob resources to the batch/v1 API version, available since v1.21. [0] and to migrate PodDisruptionBudget to the policy/v1 API version, also available since v1.21. [1] - aodh (CronJob & PodDisruptionBudget) - barbican (PodDisruptionBudget) - ceilometer (PodDisruptionBudget) - cinder (CronJob & PodDisruptionBudget) - cyborg (PodDisruptionBudget) - designate (PodDisruptionBudget) - glance (PodDisruptionBudget) - heat (CronJob & PodDisruptionBudget) - horizon (PodDisruptionBudget) - Ironic (PodDisruptionBudget) - Keystone (CronJob & PodDisruptionBudget) - magnum (PodDisruptionBudget) - masakari (PodDisruptionBudget) - mistral (PodDisruptionBudget) - neutron (PodDisruptionBudget) - nova (CronJob & PodDisruptionBudget) - octavia (PodDisruptionBudget) - placement (PodDisruptionBudget) - rally (PodDisruptionBudget) - senlin (CronJob & PodDisruptionBudget) 0: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#cronjob-v125 1: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#poddisruptionbudget-v125 Change-Id: I2fc0692e1c8e2c4fa4d4ca1da96b5c6a832343fa
2022-05-05 11:48:24 -04:00
- 0.2.5 Migrated PodDisruptionBudget resource to policy/v1 API version
Support image registries with authentication 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
2022-08-02 14:19:13 -04:00
- 0.2.6 Added OCI registry authentication
Use HTTP probe instead of TCP probe 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
2022-08-18 22:52:06 +10:00
- 0.2.7 Use HTTP probe instead of TCP probe
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
- 0.2.8 Remove default policy rules
Define service_type in keystone_authtoken If application credentials with access rules are required, an OpenStack service using keystonemiddleware to authenticate with keystone, needs to define service_type in its configuration file. Change-Id: I7034e82837d724f12d57969857f79d67c962cebe
2023-05-12 23:00:39 +10:00
- 0.2.9 Define service_type in keystone_authtoken to support application credentials with access rules
Designate: Support uWSGI for API server Currently Designate API server still using eventlet-based HTTP servers, it is generally considered more performant and flexible to run them using a generic HTTP server that supports WSGI. Change-Id: I8036ed5259c67ad1315815efa00eff80075b2ed2
2023-11-02 16:46:52 +08:00
- 0.2.10 Uses uWSGI for API service
Designate: Enable custom annotations Enable custom annotations for pods [deployments, daemonsets] Change-Id: I521c74d9f064c73b90c822456e12476cd437b8a8
2024-03-26 21:26:47 +02:00
- 0.2.11 Enable custom annotations for Openstack pods
Enable custom secret annotations Enable custom annotations for secrets [identity, oslo_db, oslo_messaging, oci_image_registry, tls + other per chart specific] Change-Id: I843e665f71aeb171185845e1d6f0a18fab030061
2024-04-22 17:15:12 +03:00
- 0.2.12 Enable custom annotations for Openstack secrets
Update default images wherever possible - In some charts third party images are used. Need inspection which of them can be updated. - For some charts we don't build images. For this case let's build images for active projects and probably retire charts for retired or inactive projects. Change-Id: Ic9e634806d40595992d68c1fc3cd54b655ca5d02
2024-04-29 21:40:13 -05:00
- 0.2.13 Update images used by default
Update kubernetes-entrypoint image Use quay.io/airshipit/kubernetes-entrypoint:latest-ubuntu_focal by default instead of 1.0.0 which is v1 formatted and not supported any more by docker. Change-Id: Idf43d229d1c81c506653980b5e8cd6463550bc5f
2024-07-11 12:56:20 -05:00
- 0.2.14 Use quay.io/airshipit/kubernetes-entrypoint:latest-ubuntu_focal by default
Update Chart.yaml apiVersion to v2 Depends-On: I66dcaedefd0640f8a7b5343363354ba539d70627 Change-Id: I25a9354dff75cf4e02c28c0e756c360df7807778
2024-12-16 10:55:15 -06:00
- 0.2.15 Update Chart.yaml apiVersion to v2
Update versions of all charts to 2024.2.0 Depends-On: Ia064d83881626452dc3c0cf888128e152692ae77 Change-Id: I3c43bbc1e82cc6afbe90056fe4173d774b8c24db
2024-12-18 11:50:15 -06:00
- 2024.2.0 Update version to align with the Openstack release cycle
Update default image values for designate This change updates the default image values for the designate chart from queens to wallaby. Change-Id: Iedab57743f7acce5af88d90e029ac9c6b6af3fe8
2022-04-27 09:08:23 -05:00
...
Copy Permalink