Unavailable endpoint after scale down for Application in Pod

Bug #1632312 reported by Sergey Kraynev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
k8s-docker-suite-app-murano
Triaged
Medium
Dmytro Dovbii

Bug Description

Intro:
Right now we expose WEB access to some Applications in Pod via Gateway node.
So basically we have 1 endpoint - 1 gateway node, and user may reach the same UI (url) by several addresses.

However it has issue if we scale up/down gateway nodes in cluster.
Because Log for deployed App will not be updated after scaling.

Example:
1. deploy Kubernetes Cluster with 2 Gateway Nodes, 1 Pod, 1 Docker Artifactory in this Pod
2. You will get log that UI for Artifactory is availbale by 2 Urls

3. Execute Scale Down and Cluster by update
 However log for Pod will be still the same - i.e. 2 Urls, one of which does not work now.

The same behavior you will if decide to scale up gateway nodes - i.e. new Urls will not be displayed in the log, but it will be accessible

Changed in k8s-docker-suite-app-murano:
assignee: nobody → Dmytro Dovbii (ddovbii)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.