Do you have more details on the resource you were running out of on the
Tomcast containers? Were you CPU bound? Perhaps K8s is limiting the number
of CPU's available in a different fashion than what docker was.
Could you include the Tomcat iostat, vmstat, etc. output?
-EJ
On Tue, Sep 19, 2017
I'm surprised there isn't more native Kubernetes integration. Their
documentation mentions this:
- KUBERNETES enables the kubernetes check if set (KUBERNETES=yes works).
KUBERNETES_COLLECT_EVENTS enables event collection from the kubernetes API,
given that KUBERNETES is also set. Note:
Does it require a single stable IP address or a range? You could possibly have
a set of dedicated nodes for you outbound proxy; that way you can still use
Kubernetes machinery for deployment, pod lifecycles, etc., but still present a
stable CIDR to the outside world.
-EJ
On Monday, May 1, 2017,
Definitely an interesting question!
At Yahoo, we've generally separated the underlying infrastructure based on
whether our CI/CD infrastructure is performing the deployment versus if a
developer is manually making changes. Mapping to Box's definition, "dev" is one
very locked down K8s
blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px
#715FFA solid !important; padding-left:1ex !important; background-color:white
!important; } You could also have something in your program that allocates
memory off java's heap. Here is a simplified program you can use to
