my-rook-config

Files

T

Travis Nielsen fb86955f01 core: examples set default priority class names

By default, we should set the priority class to one of the built-in
priority class names to ensure that pods critical to the storage
will be able to remain running when resources are low. Otherwise,
critical rook pods could be evicted and affect many other pods
that rely on the storage to continue functioning. The options have
been available in the CRs, but until now we have just not set the
defaults in the examples. Critical rook components are now set to
the priority class system-node-critical if they are generally pinned
to a node, and system-cluster-critical if they are critical to the storage.
Some pods such as the operator and crash collector do not have a
default priority class set in the examples since they don't affect
the data path.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

2022-04-19 16:09:34 -06:00

env.go

ci: wait longer for pod label to be deleted

2021-09-28 15:24:39 +02:00

exec_utils.go

ci: enable gosec linter in golangci-lint

2020-10-19 11:50:06 +05:30

helm_helper.go

test: implement helm upgrade integration test

2022-01-12 07:19:42 -07:00

k8s_helper.go

core: examples set default priority class names