Don Wonders

Ran into similar looking errors as above (502's, "http: proxy error: context canceled", and a long res.duration). In my case i had put requests/limits on the pod that we're too...

I ran into this issue as well on coreos/typhoon and with some modifications was able to get it working. Kubernetes v1.22.4 Distro: Typhoon OS: Fedora CoreOS (36) CRI: docker CNI:...

Running into this myself and found this issue. In my case, chart installation whose initial requirements end up needing to scale up underlying cluster resources can take variable and unpredictable...

made a comment with a workaround for this kind of functionality (dont believe it will work with nested blocks, but does work with nested attributes/objects/maps) https://github.com/minamijoyo/hcledit/issues/28#issuecomment-2313023116

@ldhenry I cranked the logs on our process when we create the environment. This one doesn't happen as often as the other issue i opened (#30), when it happens again...

I was able to reproduce using: ``` resource "launchdarkly_environment" "test" { count = 200 name = format("%v%v", "foo", count.index) key = format("%v%v", "foo", count.index) color = 200596 project_key = "default"...

The separate executions of terraform seek to manage independent environments of the same project. So they share feature flags in that each environment of the project contains the feature flags...

yeah I can take a stab at it

Ive noticed this too in other truechart helm charts. They all seem to use this pattern of embedding the `.Release.Revision` as a pod label, making none of them compatible with...

@jkandasa yes, and/or allow for disabling namespace management in the operator so that the namespace must be created and managed externally to the operator