Currently, VictoriaMetrics components supports secrets reading from on-disk filesystem. It improves security for general case, when service owner doesn't share access to it with other users.
In case, of operator based deployments, when scrapping and alerting configuration delegated to the users. It could be an issue.
For instance, vmalertmanagerconfig may have a following configuration:
We could extend the following configuration param https://docs.victoriametrics.com/operator/api/#arbitraryfsaccessthroughsmsconfig to the other components, that using filesystem secrets.
Currently, VictoriaMetrics components supports secrets reading from on-disk filesystem. It improves security for general case, when service owner doesn't share access to it with other users.
In case, of operator based deployments, when scrapping and alerting configuration delegated to the users. It could be an issue.
For instance, vmalertmanagerconfig may have a following configuration:
We could extend the following configuration param
https://docs.victoriametrics.com/operator/api/#arbitraryfsaccessthroughsmsconfig
to the other components, that using filesystem secrets.