You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the sysdump doesn't collect the CiliumConfig CR (not the configmap) as far as I can see. When users are using the OCP platform, it will be a little hard for us to reproduce their issue. I hope we can collect the CiliumConfig CR so we can be more user friendly for the OCP users.
Maybe we should consider a better way to collect all the cilium CR in the long run. For example, we should be able to run kubectl get crd | grep cilium to understand all the CRD on this cluster, then collect the CR all together without doing this one by one in the code.
Describe the solution you'd like
in the short term, I hope we should collect CiliumConfig for OCP. in the long term, we should collect all cilium related the CR all togethers
The text was updated successfully, but these errors were encountered:
Proposal / RFE
Currently the sysdump doesn't collect the CiliumConfig CR (not the configmap) as far as I can see. When users are using the OCP platform, it will be a little hard for us to reproduce their issue. I hope we can collect the CiliumConfig CR so we can be more user friendly for the OCP users.
Maybe we should consider a better way to collect all the cilium CR in the long run. For example, we should be able to run
kubectl get crd | grep cilium
to understand all the CRD on this cluster, then collect the CR all together without doing this one by one in the code.Describe the solution you'd like
in the short term, I hope we should collect CiliumConfig for OCP. in the long term, we should collect all cilium related the CR all togethers
The text was updated successfully, but these errors were encountered: