kubernetes-csi / kubernetes-csi/csi-driver-host-path

define resource limits to avoid eviction

Open
#47 14 comments 0 reactions 0 assignees View on GitHub
help wanted lifecycle/frozen
Dominant language
Go
Stars
388
Forks
233
Avg merge
2d 6h
Merged PRs (30d)
2

Description

Pods without resource specification are the first that get evicted when a node runs out of resources. All of our deployments should specify required resources.

Perhaps there's also something else that can be done to prevent removal of a CSI driver instance from a node?

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named. Start by locating the deployment manifests and any configuration for the CSI driver, then determine how resource requests and limits are specified. Done means all deployments declare required resources and the proposed approach to preventing CSI driver eviction is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.