Kevin comments

Results 8 comments of


                                            Kevin

The notifications-controller logging level keeps in “info” for argocd, although the config map argocd-cmd-params-cm configurarion is set to "error".

@ferchdav I can't reproduce this issue. Can you tell me how to reproduce it in detail?

The notifications-controller logging level keeps in “info” for argocd, although the config map argocd-cmd-params-cm configurarion is set to "error".

Sorry I can't reproduce this issue. What environment does this message appear in? Trigger on-sync-status-unknow result: [{[0].6SzWb05EK-0v90hwjytytTbN7S6A [app-sync-status-unknow]

The notifications-controller logging level keeps in “info” for argocd, although the config map argocd-cmd-params-cm configurarion is set to "error".

I still can't find the log in the gke environment.. how about actually checking the container log with the kubectl command?

The notifications-controller logging level keeps in “info” for argocd, although the config map argocd-cmd-params-cm configurarion is set to "error".

I can still only get the "error" log. If possible, could you check the container log?

The notifications-controller logging level keeps in “info” for argocd, although the config map argocd-cmd-params-cm configurarion is set to "error".

Did you restart the notification controller pod after you set up the configmap?

🐛 Bug Report: nestjs bootstrap fails due swagger being unable to serialize operations

feat: add ipv4/ipv6 dual stack support

Yes, I'm working on it. I'll answer as soon as possible

feat(hydrator): add inline parameter support to Source Hydrator (#24228)

Thanks @sangyeong01