You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported internally some time ago during a CaaSP upgrade, afterwards CAP stopped responding.
Since there's a bit of a race condition at play, it looks like Stratos came up first and grabbed port 80. The operator changed the NodePort of susecf-console-ui-ext to be on port 8080 instead of port 80 and everything worked again.
On the docs end we've been asked to document to not use port 80 by default when using load balancers with Stratos. This has been added and works as a short-term fix, but would be better in the long-term if changed on the Stratos end so users are not doing these additional steps.
The text was updated successfully, but these errors were encountered:
Copy pasta backstory from SUSE/doc-cap#351
On the docs end we've been asked to document to not use port 80 by default when using load balancers with Stratos. This has been added and works as a short-term fix, but would be better in the long-term if changed on the Stratos end so users are not doing these additional steps.
The text was updated successfully, but these errors were encountered: