InfluxDB Clustered 20241024-1354148 (#5660)

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
pull/5648/head^2
Scott Anderson 2024-10-28 10:54:51 -06:00 committed by GitHub
parent 16f0868162
commit df1225754e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 57 additions and 1 deletions

View File

@ -26,7 +26,63 @@ identified below with the <span class="cf-icon Shield pink"></span> icon.
---
## 20240925-1257864 {date="2024-09-25" .checkpoint}
## 20241024-1354148 {date="2024-10-24" .checkpoint}
### Quickstart
```yaml
spec:
package:
image: us-docker.pkg.dev/influxdb2-artifacts/clustered/influxdb:20241022-1346953
```
### Highlights
#### AppInstance image override bug fix
In [20240925-1257864](#20240925-1257864), the AppInstance image override was
broken with the introduction of strict always-on license enforcement.
This release fixes that bug.
This bug is expected to have an outsized impact on customers running InfluxDB
Clustered in air-gapped environments where the deployment model involves
overriding the default image repository to point to images copied to an
air-gapped registry.
This release is an alternative to [20240925-1257864](#20240925-1257864) for
customers who depend on this image override feature.
#### Upgrade bug fix
[20240925-1257864](#20240925-1257864) introduced a schema migration bug that
caused an `init` container in the `account` Pods to hang indefinitely.
This would only affect InfluxDB Clustered during an upgrade; not a fresh install.
For customers who experience this bug when attempting to upgrade to
[20240925-1257864](#20240925-1257864), upgrade to this 20241024-1354148 instead.
### Changes
#### Deployment
- Enable overriding the default CPU and memory resource requests and limits for
the Garbage collector and Catalog services.
- Remove the Gateway service and implement the newly introduced Core service.
- Fix logic related to applying default resource limits for IOx components.
- Support [`ResourceQuota`s](https://kubernetes.io/docs/concepts/policy/resource-quotas/)
with the `enableDefaultResourceLimits` feature flag. This causes resource
limits to be applied even to containers that don't normally have limits
applied.
---
## 20240925-1257864 {date="2024-09-25" .checkpoint}
{{% warn %}}
This release has a number of bugs in it which make it unsuitable for customer use.
If you are currently running this version, please upgrade to
[20241024-1354148](#20241024-1354148).
{{% /warn %}}
### Quickstart