That's such a broken assumption.
StatefulSet is the only primitive that satisfies this condition for now.
On Thu, Mar 1, 2018 at 1:48 PM, wrote:
> 1. Can't change the apparent hostname of the worker to be either an IP/
> dash-seperated IP worker DNS, as Airflow only
1. Can't change the apparent hostname of the worker to be either an IP/
dash-seperated IP worker DNS, as Airflow only supports a direct getfqdn call in
our version.
no - hostname detected on the pod has to be resolvable on other pods.
On Thursday, 1 March 2018 21:43:53 UTC, Tim Hockin wrote:
Does it have to be DNS? Are unique IPs sufficient?
On Thu, Mar 1, 2018 at 10:15 AM, wrote:
> I'm using Apache Airflow, which uses a scale out worker model.
>
> The workers run jobs, and the job logs are collected from the workers via a
> http call from a central
I'm using Apache Airflow, which uses a scale out worker model.
The workers run jobs, and the job logs are collected from the workers via a
http call from a central server. These pods definitely do have specific
identity, but they are not important individually in the way that StatefulSet
is
The short answer is that you are ascribing identity to pods that don't
really have any. They are literally called "replicas". If you need
identity, you really sort of want StatefulSet. If that doesn't work,
it would be good to understand more concretely what you're trying to
achieve.
On Thu,
Can you explain a bit more of the problem you are trying to solve? Generally
pods should be treated as anonymous unless you really need something like
StatefulSet.
A headless service will provide the IPs of all the pods, if that helps.
> On Mar 1, 2018, at 4:22 AM, james.mas...@jmips.co.uk
Hi list,
I'm following this guide:
https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pods-hostname-and-subdomain-fields
I wish to have each pod in a deployment have a unique hostname, which allows
another pod to contact each of the autoscaled pods by hostname.
However,