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
We are at OKD 4.5 and when one worker node is having network issue, the application getting dns issue when the request is hitting that problematic node.
#1092
We are at OKD 4.5 and when one worker node is having network issue, the application getting dns issue when the request is hitting that problematic node. Also we are not able to bring down that problematic node dns pod, its automatically recreate. So how to handle this type of scenario. We are already in the process of upgrading version to OKD 4.9. we dont have any zones in dns.operator/default
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are at OKD 4.5 and when one worker node is having network issue, the application getting dns issue when the request is hitting that problematic node. Also we are not able to bring down that problematic node dns pod, its automatically recreate. So how to handle this type of scenario. We are already in the process of upgrading version to OKD 4.9. we dont have any zones in dns.operator/default
Beta Was this translation helpful? Give feedback.
All reactions