iamasmith
iamasmith
Also experiencing this issue today and pinning to 4.24.0 to avoid and agree this is a regression.
The GKE Sandbox notes say that you need another nodepool without sandboxing to be able to use it, as the default node pool would be the first up I think...
@mist714 raised an PR for this which was merged on the 14th November 2023 (PR 236) which builds the Linux binaries with CGO_ENABLED=0 so should avoid these issues with glibc...
@PAI5REECHO this project publishes MDNS announcements, it doesn't resolve them - the use cases will be hosts outside of your cluster and it does not directly cater for the scope...
This is really lacking in explanation but it does actually work. The help from the verify command states.. skopeo-test:/# notary verify --help Verifies if the data passed in STDIN is...
Additional note, looking at PTR handling there are obvsiouly conflicts in the PTR records generated. Only one can be relevant so advertising multiples in MDNS may have unpredictable behaviour. I...
correction pushed to the refactor commit.
@pl4nty thanks so much! I really, really appreciate your review! You know the pattern, I was swapping annotations back and forth in names for correctness and I actually went with...
@blake to ensure compatibility with the new changes merged for the security update I've cherry picked @Stelminator and my updates merged to master to this branch so any builds off...
Actually, I'll reorder these commits tonight so the cherry-picked ones appear first and they _should_ disappear from the MR.