-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I setup a cluster using k3s on 3 vm's running on 3 different physical servers then imported the cluster to rancher. I'm having some issues with deploying workloads though. For testing purposes I'm trying to run the Homer [dashboard](https://github.com/bastienwirtz/homer) with 3 replicas that each read and store their configuration files to a single NFS share on another server. That way, in theory I can just point the DNS name to a load balancer and always have the service running if one or two nodes go down. When I do this, I can see that the sub-volume is created on the NFS server, but none of the configuration files from the container are written to the directory and the pod crashes over and over. I'm setting my mount point as /www/assets for the container (Where the configuration is kept). I can get the dashboard to launch if I mount to a different directory that does not contain the config files, but then still nothing is appearing in the NFS Share so I'm unable to change the config files unless I exec into the container. I also have my PVC set for single and multiple node read-write.