j_r0dd

create a new user and have that user running the container. here's a couple snippets from relevant sections of code from here https://github.com/k8s-at-home/container-images/blob/main/base/ubuntu/Dockerfile ``` RUN \ adduser kah \ --uid...

Very nice! It seems that a lot of images are using Tini over S6 these days. You did a great job on this btw. I did create a helm chart...

I just wanted to report that I'm also having the same problem. I have a single node cluster so I only ever define 1 replica if the chart pre-defines more....

the more i mess with this i'm starting to think this not a flux issue....

@alokhom try running this [tool](https://github.com/kubernetes-sigs/kubectl-check-ownerreferences). it's definitely finding some discrepancies in owner uid. my issue is not a flux issue, now to find the cause...

I have been searching for the proper way to go about this with devices that may not have the same interface name. I go a layer deeper with this though....

So one way I've found to at least keep the interface names uniform on Ubuntu is forcing the interface name by mac. I just use a template with Ansible when...

Everything went smooth for the most part. Just had to make some adjustments for Flux to not deploy the CR's before the chart is deployed. It did take a couple...

hmm definitely getting spammed with alerts every time flux reconciles my git repo because of that validating webhook.

yeah it's after. i'll open a new issue regarding that.