Skip to content

access lost after pod restart #2

@cbalan58

Description

@cbalan58

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions