Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

chore: update CHANGELOG for Infisical standalone Postgres, clarifying TLS verification changes for Kubernetes auth and detailing additional upgrade notes for version v0.167.0

Victor Hugo dos Santos369d7b4131ea
diff --git a/helm-charts/infisical-standalone-postgres/CHANGELOG.md b/helm-charts/infisical-standalone-postgres/CHANGELOG.md
index 79a14cb3ca..be239c58c4 100644
--- a/helm-charts/infisical-standalone-postgres/CHANGELOG.md
+++ b/helm-charts/infisical-standalone-postgres/CHANGELOG.md
@@ -7,7 +7,7 @@ Upgrade notes:
Upgrading on default values moves Infisical from `v0.158.0` to `v0.167.0`, across releases with breaking changes. The full list, with the action for each, is in `upgrade-impact/data/releases/` (`v0.159.19` through `v0.167.0`). Act on these before you upgrade:
* Org identity credentials (`v0.166.6`): revoking auth, and creating, reading or deleting tokens and client secrets on org identities, now checks only the specific identity action. In orgs on the legacy privilege system, roles without that action, including the built-in Member role, get 403. Give users and machine identities that manage identity credentials a role with the `edit-auth`, `revoke-auth`, `create-token`, `get-token` and `delete-token` identity actions they need.
-* Identity auth TLS (`v0.159.24`): TLS is now verified for the OIDC issuer, JWT JWKS URL and Kubernetes API host that identity auth calls. If any of them uses a self-signed or internal CA, add the issuing CA certificate to that auth method's configuration.
+* Identity auth TLS (`v0.159.24`): TLS is now verified for the OIDC issuer and JWT JWKS URL that identity auth calls. If either uses a self-signed or internal CA, add the issuing CA certificate to that auth method's configuration. Kubernetes auth is different: methods that had no CA certificate stored keep TLS verification disabled after the upgrade. To turn it on, add the Kubernetes API server's issuing CA certificate to the method and set `verifyTlsCertificate` to `true`.
* Removed APIs and fields: the upgrade-path endpoints are removed (`v0.159.19`), native integrations can no longer be created (`v0.162.22`; existing integrations keep working, so move creation to Secret Syncs), and the super-admin `trustSamlEmails` and `trustOidcEmails` fields are dropped (`v0.163.0`). Update any tooling that uses them.
* Rollout: with the default `infisical.replicaCount: 2`, the Deployment replaces pods one at a time, so pods still running `v0.158.0` keep serving requests after the first new pod has migrated the database. The `v0.166.5` notes ask for all pods to roll out together. To avoid running mixed versions, scale the Deployment to 0 before `helm upgrade`, which means downtime until the new pod is ready.
* Rollback: back up the database before upgrading. After the migrations run, a `v0.158.0` pod refuses to start against the database, so `helm rollback` alone does not restore the old version.