Skip to content

Commit

Permalink
add "whats new in v3.2.1" to csv description (#315)
Browse files Browse the repository at this point in the history
  • Loading branch information
maskarb authored Mar 18, 2024
1 parent 631434d commit af2669a
Showing 1 changed file with 9 additions and 4 deletions.
13 changes: 9 additions & 4 deletions docs/csv-description.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,10 +19,15 @@ The Koku Metrics Operator (`koku-metrics-operator`) collects the metrics require
* PersistentVolumeClaim (PVC) configuration: The KokuMetricsConfig CR can accept a PVC definition and the operator will create and mount the PVC. If one is not provided, a default PVC will be created.
* Restricted network installation: this operator can function on a restricted network. In this mode, the operator stores the packaged reports for manual retrieval.

## New in v3.2.1:
* The minimum supported configuration for `upload_cycle` is now 60 (minutes).
* (Bugfix) many-to-many matching not allowed query fix.
* (Bugfix) Sequentially collect data during initial install.

## New in v3.2.0:
* Support for amd64, arm64, ppc64le, s390x architectures
* add liveness and readiness probes to controller Pod
* update pod security settings so that the controller Pod can run in Restricted mode [more info](https://sdk.operatorframework.io/docs/best-practices/pod-security-standards/)
* Support for amd64, arm64, ppc64le, s390x architectures.
* add liveness and readiness probes to controller Pod.
* update pod security settings so that the controller Pod can run in Restricted mode [more info](https://sdk.operatorframework.io/docs/best-practices/pod-security-standards/).

## New in v3.1.0:
* Add service-account authentication type.
Expand Down Expand Up @@ -84,7 +89,7 @@ If these assumptions are not met, the operator will not deploy correctly. In the
* `create_source: false` -> Toggle for whether or not the operator will create the integration in `console.redhat.com`. The default is False. This parameter should be switched to True when an integration does not already exist in `console.redhat.com` for this cluster.
* `check_cycle: 1440` -> The time in minutes to wait between checking if an integration exists for this cluster. The default is 1440 minutes (24 hrs).
* `upload`:
* `upload_cycle: 360` -> The time in minutes between payload uploads. The default is 360 (6 hours).
* `upload_cycle: 360` -> The time in minutes between payload uploads. The default is 360 (6 hours), minimum is 60 (1 hour).
* `upload_toggle: true` -> Toggle to turn upload on or off -> true means upload, false means do not upload (false == air-gapped mode). The default is `true`.
* `upload_wait` -> The amount of time (in seconds) to pause before uploading a payload. The default is a random number between 0 and 35. This is used to decrease service load, but may be set to `0` if desired.
* `volume_claim_template` -> see the "Storage configuration prerequisite" section above.
Expand Down

0 comments on commit af2669a

Please sign in to comment.