aws / aws/amazon-eks-pod-identity-webhook

Specify liveness & readiness probes for the pod-identity-webhook

Open
#111 1 comment 5 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
691
Forks
202
Avg merge
4h 38m
Merged PRs (30d)
1

Description

**What would you like to be added**:

This conversation seemed to have sidetracked in [github issue 45](https://github.com/aws/amazon-eks-pod-identity-webhook/issues/45) but typically it's best practices in k8s workloads to define readiness and liveness probes for a deployment. Is it possible to set readiness and liveness probes to monitor this workload?

**Why is this needed**:

Monitor the workload and ensure that the workload is healthy and ready to start processing requests.

Contributor guide

Open the contributing guide

Research direction

Start by locating the Kubernetes Deployment manifest for the pod-identity-webhook and reviewing how the workload currently exposes or reports health. Done means the deployment specifies readiness and liveness probes that monitor the webhook and the resulting configuration can be validated against the workload’s request-processing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.