Michi Mutsuzaki
Michi Mutsuzaki
noticed this while backporting to v1.11 here: https://github.com/cilium/cilium/pull/20842 😞
steps to repro using kind from @mauilion: ``` cat > kind-config.yaml
follow up: - create a new CLI. - latest master breaks
tracking cilium-cli release in https://github.com/cilium/cilium-cli/labels/release-blocker%2Fv0.10.4
> Should we enable --debug to log the error returned by nslookup? for some reason `nslookup -debug` always exit with a non-zero return code 😐 > Can we collect coredns...
opened https://github.com/cilium/cilium-cli/pull/426 to capture sysdump when a job times out
we should test this with the new sysdump command. transferring the issue.
steps to repro: - follow https://docs.cilium.io/en/v1.10/gettingstarted/k8s-install-default/ to create an eks cluster and install cilium. use `cilium-cli: v0.8.1`. - run the connectivity check: ``` cilium hubble enable cilium hubble port-forward& cilium...
i think @willfindlay 's concern is that the traffic is not encrypted, so if you expose the grpc endpoint as a service, anybody on the network can connect to it....
@dependabot rebase