-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add support for k8s pod to node affinity and taint toleration (#917)
Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/917 Reviewed-by: Thomas E Lackey <telackey@noreply.git.vdb.to> Co-authored-by: David Boreham <david@bozemanpass.com> Co-committed-by: David Boreham <david@bozemanpass.com>
- Loading branch information
Showing
7 changed files
with
369 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
name: K8s Deployment Control Test | ||
|
||
on: | ||
pull_request: | ||
branches: '*' | ||
push: | ||
branches: '*' | ||
paths: | ||
- '!**' | ||
- '.gitea/workflows/triggers/test-k8s-deployment-control' | ||
- '.gitea/workflows/test-k8s-deployment-control.yml' | ||
- 'tests/k8s-deployment-control/run-test.sh' | ||
schedule: # Note: coordinate with other tests to not overload runners at the same time of day | ||
- cron: '3 30 * * *' | ||
|
||
jobs: | ||
test: | ||
name: "Run deployment control suite on kind/k8s" | ||
runs-on: ubuntu-22.04 | ||
steps: | ||
- name: "Clone project repository" | ||
uses: actions/checkout@v3 | ||
# At present the stock setup-python action fails on Linux/aarch64 | ||
# Conditional steps below workaroud this by using deadsnakes for that case only | ||
- name: "Install Python for ARM on Linux" | ||
if: ${{ runner.arch == 'arm64' && runner.os == 'Linux' }} | ||
uses: deadsnakes/action@v3.0.1 | ||
with: | ||
python-version: '3.8' | ||
- name: "Install Python cases other than ARM on Linux" | ||
if: ${{ ! (runner.arch == 'arm64' && runner.os == 'Linux') }} | ||
uses: actions/setup-python@v4 | ||
with: | ||
python-version: '3.8' | ||
- name: "Print Python version" | ||
run: python3 --version | ||
- name: "Install shiv" | ||
run: pip install shiv | ||
- name: "Generate build version file" | ||
run: ./scripts/create_build_tag_file.sh | ||
- name: "Build local shiv package" | ||
run: ./scripts/build_shiv_package.sh | ||
- name: "Check cgroups version" | ||
run: mount | grep cgroup | ||
- name: "Install kind" | ||
run: ./tests/scripts/install-kind.sh | ||
- name: "Install Kubectl" | ||
run: ./tests/scripts/install-kubectl.sh | ||
- name: "Run k8s deployment control test" | ||
run: | | ||
source /opt/bash-utils/cgroup-helper.sh | ||
join_cgroup | ||
./tests/k8s-deployment-control/run-test.sh | ||
- name: Notify Vulcanize Slack on CI failure | ||
if: ${{ always() && github.ref_name == 'main' }} | ||
uses: ravsamhq/notify-slack-action@v2 | ||
with: | ||
status: ${{ job.status }} | ||
notify_when: 'failure' | ||
env: | ||
SLACK_WEBHOOK_URL: ${{ secrets.VULCANIZE_SLACK_CI_ALERTS }} | ||
- name: Notify DeepStack Slack on CI failure | ||
if: ${{ always() && github.ref_name == 'main' }} | ||
uses: ravsamhq/notify-slack-action@v2 | ||
with: | ||
status: ${{ job.status }} | ||
notify_when: 'failure' | ||
env: | ||
SLACK_WEBHOOK_URL: ${{ secrets.DEEPSTACK_SLACK_CI_ALERTS }} |
Empty file.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# K8S Deployment Enhancements | ||
## Controlling pod placement | ||
The placement of pods created as part of a stack deployment can be controlled to either avoid certain nodes, or require certain nodes. | ||
### Pod/Node Affinity | ||
Node affinity rules applied to pods target node labels. The effect is that a pod can only be placed on a node having the specified label value. Note that other pods that do not have any node affinity rules can also be placed on those same nodes. Thus node affinity for a pod controls where that pod can be placed, but does not control where other pods are placed. | ||
|
||
Node affinity for stack pods is specified in the deployment's `spec.yml` file as follows: | ||
``` | ||
node-affinities: | ||
- label: nodetype | ||
value: typeb | ||
``` | ||
This example denotes that the stack's pods should only be placed on nodes that have the label `nodetype` with value `typeb`. | ||
### Node Taint Toleration | ||
K8s nodes can be given one or more "taints". These are special fields (distinct from labels) with a name (key) and optional value. | ||
When placing pods, the k8s scheduler will only assign a pod to a tainted node if the pod posesses a corresponding "toleration". | ||
This is metadata associated with the pod that specifies that the pod "tolerates" a given taint. | ||
Therefore taint toleration provides a mechanism by which only certain pods can be placed on specific nodes, and provides a complementary mechanism to node affinity. | ||
|
||
Taint toleration for stack pods is specified in the deployment's `spec.yml` file as follows: | ||
``` | ||
node-tolerations: | ||
- key: nodetype | ||
value: typeb | ||
``` | ||
This example denotes that the stack's pods will tolerate a taint: `nodetype=typeb` | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.