Question

MariaDB POD wasn't able to expose port

To make it sort, I have successfully created MariaDB pod using YAML manifest, then exposes it as service to port 3306 using NodePort.

Until that step, everything seems normal, kubectl didn’t give error messages, but MariaDB cannot be accessed from outside (external IP)

Troubleshooting steps I’ve done:

  1. I have opened MySQL 3306 port on the firewall.
  2. I enter into MariaDB environment pod/docker via the kubectl command exec MariaDB /bin/bash and then run mysql -u root -p, the database responds normally
  3. I do SSH to the node where MariaDB image is located, and probing the port opened with telnet, and the results cannot be connected
  4. Node’s External IP that I use can be connected properly from my local PC, proofed by I can directly do SSH from my local PC.

I understand, that exposing MySQL to a public IP is a dangerous practice. I did this in order to review Kubernetes DigitalOcean service for converting an existing application to Kuberneter Digital Ocean.


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hello,

I just came across this question. What is the output of the following command:

  1. kubectl get svc

Also, can you share the exact YAML file that you are using?

Regards, Bobby