Samuel
Samuel
Hey This is indeed quite a critical issue that's being raised here. That terraform helm provider is not capable to spot in-cluster changes. Which makes it quite unique, in terms...
really, this does not exist?!! 👍
In our case, we won't be able to adjust our code, at least until this behavior is consistent. Only a few of our security groups, created in the last few...
I could work around this re-building my image and pinning kubernetes to 33.1.0 I also found that issue in some controller of mine. That one connects to kubernetes.default.svc, as well...
> Downgrading to v33.1.0 wouldn't honour HTTP_PROXY or HTTPS_PROXY at all Maybe we should point out this behavior is consistent with kubectl/oc clients would work. Doesn't mean you can't use...
running ansible-operator based controllers, 2.6.0 broke a bunch of my code too won't merge those renovate PRs for now, sticking to `urllib3==2.5.0`