Pat Riehecky
Pat Riehecky
##### SUMMARY Currently there is Helm support with the ansible kubernetes collection. This is great for managing packages, but not all operators are bundled up as Helm charts. Adding support...
Adds metrics for the cachevault status. Hardware tested: `LSI MegaRAID SAS-3 3108 [Invader] (rev 02)`
While this runs inside `kube-system` in many cases, it would be nice if the defaults for the deployment met the restricted context. The helm chart currently has a number of...
It would be nice if the pod had a prometheus compatible metrics endpoint (with optional `ServiceMonitor` from helm).
These hardening bits were recommended by the trivy scanner. https://github.com/aquasecurity/trivy https://github.com/aquasecurity/trivy-operator
For my auditors, they want the registry listed for each container we are running. Storing it here makes generating my reports much easier.
The `app.kubernetes.io/` labels are becoming part of the standard way of labeling things within the infrastructure. Can this be updated to start applying those labels to various elements?
I'm not sure how the various deployment elements are created, but it would be nice if the `rancher/local-path-provisioner` bits where explicit about `docker.io` (ie . `docker.io/rancher/local-path-provisioner`)
It would be nice if there was a network policy for the `local-path-provisioner` pod that only permitted the required traffic. I don't think any `ingress` is required. If I understand...
The instructions are a bit vague and I'm unable to sort how to build a telegraf.conf like: ```toml [[inputs.kafka_consumer]] brokers = [ "kafka-bootstrap.kafka:9092" ] client_id = "opmon-telegraf" consumer_group = "opmon-telegraf"...