Bitnami/charts
2
0
Fork 0
mirror of https://github.com/bitnami/charts.git synced 2026-03-15 14:57:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/influxdb] Expose admin bucket retention (#16006)

Browse Source 
Signed-off-by: Tom Roush <4317255+TomRoush@users.noreply.github.com>
This commit is contained in:
Tom Roush
2023-04-11 02:08:58 -05:00
committed by GitHub
parent 997cb0ffa6
commit 76f89651b3
4 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
bitnami/influxdb/Chart.yaml
View File

@@ -24,4 +24,4 @@ name: influxdb
sources:
- https://github.com/bitnami/containers/tree/main/bitnami/influxdb
- https://www.influxdata.com/products/influxdb-overview/
version: 5.4.20
version: 5.4.21

1
bitnami/influxdb/README.md
View File

@@ -94,6 +94,7 @@ The command removes all the Kubernetes components associated with the chart and
| `auth.admin.token` | InfluxDB&trade; admin user's token. Only valid with InfluxDB&trade; v2 | `""` |
| `auth.admin.org` | InfluxDB&trade; admin user's org. Only valid with InfluxDB&trade; v2 | `primary` |
| `auth.admin.bucket` | InfluxDB&trade; admin user's bucket. Only valid with InfluxDB&trade; v2 | `primary` |
| `auth.admin.retention` | InfluxDB&trade; admin user's bucket retention. Only valid with InfluxDB&trade; v2 | `""` |
| `auth.createUserToken` | Whether to create tokens for the different users. Take into account these tokens are going to be created by CLI randomly and they will not be accessible from a secret. See more influxdb 2.0 [auth ref](https://docs.influxdata.com/influxdb/v2.0/security/tokens/) | `false` |
| `auth.user.username` | Name for InfluxDB&trade; user with 'admin' privileges on the bucket specified at `auth.user.bucket` and `auth.user.org` or `auth.admin.org` | `""` |
| `auth.user.password` | InfluxDB&trade; password for `user.name` user | `""` |

4
bitnami/influxdb/templates/deployment.yaml
View File

@@ -147,6 +147,10 @@ spec:
value: {{ .Values.auth.admin.bucket | quote }}
- name: INFLUXDB_ADMIN_ORG
value: {{ .Values.auth.admin.org | quote }}
{{- if .Values.auth.admin.retention }}
- name: INFLUXDB_ADMIN_RETENTION
value: {{ .Values.auth.admin.retention | quote }}
{{- end }}
{{- if .Values.auth.user.username }}
- name: INFLUXDB_USER
value: {{ .Values.auth.user.username | quote }}

3
bitnami/influxdb/values.yaml
View File

@@ -114,6 +114,9 @@ auth:
## @param auth.admin.bucket InfluxDB&trade; admin user's bucket. Only valid with InfluxDB&trade; v2
##
bucket: primary
## @param auth.admin.retention InfluxDB&trade; admin user's bucket retention. Only valid with InfluxDB&trade; v2
##
retention: ""
## @param auth.createUserToken Whether to create tokens for the different users. Take into account these tokens are going to be created by CLI randomly and they will not be accessible from a secret. See more influxdb 2.0 [auth ref](https://docs.influxdata.com/influxdb/v2.0/security/tokens/)
## You should take into account these tokens are going to be created by CLI
## so it is not possible to get them by k8s secrets nor to provide them though