Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 0 additions & 29 deletions charts/aisix-cp/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -216,35 +216,6 @@ after taking a backup, set `api.allowUnsupportedUpgrade: true` for that one
upgrade and set it back afterwards. See
[Upgrade](https://docs.api7.ai/ai-gateway/on-premises/upgrade).

### Upgrading to 1.8.0

`cp-api` 1.8.0 refuses to start on a database last run by a control plane older
than 1.6.0. Upgrade to 1.6.x or 1.7.x first; to proceed anyway, take a database
backup, then set `api.allowUnsupportedUpgrade: true` for that one upgrade and
set it back afterwards.

An install that still carries chart 1.5.0 values moves `AISIX_TRUSTED_ORIGINS`
and `AISIX_AUTH_BEARER_SESSIONS` from `ui.extraEnvVars` to `api.extraEnvVars`
before upgrading — or better, sets `api.trustedOrigins` / `api.bearerSessions` —
since the chart no longer copies them to `cp-api`. The `<release>-ui` Service is
removed: point any NodePort, ingress or proxy that used it at the
`<release>-api` Service, which serves the console at every path.

Whenever the release was first installed: if `api.extraEnvVars` or
`dpm.extraEnvVars` overrides an environment variable chart 1.5.0 itself
rendered (for example `AISIX_CLOUD_PUBLIC_BASE_URL` or
`AISIX_CLOUD_DATABASE_URL`), the first `helm upgrade` to 1.8.0 removes that
variable from the Deployment, because the 1.6.x and 1.7.x charts rendered the
name twice and this one renders it once, so until it is restored `cp-api` runs
on the value the chart derives from `values.yaml` — for the database URL, that
is the chart's database, which `cp-api` migrates on start. Move such a setting
to its key in `values.yaml` before upgrading, and check that the rendered
database is the one you mean. If an upgrade already dropped an override, run
`helm upgrade` again with the same values to restore it.

See [Upgrade](https://docs.api7.ai/ai-gateway/on-premises/upgrade) for the full
procedure.

## Uninstall

```sh
Expand Down
29 changes: 0 additions & 29 deletions charts/aisix-cp/README.md.gotmpl
Original file line number Diff line number Diff line change
Expand Up @@ -208,35 +208,6 @@ after taking a backup, set `api.allowUnsupportedUpgrade: true` for that one
upgrade and set it back afterwards. See
[Upgrade](https://docs.api7.ai/ai-gateway/on-premises/upgrade).

### Upgrading to 1.8.0

`cp-api` 1.8.0 refuses to start on a database last run by a control plane older
than 1.6.0. Upgrade to 1.6.x or 1.7.x first; to proceed anyway, take a database
backup, then set `api.allowUnsupportedUpgrade: true` for that one upgrade and
set it back afterwards.

An install that still carries chart 1.5.0 values moves `AISIX_TRUSTED_ORIGINS`
and `AISIX_AUTH_BEARER_SESSIONS` from `ui.extraEnvVars` to `api.extraEnvVars`
before upgrading — or better, sets `api.trustedOrigins` / `api.bearerSessions` —
since the chart no longer copies them to `cp-api`. The `<release>-ui` Service is
removed: point any NodePort, ingress or proxy that used it at the
`<release>-api` Service, which serves the console at every path.

Whenever the release was first installed: if `api.extraEnvVars` or
`dpm.extraEnvVars` overrides an environment variable chart 1.5.0 itself
rendered (for example `AISIX_CLOUD_PUBLIC_BASE_URL` or
`AISIX_CLOUD_DATABASE_URL`), the first `helm upgrade` to 1.8.0 removes that
variable from the Deployment, because the 1.6.x and 1.7.x charts rendered the
name twice and this one renders it once, so until it is restored `cp-api` runs
on the value the chart derives from `values.yaml` — for the database URL, that
is the chart's database, which `cp-api` migrates on start. Move such a setting
to its key in `values.yaml` before upgrading, and check that the rendered
database is the one you mean. If an upgrade already dropped an override, run
`helm upgrade` again with the same values to restore it.

See [Upgrade](https://docs.api7.ai/ai-gateway/on-premises/upgrade) for the full
procedure.

## Uninstall

```sh
Expand Down
Loading