-
I can see the events below when I run the command
oc describe node:Warning listen tcp4 :XXXXX: bind: address already in use 5s kube-proxy can't open port "nodePort for <namespace>/<service>" (:XXXXX/tcp4), skipping it Warning listen tcp4 :Y
Why do I get events like "kube-proxy can't open port nodePort for XXX/YYY" on RHOCP 4?
Solution verified - Updated on
Request a new translation or translation update
A translation for your language preference does not exist. Click below to request a translation for your selected language.
Issue
Subscriber Exclusive Content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.