Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

access lost after pod restart #2

Open
cbalan58 opened this issue Oct 8, 2022 · 0 comments
Open

access lost after pod restart #2

cbalan58 opened this issue Oct 8, 2022 · 0 comments

Comments

@cbalan58
Copy link

cbalan58 commented Oct 8, 2022

Hi, i've used this and it worked (without namespace though) but then i wanted to test it more and restarted the pod via kubectl delete. All is fine from kube side, but i cannot access the port that NodePort is supposed to nat on my node.
I deleted further the deployment and service and had them recreated again from yaml but same result, gogs seems to be dead.
I also tried changing from Nodeport to external-ip and while deployment went ok i still wasn't able to reach intended http port.
Pod log is fine, no err and i do have another nginx pod running just fine so no idea where to look anymore.
Any idea why restarting the pod went downhill?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant