Dan Foulkes
Dan Foulkes
How is this not solved yet? This flow is now common place for most businesses using AWS as a primary IT solution. I appreciate the landscape has moved on abit...
hey guys, did anyone resolve the iOS 9+ issues with Apple's rewrite?
Personally I've just been mainitaining my own custom `values.yml` file that has my preffered dnsmasq settings: Doing this you can perist your custom settings between deployment plus ideal for automating...
Just seen you wanted CNAME not A record lol. Ok, good point personally haven't hit this issue. Curiously, what's the usecase a `ingress` class?
Looking through the spec, there's option todo this the same way I proposed for A records. have you tried this in the `values.yml` ```yaml dnsmasq: customCnameEntries:: # Here we specify...
Fare point, if its the public facing element that concerns you and you're not overally bothered by the cosmetics, you could just supply a different value file that's not in...
hey, if you're using metalb on k3s with a single IP it can become quite templemental assigning the same IP twice. Personally, I found using the work around that works...
Any news on when this will be fixed?
It still looks like this solution is based on the user supplying the bearer token at initially. I didnt check the whole package, but I don't think it automatically refreshes...