Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nodes a objects #3

Open
bentterp opened this issue May 24, 2019 · 1 comment
Open

Nodes a objects #3

bentterp opened this issue May 24, 2019 · 1 comment

Comments

@bentterp
Copy link

Hi!
Any ideas how to represent nodes?
Or rather, a way of indicating which set of nodes that a compute object is deployed to.

In our current setup we have two sets of worker nodes, and on one of them we also have an internal router deployed. So not only can the pod run on one set or the other, but the service can also be exposed in two different places - and even both at the same time.

@ammerzon
Copy link

ammerzon commented May 14, 2020

In his article he states the following:

There should never be a need to call out individual nodes of a Kubernetes cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants