Ryfujk

Eww, those bytes are gross

I am on the US no-fly list. What can I do in order to be allowed on flights which go through US airspace?

A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?

The terminology for an excluded solution

PGF Plot settings

If I delete my router's history can my ISP still provide it to my parents?

Discrepancy in P/E ratio of stocks in Robinhood app?

Why did Bush enact a completely different foreign policy to that which he espoused during the 2000 Presidential election campaign?

Why avoid shared user accounts?

Why do neural networks need so many training examples to perform?

Am I a Rude Number?

Integral inequality of length of curve

What's a good word to describe a public place that looks like it wouldn't be rough?

What kind of hardware implements Fourier transform?

How to interpret this PubChem record of L-Alanine

Are Giants classified as Beasts or Beings?

What does "keynote company" mean?

How to replace the content to multiple files?

Copy large no of files of specific date to another directory?

Using only 1s, make 29 with the minimum number of digits

Do authors have to be politically correct in article-writing?

Can you earn endless XP using a Flameskull and its self-revival feature?

What do you call a fact that doesn't match the settings?

How can I improve my fireworks photography?

Why is Kubernetes (AWS EKS) registering all workers to the Load Balancer?

Scalable django app, should message queue be located on load balancer or app server?Google container engine / Kubernetes 1.1.1 - Service LoadBalancer not being createdHow does nodeAffinity work in DaemonSets?Connect AWS route53 domain name with K8s LoadBalancer ServiceIn AWS EKS, what security group allows access to master node from kubernetes client?In Kubernetes, how can a container created from a CronJob find out when it was scheduled?Kubernetes service vs Load balancerHow do I update the loadbalancer IP?Kubernetes CrashLoopBackOff after pod create pulling image from Docker HubHow to run a docker image on kubernetes that accepts command line arguments?

2

I want to know whether this is a default behaviour or something wrong with my setup.

I have 150 workers running on kubernetes.

I made a set of kubernetes workers (10 workers) run only a specific deployment using nodeSelector, I created a service (type=LoadBalancer) for it, when the Load Balancer was created all the 150 workers of Kubernetes were registered to the Load Balancer, while I was expecting to see only this set of workers (10 workers) of this deployment/service.

It behaved the same with alb-ingress-controller and AWS NLB

kind: Service

apiVersion: v1

metadata:

  name: my-service

spec:

  selector:

    app: my-app

  ports:

  - port: 8080

  type: LoadBalancer

and the deployment

apiVersion: apps/v1

kind: Deployment

metadata:

  name: my-app

spec:

  selector:

    matchLabels:

      app: my-app

  replicas: 10

  template:

    metadata:

      labels:

        app: my-app

    spec:

      containers:

      - name: master-api

        image: private/my-app:prod

        resources:

          requests:

            memory: 8000Mi

        ports:

        - containerPort: 8080

      nodeSelector:

        role: api 

I was already labeled 10 workers nodes with the label role=api
the 10 run only pods of this deployment, and no other worker is running this service
I also don't have another service or container using port 8080

amazon-web-services kubernetes

share|improve this question

asked 22 hours ago

EltorroooEltorrooo

1114

add a comment | 

2

I want to know whether this is a default behaviour or something wrong with my setup.

I have 150 workers running on kubernetes.

I made a set of kubernetes workers (10 workers) run only a specific deployment using nodeSelector, I created a service (type=LoadBalancer) for it, when the Load Balancer was created all the 150 workers of Kubernetes were registered to the Load Balancer, while I was expecting to see only this set of workers (10 workers) of this deployment/service.

It behaved the same with alb-ingress-controller and AWS NLB

kind: Service

apiVersion: v1

metadata:

  name: my-service

spec:

  selector:

    app: my-app

  ports:

  - port: 8080

  type: LoadBalancer

and the deployment

apiVersion: apps/v1

kind: Deployment

metadata:

  name: my-app

spec:

  selector:

    matchLabels:

      app: my-app

  replicas: 10

  template:

    metadata:

      labels:

        app: my-app

    spec:

      containers:

      - name: master-api

        image: private/my-app:prod

        resources:

          requests:

            memory: 8000Mi

        ports:

        - containerPort: 8080

      nodeSelector:

        role: api 

I was already labeled 10 workers nodes with the label role=api
the 10 run only pods of this deployment, and no other worker is running this service
I also don't have another service or container using port 8080

amazon-web-services kubernetes

share|improve this question

asked 22 hours ago

EltorroooEltorrooo

1114

add a comment | 

I want to know whether this is a default behaviour or something wrong with my setup.

I have 150 workers running on kubernetes.

I made a set of kubernetes workers (10 workers) run only a specific deployment using nodeSelector, I created a service (type=LoadBalancer) for it, when the Load Balancer was created all the 150 workers of Kubernetes were registered to the Load Balancer, while I was expecting to see only this set of workers (10 workers) of this deployment/service.

It behaved the same with alb-ingress-controller and AWS NLB

kind: Service

apiVersion: v1

metadata:

  name: my-service

spec:

  selector:

    app: my-app

  ports:

  - port: 8080

  type: LoadBalancer

and the deployment

apiVersion: apps/v1

kind: Deployment

metadata:

  name: my-app

spec:

  selector:

    matchLabels:

      app: my-app

  replicas: 10

  template:

    metadata:

      labels:

        app: my-app

    spec:

      containers:

      - name: master-api

        image: private/my-app:prod

        resources:

          requests:

            memory: 8000Mi

        ports:

        - containerPort: 8080

      nodeSelector:

        role: api 

I was already labeled 10 workers nodes with the label role=api
the 10 run only pods of this deployment, and no other worker is running this service
I also don't have another service or container using port 8080

amazon-web-services kubernetes

share|improve this question

asked 22 hours ago

EltorroooEltorrooo

1114

kind: Service

apiVersion: v1

metadata:

  name: my-service

spec:

  selector:

    app: my-app

  ports:

  - port: 8080

  type: LoadBalancer

apiVersion: apps/v1

kind: Deployment

metadata:

  name: my-app

spec:

  selector:

    matchLabels:

      app: my-app

  replicas: 10

  template:

    metadata:

      labels:

        app: my-app

    spec:

      containers:

      - name: master-api

        image: private/my-app:prod

        resources:

          requests:

            memory: 8000Mi

        ports:

        - containerPort: 8080

      nodeSelector:

        role: api 

share|improve this question

asked 22 hours ago

EltorroooEltorrooo

1114

share|improve this question

asked 22 hours ago

EltorroooEltorrooo

1114

asked 22 hours ago

EltorroooEltorrooo

1114

asked 22 hours ago

EltorroooEltorrooo

1114