bewing
bewing
> @boseadler can you share a peak on how you did it in the kustomize file? I'm struggling with this part to add certain taints: tolerations: | - key: "node.kubernetes.io/unreachable"...
@ncapps or @knverey can I get a review of this PR?
I'm still seeing single-line output from the Github API in my location (Chicago, IL) ```nowrap $ dig AAAA +short github.com $ dig +short github.com 140.82.114.3 $ curl -s https://api.github.com/repos/kubernetes-sigs/kustomize/releases |...
Haven't thought about this in a bit. Might the best approach be to: * Download `https://api.github.com/repos/kubernetes-sigs/kustomize/releases`, store it as a variable, and test its line length * If line length...
/reopen /remove-lifecycle rotten
/reopen /remove-lifecycle rotten
Even if the random allocated CIDR isn't advertised via BGP, I still see it installed into the routing table for the node (pointing at `cilium_host`) when configured in native routing...
Testing shows that the route doesn't affect pods (because eBPF forwards it out), but the node itself considers it a blackhole. LMK if I should file a separate issue for...
@srebhan Thank you for taking the time to look at this! I'm sorry my change resulted in so much work! I can confirm that the PR build works for tagging...
Closed via #1750