Chris Pressland

@mothy-tim see new issue and PR raised above, this should fix this if it is accepted by the maintainers.

I'm also seeing this with Azure Redis: ```shell $ redis-cli -u $(kubectl get secret azure-redis -o go-template='{{.data.url_primary|base64decode}}') AUTH failed: WRONGPASS invalid username-password pair host.redis.cache.windows.net:6380> ``` In this case `.data.url_primary` is...

I can also replicate this for what it's worth.

@Seraphen did you ever figure this out? Switching to AVPlayer makes for a better experience for me. But I’m not sure of the Pros/Cons of MPV vs AVPlayer.

For now I've mitigated this with the following automation: ```yaml alias: Shed - Reload HomePod Config description: "" trigger: - platform: device type: turned_off device_id: af26fc2929912a7ed13c45ad61e3978b entity_id: 324f4059551f8f1247ddd097fdd1592e domain: remote...

We're also seeing this over the past 12 hours in our Staging environment, did you find a solution @sanjaydebnath

Thanks @jacobtomlinson - authentication is entirely driven by Service Accounts, with the app only getting ConfigMaps and Secrets from the same namespace.

Right, I finally had time to tackle this properly, here is a full Kubernetes Manifest set that should replicate this: ```yaml apiVersion: v1 kind: Namespace metadata: name: kr8s-test labels: team:...

Thanks @jacobtomlinson - as above I'm more than happy to spin up a fresh cluster on Azure if it helps.

right, I changed the install command to: `pip install git+https://github.com/kr8s-org/kr8s.git`, so this should be the `main` branch instead of v0.20.4: [log.txt](https://github.com/user-attachments/files/19011728/log.txt) I decided to include everything from the pod rather...