BenB196

Hi @faust64 I patched the deployment with the subPath setting, and this does indeed solve the issue: ```yaml volumeMounts: - mountPath: /data name: data - mountPath: /tmp name: tmp -...

@faust64 I've gone ahead and tried the solution you provided with the following additions/changes to the helm chart: ```yaml initContainers: - args: - '-c' - | update-ca-certificates || echo warning...

I wanted to provide an update on this as I was able to have some time to debug this. From what I tell @faust64 your example works. What I believe...

Definitely would be a fan of this, currently using a standalone agent with terraform yaml template because there isn't a good way to add 500+ integrations to a single policy...

I'm seeing a similar issue, but even with some resources that are created by Terraform (on 2.13.1): Terraform output of a secondary plan run after the initial plan/apply. ``` Terraform...

The CRD has a schema: https://raw.githubusercontent.com/elastic/cloud-on-k8s/main/config/crds/v1/bases/elasticsearch.k8s.elastic.co_elasticsearches.yaml

Below is the full output of the terraform plan command, but there is no mention of `forces replacement`. Terraform Plan Output ```shell terraform plan Initializing the backend... Successfully configured the...

Just a quick update here, I did some further testing and it seems like any time there is a change under `manifest.spec.(daemonset|deployment).podTemplate` a `forces replacement` happens. Would anyone know where...

@brian-brazil If I understand you correctly, you are saying switch to SNMPv1 correct? If this is correct, it is slightly different then what I am requesting. The device itself """supports"""...

While I understand that this issue revolves around an incorrect implementation of SNMPv3 on the device itself. I don't think that being forced to use SNMPv1 is the correct solution...