On 01/24/2017 10:21 AM, Heiko W.Rupp wrote:
Now when WildFly is deployed into Kubernetes or OpenShift, we
will see that WildFly is started, syncs and then dies at some point
in time, where k8s will not re-use the existing one, but start
a new one, which will have a different FeedId.
It might be interesting to re-read the following threads, as some ideas
were thrown around this subject already:
[Hawkular-dev] OpenShift Pet vs Cattle metaphor (10/13/2016)
[Hawkular-dev] Identification of WildFly in container in a
Kube/Openshift env (07/03/2016)
- Juca.