Skip to content

Commit

Permalink
chore(typo): fix (#1375)
Browse files Browse the repository at this point in the history
  • Loading branch information
@yinheli
yinheli authored Aug 3, 2024
1 parent cb53a21 commit a284f91
Show file tree
Hide file tree
Showing 4 changed files with 25 additions and 25 deletions.
12 changes: 6 additions & 6 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@ mode. This change requires action on your part to ensure a smooth upgrade.
7. **(Optional)** If you would like to switch to a non-dedicated cluster, set **'controller.controllerOnly=false'**. This will cause controller-only nodes to switch to controller+broker nodes.

At this point, you could manually decommission broker-only nodes by reassigning its partitions to controller-eligible nodes.

For more information about decommissioning a Kafka broker, check the official documentation.

## Upgrading from 20.x.x version of this Chart to 21.x.x
Expand Down Expand Up @@ -131,7 +131,7 @@ kafka:
## Upgrading from 18.x.x version of this Chart to 19.x.x
Chart dependencies has been upgraded because of sentry requirements.
Chart dependencies has been upgraded because of sentry requirements.
Changes:
- The minimum required version of Postgresql is 14.5 (works with 15.x too)
Expand All @@ -141,7 +141,7 @@ Bumped dependencies:
## Upgrading from 17.x.x version of this Chart to 18.x.x
If Kafka is complaining about unknown or missing topic, please connect to kafka-0 and run
If Kafka is complaining about unknown or missing topic, please connect to kafka-0 and run
`/opt/bitnami/kafka/bin/kafka-topics.sh --create --topic ingest-replay-recordings --bootstrap-server localhost:9092`
Expand All @@ -150,7 +150,7 @@ If Kafka is complaining about unknown or missing topic, please connect to kafka-
Sentry version from 22.10.0 onwards should be using chart 17.x.x
- post process forwarder events and transactions topics are splitted in Sentry 22.10.0
- post process forwarder events and transactions topics are split in Sentry 22.10.0
You can delete the deployment "sentry-post-process-forward" as it's no longer needed.

Expand All @@ -167,7 +167,7 @@ See https://github.com/sentry-kubernetes/charts/tree/develop/sentry#sentry-secre

## Upgrading from 14.x.x version of this Chart to 15.x.x

Chart dependencies has been upgraded because of bitnami charts removal.
Chart dependencies has been upgraded because of bitnami charts removal.
Changes:
- `nginx.service.port: 80` > `nginx.service.ports.http: 80`
- `kafka.service.port` > `kafka.service.ports.client`
Expand Down Expand Up @@ -246,7 +246,7 @@ clickhouse.clickhouse.configmap.remote_servers.replica.backup

## Upgrading from 4.x.x version of this Chart to 5.0.0

As Relay is now part of this chart your need to make sure you enable either Nginx or the Ingress. Please read the next paragraph for more informations.
As Relay is now part of this chart your need to make sure you enable either Nginx or the Ingress. Please read the next paragraph for more information.

If you are using an ingress gateway (like istio), you have to change your inbound path from sentry-web to nginx.

Expand Down
28 changes: 14 additions & 14 deletions charts/clickhouse/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -68,14 +68,14 @@ The following tables lists the configurable parameters of the Clickhouse chart a
| `clickhouse.readinessProbe.successThreshold` | Minimum consecutive failures for the probe | `1` |
|`clickhouse.resources` | The resource requests and limits for Clickhouse pods |`{}` |
| `clickhouse.persistentVolumeClaim.enabled` | Enable persistence using a `PersistentVolumeClaim` | `false` |
| `clickhouse.persistentVolumeClaim.dataPersistentVolume.enabled` | Turn on and off dataPersistentVolume | `false` |
| `clickhouse.persistentVolumeClaim.dataPersistentVolume.accessModes` | Persistent Volume Access Modes | `[ReadWriteOnce]` |
| `clickhouse.persistentVolumeClaim.dataPersistentVolume.storageClassName` | Persistent Volume Storage Class | `` |
| `clickhouse.persistentVolumeClaim.dataPersistentVolume.storage` | Persistent Volume Size | `500Gi` |
| `clickhouse.persistentVolumeClaim.logsPersistentVolume.enabled` | Turn on and off dataPersistentVolume | `false` |
| `clickhouse.persistentVolumeClaim.logsPersistentVolume.accessModes` | Persistent Volume Access Modes | `[ReadWriteOnce]` |
| `clickhouse.persistentVolumeClaim.logsPersistentVolume.storageClassName` | Persistent Volume Storage Class | `` |
| `clickhouse.persistentVolumeClaim.logsPersistentVolume.storage` | Persistent Volume Size | `50Gi` |
| `clickhouse.persistentVolumeClaim.dataPersistentVolume.enabled` | Turn on and off dataPersistentVolume | `false` |
| `clickhouse.persistentVolumeClaim.dataPersistentVolume.accessModes` | Persistent Volume Access Modes | `[ReadWriteOnce]` |
| `clickhouse.persistentVolumeClaim.dataPersistentVolume.storageClassName` | Persistent Volume Storage Class | `` |
| `clickhouse.persistentVolumeClaim.dataPersistentVolume.storage` | Persistent Volume Size | `500Gi` |
| `clickhouse.persistentVolumeClaim.logsPersistentVolume.enabled` | Turn on and off dataPersistentVolume | `false` |
| `clickhouse.persistentVolumeClaim.logsPersistentVolume.accessModes` | Persistent Volume Access Modes | `[ReadWriteOnce]` |
| `clickhouse.persistentVolumeClaim.logsPersistentVolume.storageClassName` | Persistent Volume Storage Class | `` |
| `clickhouse.persistentVolumeClaim.logsPersistentVolume.storage` | Persistent Volume Size | `50Gi` |
| `clickhouse.ingress.enabled` | Enable ingress | `false` |
| `clickhouse.ingress.host` | Ingress host | `` |
| `clickhouse.ingress.path` | Ingress path | `` |
Expand Down Expand Up @@ -130,22 +130,22 @@ The following tables lists the configurable parameters of the Clickhouse chart a
| `clickhouse.configmap.remote_servers.graphite.config[].events_cumulative` | Sending cumulative data from a :ref:system_tables-system.events table | `true` |
| `clickhouse.configmap.remote_servers.graphite.config[].asynchronous_metrics` | Sending data from a :ref:system_tables-system.asynchronous_metrics table | `true` |
| `clickhouse.configmap.profiles.enabled` | Enable a settings profiles | `false` |
| `clickhouse.configmap.profiles.profile[].name` | Tne name of a settings profile | `` |
| `clickhouse.configmap.profiles.profile[].name` | The name of a settings profile | `` |
| `clickhouse.configmap.profiles.profile[].config` | The config of a settings profile | `{}` |
| `clickhouse.configmap.users.enabled` | Enable a settings users | `false` |
| `clickhouse.configmap.users.user[].name` | Tne name of a settings user | `` |
| `clickhouse.configmap.users.user[].config` | Tne config of a settings user | `{}` |
| `clickhouse.configmap.users.user[].name` | The name of a settings user | `` |
| `clickhouse.configmap.users.user[].config` | The config of a settings user | `{}` |
| `clickhouse.configmap.quotas.enabled` | Enable a settings quotas | `false` |
| `clickhouse.configmap.quotas.quota[].name` | Tne name of a settings quota | `` |
| `clickhouse.configmap.quotas.quota[].config[]` | Tne config of a settings quota | `[]` |
| `clickhouse.configmap.quotas.quota[].name` | The name of a settings quota | `` |
| `clickhouse.configmap.quotas.quota[].config[]` | The config of a settings quota | `[]` |
| `tabix.enabled` | Enable tabix | `false` |
| `tabix.replicas` | The instance number of Tabix | `1` |
| `tabix.updateStrategy.type` | Type of deployment. Can be "Recreate" or "RollingUpdate". Default is RollingUpdate | `RollingUpdate` |
| `tabix.updateStrategy.maxSurge` | The maximum number of pods that can be scheduled above the desired number of pods | `3` |
| `tabix.updateStrategy.maxUnavailable` | The maximum number of pods that can be unavailable during the update | `1` |
| `tabix.image` | Docker image name | `spoonest/clickhouse-tabix-web-client` |
| `tabix.imageVersion` | Docker image version | `stable` |
| `tabix.imagePullPolicy` | Dcoker image pull policy | `IfNotPresent` |
| `tabix.imagePullPolicy` | Docker image pull policy | `IfNotPresent` |
| `tabix.livenessProbe.enabled` | Turn on and off liveness probe | `true` |
| `tabix.livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated | `30` |
| `tabix.livenessProbe.periodSeconds` | How often to perform the probe | `30` |
Expand Down
Loading

0 comments on commit a284f91

Please sign in to comment.