Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare for release 0.26.1 #970

Merged
merged 2 commits into from
Oct 30, 2023
Merged

Prepare for release 0.26.1 #970

merged 2 commits into from
Oct 30, 2023

Conversation

kschoche
Copy link
Contributor

Fixes a bug preventing templating of server.ha.replicas.

+## 0.26.1 (October 30, 2023)
+
+Bugs:
+* Fix templating of `server.ha.replicas` when set via override file. [GH-961](https://github.com/hashicorp/vault-helm/pull/961)
+

@kschoche kschoche requested a review from a team as a code owner October 30, 2023 18:13
Copy link
Contributor

@swenson swenson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, one question

CHANGELOG.md Outdated
## 0.26.0 (October 27, 2023)

KNOWN ISSUES:

* The chart will ignore `server.ha.replicas` and always deploy 3 server replicas when `server.ha.enabled=true` unless overridden by command line when issuing the helm command: `--set server.ha.replicas=<some_number>`. Fixed in [GH-961](https://github.com/hashicorp/vault-helm/pull/961)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure it is necessary to put this here if we are fixing it in 0.26.1?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I was trying to say that 0.26.0 has a known issue which is fixed in 0.26.1. I was pointing it out because it can be particularly impactful if you were to deploy to a cluster that has it previously pinned to 1 or 5?
Happy to change it if you don't think it's necessary.

@swenson
Copy link
Contributor

swenson commented Oct 30, 2023

I'm okay either way. But presumably all bug fixes were known issues in 1 or more prior releases :)

@kschoche
Copy link
Contributor Author

I'm okay either way. But presumably all bug fixes were known issues in 1 or more prior releases :)

Thanks, good call. I removed the known issues section and moved some of its contents in support of the "fix".

@kschoche kschoche merged commit 36dafa0 into main Oct 30, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants