openstack/openstack-helm
Code Issues Proposed changes
02a9e1e0ed
openstack-helm/releasenotes/notes/aodh.yaml

15 lines
632 B
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
---
aodh:
- 0.1.0 Initial Chart
Update aodh release notes to current Change-Id: Iddb3bd0e3502f25839fd4d985ea4b5471930a4ae
2021-02-04 15:48:57 +00:00
- 0.1.1 Change helm-toolkit dependency version to ">= 0.1.0"
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
Enable taint toleration for aodh This changes use the helm-toolkit template for toleration in openstack services Signed-off-by: Lucas Cavalcante <lucasmedeiros.cavalcante@windriver.com> Story: 2009276 Task: 43531 Depends-On: I168837f962465d1c89acc511b7bf4064ac4b546c Change-Id: Ic5de545de70112bcc16cf353163a110b70874967
2022-03-22 15:34:54 -03:00
- 0.2.3 Enable taint toleration for Openstack services
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.4 Migrated CronJob resource to batch/v1 API version & PodDisruptionBudget to policy/v1
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.5 Added OCI registry authentication
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.6 Remove default policy rules
Replace node-role.kubernetes.io/master with control-plane The master label is no longer present on kubeadm control plane nodes(v1.24). For new clusters, the label 'node-role.kubernetes.io/master' will no longer be added to control plane nodes, only the label 'node-role.kubernetes.io/control-plane' will be added. For more information, refer to KEP-2067[https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint]: Rename the kubeadm "master" label and taint. the kubernetes pr: https://github.com/kubernetes/kubernetes/pull/107533 Change-Id: Iad8c833371efb3ec35149c89eb8fafdf1150fa87
2023-03-20 13:51:59 +08:00
- 0.2.7 Replace node-role.kubernetes.io/master with control-plane
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.8 Define service_type in keystone_authtoken to support application credentials with access rules
fix(yaml): add end symbol This patch set fixes end symbol to update the yaml format specification. Change-Id: I4e3e0fe4e7afeedb78679a4d4dfa37f93f459072
2021-06-22 19:57:11 +08:00
...
Copy Permalink