1-21 - K8S No Service Available
Possible Reason
- The current service is not loaded correctly.
- The configured Pod does not exist in the current instance service.
Troubleshooting and resolution steps
You can use some third-party tools or jstack [PID] > jstack.log
to analyze the stack information and locate it.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified January 3, 2023: Merge error code 3-3 to 3-8, 6-4 to 99-0. (#1796) (a687d30ae)