I would look at the network config, the flags on the master and kubelets,
and the existing namespace usages
On Dec 11, 2016 8:21 PM, "Bruno Bronosky" wrote:
> If you came into a new company with a production kubernetes cluster but
> they knew nothing about it (the person who set it up was gone)
If you came into a new company with a production kubernetes cluster but
they knew nothing about it (the person who set it up was gone) what would
you examine to get an understanding of it?
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion
On Dec 11, 2016 12:58 PM, wrote:
Hi Tim,
Thanks for your answer and sorry for not replying before, I didn't realize
I should check the group site for answers.
Your solution for exposing the server on given external IP worked,
specifically setting hostPort in pod's container spec.
The client j
Hi Tim,
Thanks for your answer and sorry for not replying before, I didn't realize I
should check the group site for answers.
Your solution for exposing the server on given external IP worked, specifically
setting hostPort in pod's container spec.
The client job runs in a single-node cluster,
Yes but nginx ingress controller does support for TCP balancing with custom
ports.
On Sunday, December 11, 2016 at 7:06:23 AM UTC+1, Tim Hockin wrote:
>
> Ingress currently assumes ports 80 and 443
>
> On Dec 10, 2016 8:54 PM, "Paolo Mainardi" > wrote:
>
>> Hello everyone!
>> What i want to achi