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

Support assigning Pods to Nodes using nodeSelector #148

Merged
merged 5 commits into from Jun 22, 2020

Conversation

dcasavant
Copy link
Member

In some Kubernetes environments, you may have configured certain Nodes in your Kubernetes cluster with different attributes, such as persistent storage. You may want to use the nodeSelector pattern to assign Pods of a tier to run on particular node(s).

This change adds the ability to use nodeSelector as a block under a particular tier.

Example use cases:

  1. Assign Stream tier Pods to Kubernetes Nodes with durable disks attached.
  2. Assign all Pega Pods to Kubernetes Nodes with extra memory.

To specify a nodeSelector, add the option under a particular tier, such as in the example below:

tier:
- name: "stream"
  nodeType: "Stream"

  nodeSelector:
    disktype: ssd

@dcasavant dcasavant added the enhancement New feature or request label Jun 1, 2020
@dcasavant dcasavant self-assigned this Jun 1, 2020
@dcasavant dcasavant marked this pull request as ready for review June 18, 2020 13:49
@dcasavant dcasavant requested review from taz-mon and a team as code owners June 18, 2020 13:49
Copy link
Contributor

@taz-mon taz-mon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi Dave - I'll approve so you can move this forward, but I'd suggest changes here. It'd be useful to use a little more direct language here and include the context of the node selector label, since the linked article uses the label terminology? This is what I'm thinking:
Pega supports configuring certain nodes in your Kubernetes cluster with a label to identify its attributes, such as persistent storage. For such configurations, use the Pega Helm chart nodeSelector property to assign pods in a tier to run on particular nodes with a specified label. For more information about assigning Pods to Nodes including how to configure your Nodes with labels, see the Kubernetes documentation on nodeSelector.

@dcasavant dcasavant merged commit fcec1c6 into pegasystems:master Jun 22, 2020
@dcasavant dcasavant deleted the nodeSelector branch June 25, 2020 15:01
MadhuriArugula pushed a commit to MadhuriArugula/pega-helm-charts that referenced this pull request Sep 14, 2020
* Add nodeSelector option
* Add nodeSelector documentation
MadhuriArugula pushed a commit to MadhuriArugula/pega-helm-charts that referenced this pull request Dec 7, 2020
* Add nodeSelector option
* Add nodeSelector documentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants