influxdb-operator icon indicating copy to clipboard operation
influxdb-operator copied to clipboard

The Kubernetes operator for InfluxDB and the TICK stack.

Results 11 influxdb-operator issues
Sort by recently updated
recently updated
newest added

Now that we've pushed up the initial spike for token provisioning with InfluxDB v2, we need to discuss the next step: token scopes. Currently our CRD looks like: ```yaml apiVersion:...

the pr for this change is here: https://github.com/influxdata/influxdb/pull/19494

The K8s operator libraries have been updated. We should update this to work with them.

When InfluxDB scales up to more than 1 we need to add https://github.com/influxdata/influxdb-relay on top of it. if it scales down to 1 we can remove it.

area/influxdb

We need to change containerPort and servicePort according with the one specified via spec

area/influxdb

Chronograf supports port but changing it k8s doesn't change the containerPort and the service port

kind/bug
area/chronograf

Data in InfluxDB are stored on file system. at the moment we are not creating volumes or whatever. my current opinion is that we should continue in this way plus...

kind/feature
area/influxdb

We need to figure out how to bootstrap the kapacitor configuration via spec in our kapacitor crd. I tried to import kapacitor in our operator as we did for InfluxDB...

area/kapacitor

Chronograf supports multi source configuration via file. At the moment our spec only support one InfluxDB and Kapacitor via env var. we should replace it

kind/feature
area/chronograf