K
Q

Multiple pods and nodes management in Kubernetes

12/1/2017

I've been digging the Kubernetes documentation to try to figure out what is the recommend approach for this case.

I have a private movie API with the follow microservices (pods).

- summary
- reviews
- popularity

Also I have accounts that can access these services.

  1. How do restrict access to services per account e.g. account A can access all the services but account B can only access summary.
  2. The account A could be doing 100x more requests than account B. It's possible to scale services for specific accounts?
  3. Should I setup the accounts as Nodes?

I feel like I'm missing something basic here.

Any thoughts or animated gifs are very welcome.

--
deployment
kubernetes

Similar Questions

unable to access DB pod External IP from application
How do I load multiple templated config files into a helm chart?
How do I access the current user in a helm chart template
Request to URL defined with ingress.kubernetes.io/auth-url annotation is done with HTTP/1.0

1 Answer

12/3/2017

It sounds like this is level of control should be implemented at the application level.

Access to particular parts of your application, in this case the services, should probably be controlled via user permissions. Similar line of thought for scaling out the services...allow everything to scale but rate limit up front, e.g., account A can get 10 requests per second and account B can do 100x. Designating accounts to nodes might also be possible, but should be avoided. You don't want to end up micromanaging the orchestration layer :)

-- HammerMeetNail
Source: StackOverflow