Karl Stoney comments

Results 175 comments of


                                            Karl Stoney

Native Sidecars draining erroneously sending connection: close for outbound requests

That hacky script was never part of istio. It was my hacky script I baked into my custom proxy image.

Native Sidecars draining erroneously sending connection: close for outbound requests

Istio maintainers - can we remove the stale label? This issue is absolutely an issue and imo is a blocker for people using native sidecars, which more and more people...

Native Sidecars draining erroneously sending connection: close for outbound requests

Hmm not sure? I use native sidecars fine now, I just simply removed the `preStop` hook that istio adds when native sidecars is enabled which is what triggers this behaviour...

Native Sidecars draining erroneously sending connection: close for outbound requests

Aye, it's crude, i just removed it from the template.

Istioctl says fromNamespaces in CUSTOM AuthZ policy is not valid, but it appears to be

@hzxuzhonghu i don't think i understand you? I'm saying: ``` spec: action: CUSTOM provider: name: some-external rules: - from: - source: namespaces: - whatever ``` Is valid config, is accepted...

Istioctl says fromNamespaces in CUSTOM AuthZ policy is not valid, but it appears to be

``` ❯ kubectl get validatingwebhookconfiguration istio-validator-istio-system NAME WEBHOOKS AGE istio-validator-istio-system 1 669d ``` yup 🤔 ``` ❯ cat

'Teslamate ID' isn't retained - ValueError: invalid literal for int() with base 10: ''

I also have this issue! No error logs in anything however. Cannot get it to save the id, it's just `unknown`.

'Teslamate ID' isn't retained - ValueError: invalid literal for int() with base 10: ''

OK restarting the teslamate addon and it's now `1`

MALFORMED_FUNCTION finishReason in Gemini candidate

Also getting this! I resolved it by making sure all function names were `snake_case`, i had some that were `some-thing-And-Caps`

[Feature]: Add transform processor

4mb it seems. In my opinion jaeger should bundle the common processors, one of the advantages to switching to the otel collector is that we're able to leverage the pipelines!