cilium-cli icon indicating copy to clipboard operation
cilium-cli copied to clipboard

Reduce sysdump warnings

Open pchaigno opened this issue 3 years ago • 2 comments

Almost every time someone takes a sysdump on a Cilium-managed cluster, they end up with a bunch of warnings:

⚠️ Deployment "hubble-relay" not found in namespace "kube-system" - this is expected if Hubble is not enabled
⚠️ Deployment "hubble-ui" not found in namespace "kube-system" - this is expected if Hubble UI is not enabled
⚠️ Deployment "clustermesh-apiserver" not found in namespace "kube-system" - this is expected if 'clustermesh-apiserver' isn't enabled
⚠️ The following tasks failed, the sysdump may be incomplete:
⚠️ [11] Collecting Cilium egress NAT policies: failed to collect Cilium egress NAT policies: the server could not find the requested resource (get ciliumegressnatpolicies.cilium.io)
⚠️ [12] Collecting Cilium local redirect policies: failed to collect Cilium local redirect policies: the server could not find the requested resource (get ciliumlocalredirectpolicies.cilium.io)
⚠️ [17] Collecting CiliumClusterwideEnvoyConfigs: failed to collect CiliumClusterwideEnvoyConfigs: the server could not find the requested resource (get ciliumclusterwideenvoyconfigs.cilium.io)
⚠️ [18] Collecting CiliumEnvoyConfigs: failed to collect CiliumEnvoyConfigs: the server could not find the requested resource (get ciliumenvoyconfigs.cilium.io)
⚠️ [23] Collecting the Hubble Relay configuration: failed to collect the Hubble Relay configuration: configmaps "hubble-relay-config" not found
⚠️ Please note that depending on your Cilium version and installation options, this may be expected

Most of the time all of the warnings are fine to ignore. We even add one more warning at the end to say that all warnings may be expected :rofl:

Instead, we could (should?) check the configuration to determine if there's really a need for a warning. For example, the warning below is not needed if the egress gateway is disabled (default):

⚠️ [11] Collecting Cilium egress NAT policies: failed to collect Cilium egress NAT policies: the server could not find the requested resource (get ciliumegressnatpolicies.cilium.io)

pchaigno avatar Sep 07 '22 13:09 pchaigno

@pchaigno is there something already WIP?

otherwise I would like to work on the issue

f1ko avatar Sep 12 '22 21:09 f1ko

@F1ko Nothing in progress that I know of. Feel free to send a PR.

pchaigno avatar Sep 13 '22 08:09 pchaigno