Quieten expected warnings #1962
Description
When running cilium sysdump in a kind dev environment with a relatively simple deployment, the command complains with many warnings that do not need to be warned about:
...
I0911 16:35:09.580937 3224081 request.go:697] Waited for 1.167974212s due to client-side throttling, not priority and fairness, request: GET:https://127.0.0.1:41805/api/v1/namespaces/kube-system/pods?labelSelector=k8s-app%3Dcilium
⚠️ ConfigMap "spire-agent" not found in namespace "kube-system" - this is expected if SPIRE installation is not enabled
⚠️ ConfigMap "spire-server" not found in namespace "kube-system" - this is expected if SPIRE installation is not enabled
I0911 16:35:19.780446 3224081 request.go:697] Waited for 2.945800215s due to client-side throttling, not priority and fairness, request: GET:https://127.0.0.1:41805/api/v1/namespaces/kube-system/pods/cilium-d7rr7/log?container=mount-bpf-fs&limitBytes=1073741824&sinceTime=2022-09-11T23%3A35%3A12Z×tamps=true
I0911 16:35:29.780784 3224081 request.go:697] Waited for 3.779628289s due to client-side throttling, not priority and fairness, request: GET:https://127.0.0.1:41805/api/v1/namespaces/kube-system/pods/kube-controller-manager-kind-control-plane/log?container=kube-controller-manager&limitBytes=1073741824&sinceTime=2022-09-11T23%3A35%3A12Z×tamps=true
⚠️ The following tasks failed, the sysdump may be incomplete:
⚠️ [12] Collecting Cilium egress NAT policies: failed to collect Cilium egress NAT policies: the server could not find the requested resource
⚠️ [13] Collecting Cilium Egress Gateway policies: failed to collect Cilium Egress Gateway policies: the server could not find the requested resource (get ciliumegressgatewaypolicies.cilium.io)
⚠️ [15] 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 Cilium endpoint slices: failed to collect Cilium endpoint slices: the server could not find the requested resource (get ciliumendpointslices.cilium.io)
⚠️ [23] Collecting CiliumClusterwideEnvoyConfigs: failed to collect CiliumClusterwideEnvoyConfigs: the server could not find the requested resource (get ciliumclusterwideenvoyconfigs.cilium.io)
⚠️ [24] Collecting CiliumEnvoyConfigs: failed to collect CiliumEnvoyConfigs: the server could not find the requested resource (get ciliumenvoyconfigs.cilium.io)
⚠️ [25] Collecting Cilium BGP Peering Policies: failed to collect Cilium BGP Peering policies: the server could not find the requested resource (get ciliumbgppeeringpolicies.cilium.io)
⚠️ [32] Collecting the Cilium Envoy configuration: failed to collect the Cilium Envoy configuration: configmaps "cilium-envoy-config" not found
⚠️ [35] Collecting the Hubble Relay configuration: failed to collect the Hubble Relay configuration: configmaps "hubble-relay-config" not found
⚠️ [64] Collecting GatewayClass entries: failed to collect GatewayClass entries: the server could not find the requested resource
⚠️ [65] Collecting Gateway entries: failed to collect Gateway entries: the server could not find the requested resource
⚠️ [66] Collecting ReferenceGrant entries: failed to collect ReferenceGrant entries: the server could not find the requested resource
⚠️ [67] Collecting HTTPRoute entries: failed to collect HTTPRoute entries: the server could not find the requested resource
⚠️ [68] Collecting TLSRoute entries: failed to collect TLSRoute entries: the server could not find the requested resource
⚠️ [69] Collecting GRPCRoute entries: failed to collect GRPCRoute entries: the server could not find the requested resource
⚠️ [70] Collecting TCPRoute entries: failed to collect TCPRoute entries: the server could not find the requested resource
⚠️ [71] Collecting UDPRoute entries: failed to collect UDPRoute entries: the server could not find the requested resource
⚠️ [74] Collecting Tetragon tracing policies: failed to collect Tetragon tracing policies: the server could not find the requested resource (get tracingpolicies.cilium.io)
⚠️ Please note that depending on your Cilium version and installation options, this may be expected
This gives the impression that the sysdump might not have been successful, when really it has correctly gathered all of the information it can based on the configuration of the cluster.
Cilium CLI should autodetect when these resources are in use or not, and just pull them if available rather than complaining if they're not used. We don't need to emit warnings if users are not running the latest SPIRE configurations or specialist NAT / LRP policies or they're not using Gateway API.