Oldřich Jedlička

> [@oldium](https://github.com/oldium), I'm a but puzzled with your wording, did the update fix the issue discussed here? Or disabling fixed it and the update was a general recommendation? It worked...

Unfortunately, the problem hit me again. I am trying to disable network interfaces, because of the Event Log message, but after disabling like 3 interfaces (including hidden ones) I got...

This time it was probably caused by having the WSL window opened on the second user account. WSL is probably not able to run for two users simultaneously. Sorry for...

Our workaround was to define such variables directly in the POD's Env, not in EnvFrom ConfigMap, this is what OTEL Operator could read. I prepared a fix for this in...

Yeah, but "toContainValues" is a perfect method name for arrays too. And it worked like that. That is the point. Intuitive API is what makes the library great. If people...

> 3. We have the ~`toContain*`~ `toInclude*` matchers, which are meant for arrays. Ironically, this is *exactly* what I am talking about. You have to double-check before using the function...

Tested ConfigMaps with custom built image `oldium/opentelemetry-operator:configmaps-2024-10-20-1` on our test cluster.

Handling Secrets requires updated permissions, otherwise it ends up with: ``` failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:opentelemetry-operator-system:opentelemetry-operator-controller-manager" cannot list resource "secrets" in API group "" at the...

So the Secrets code works fine with the following kustomize patch to the Release asset (it syncs value to `config/rbac/role.yaml` state). Here is what I tested: ``` apiVersion: kustomize.config.k8s.io/v1beta1 kind:...

> can you adjust an E2E test to ensure this logic works as expected? You mean to add e2e tests for ConfigMaps and Secrets to ensure it works, right? Sure.