SKIP UPGRADE CHECK Update Ironbank

This MR contains the following updates:

Package	Update	Change
gluon	patch	0.5.4 -> 0.5.8
ironbank/hashicorp/vault (source)	minor	1.17.6 -> 1.18.0
registry1.dso.mil/ironbank/hashicorp/vault (source)	minor	1.17.6 -> 1.18.0

Complete MR checklist

Assignee

• Followed upgrade instructions outlined in docs/DEVELOPMENT_MAINTENANCE.md
• Update Docs with new/updated steps as needed
• Tested and Validated Changes made with supporting info like logs or screenshots from test pipelines

Add supporting info below

Running 1.18.0

Can create and read secrets using the stored token in the vault-token secret

ACL policies are created

Reviewer only

• Tested and Validated changes

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this MR, check this box

---

This MR was automatically generated by Renovate Bot.

Upgrade Notices

Vault is upgrading from 1.17.6 to 1.18.0 . Please, follow the official upgrade notices and instructions found here:

https://developer.hashicorp.com/vault/docs/platform/k8s/helm/run#upgrading-vault-on-kubernetes

Primarily:

1. backup your data
2. The helm upgrade command should have updated the StatefulSet template for the Vault servers, however, no pods have been deleted. The pods must be manually deleted to upgrade. Deleting the pods does not delete any persisted data.