Brandon Wulf

Here's a hacked workaround (in my update script): ```bash ( RELEASE_VERSION=$(wget -qO - "https://api.github.com/repos/siderolabs/talos/releases/latest" | grep -Po '"tag_name": "v\K.*?(?=")') && CURRENT_VERSION=$(talosctl version --client | grep 'Tag:' | grep -oP 'v[0-9]+.[0-9]+.[0-9]+')...

I can confirm the TLP fork works with 3.11.0.

So... why didn't this get merged during the last release?

I think this is an actual (and ongoing!) issue- I'm running v1.2.2 with kubernetes 1.23.4 and am seeing the same problem. I've just run through `talos apply-config`, `talos upgrade`, and...

Ah! Thanks @smira - I see from a [clarifying comment](https://github.com/siderolabs/talos/pull/5959#discussion_r928987808) you made on #5959 that talos will never update the kube-proxy manifest! I haven't fully groked WHY kube-proxy isn't updated...

This can also change the value type: string ``` user: username: '123456' ``` becomes int ``` user: username: 123456 ```

@logicfox, I agree that it would be really convenient to be able to define clients with CRDs, but this doesn't currently work -- as the [documentation](https://github.com/dexidp/dex/blob/master/Documentation/storage.md#kubernetes-custom-resource-definitions-crds) states, "Admins should not...

Yes, logs would go to the console (standard out) and any configured log file.