Re: [kubernetes-users] Unique DNS records for every pod in a autoscaled deployment

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

Re: [kubernetes-users] Unique DNS records for every pod in a autoscaled deployment

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:

Re: [kubernetes-users] Unique DNS records for every pod in a autoscaled deployment

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

Re: [kubernetes-users] Unique DNS records for every pod in a autoscaled deployment

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

[kubernetes-users] 2018-03-01 SIG Storage Community Update - Invitation to view

I've shared an item with you: 2018-03-01 SIG Storage Community Update https://docs.google.com/presentation/d/1VNQQ9Lzn6ahy9zHm0aE6KOzS6YzCREzNE2Jla2ESbC8/edit?usp=sharing=5a9841b7 It's not an attachment -- it's stored online. To open this item, just click the link above. SIG Storage -

[kubernetes-users] Re: Network Policy restricts ingress controller

On Wednesday, July 19, 2017 at 5:53:18 PM UTC+3, mrpanigale wrote: > I am unable to define a network policy that allows an ingress controller > > > Example: > > > Pod in namespace A > Ingress controller in namespace kube-system > > > Policy: > > kind: NetworkPolicy > apiVersion:

Re: [kubernetes-users] Unique DNS records for every pod in a autoscaled deployment

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,

[kubernetes-users] Re: question answering for kubernetes community

Cool. Let's make sure that 1. this is public data, 2. but users can opt out. We as a community have numerous obligations here and need to be careful. On Thu, Mar 1, 2018 at 2:46 PM, Jorge Castro wrote: > Since we already index the channels publically with slackarchive I

Re: [kubernetes-users] Unique DNS records for every pod in a autoscaled deployment

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

[kubernetes-users] Re: question answering for kubernetes community

Since we already index the channels publically with slackarchive I didn't think it would be a problem, however I'll take an item to get a clear policy on this and make it visible. On Thu, Mar 1, 2018 at 1:14 AM Alexis Richardson wrote: > Does this present any data collection

[kubernetes-users] minikube: setting proxy inside minikube

Hi, I am trying to run fabric8 on Kubernetes with the help of minikube. I am working behind a corporate proxy with authentication enabled. I am running Ubuntu 16.04.3 LTS. And I have set http_proxy, http_proxy and and no_proxy on /etc/environment. And then I have started minikube (with

[kubernetes-users] Unique DNS records for every pod in a autoscaled deployment

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,