Viacheslav Vasilyev

> we should really fix this in the package itself, it isn't too hard to auto-detect, and not worth end-user time/energy :) on the other hand, you can of course...

@m4h1r what will be `chcp` command output in cmd and powershell on your end? ps. in my case I had to rollback the following commit https://github.com/enkessler/childprocess/commit/0230cf96ce2fb15eb7c9538b14d75f7b50f3e505

have you tried on Windows Terminal?

I'm using Windows Terminal, with rolled back https://github.com/enkessler/childprocess/commit/0230cf96ce2fb15eb7c9538b14d75f7b50f3e505

Based on Vault docs from [here](https://www.vaultproject.io/docs/auth/kubernetes#kubernetes-1-21) > In response to the issuer changes, Kubernetes auth has been updated in Vault 1.9.0 to not validate the issuer by default. as a...

As far I can see the bound_issuer / BoundIssuer setting in Vault JWT auth logic is optional and verification is skipped if it's not specified. JWT auth backend does support...

coming back to your question @maelvls I assume it can be closed with a remark similar to one in HashiCorp Vault documentation

There was @SpectralHiss comment in another similar issue here https://github.com/cert-manager/cert-manager/pull/4524#issuecomment-1072238158

I'm thinking about to not block the metadata ip at all, and give imdsv2 a try

I know that's quite old topic, but I see that you're following your own tagging strategy on Vault container images, in the same time I see hardcoded version checks in...