This article covers how to resolve the following issue:
A full restart was performed on the SMAX platform where has been restarted the Masters as well as the Workers. This was done in sequence as per the documentation.
After the restart does the kube-proxy fail to start on Master01. A reboot was also done on this server without any success.
When trying to start Master1 using ./kube-start.sh that it fails to complete the procedure and pops massage : connection refused: 8443 error.
Because of the above it's unable to run any kubectl commands on Master 1.
Micro Focus Community Manager
If this answered your question, please mark it as "Suggest as Answer" or "Verify as Answer".
If you found this post useful, please give it a "Like".