Scenario

So you have your Rancher 2.0 Kubernetes cluster up, and you update one of your apps.. Suddenly your site is down and you see the error

503 Service Temporarily Unavailable

Don’t freak out, theres a simple solution here. More likely than not, you setup your ingress to target a backend instead of a service.

Updating your app can often rename the ‘backend’, causing your initial ingress to be at a loss about what to point to.

Solution

Edit your app, expose the port as a Cluster IP and then edit your ingress to be a service which targets the exposed port.

Categories: Uncategorized

1 Comment

Pavel · March 1, 2019 at 1:42 pm

Thank you so much! is there any explanation for why this is happening?

Leave a Reply

%d bloggers like this: