aws / aws/aws-application-networking-k8s

[e2e test] Need to test mutation of replica of Pod(s)

Open
#232 0 comments 0 reactions 0 assignees View on GitHub
test case
Dominant language
Go
Stars
278
Forks
85
PR merge metrics
No merged PRs in 30d

Description

Today, all the tests are covering static replica of Pods, e.g. 1 replica. We need to enhance these tests to cover following

* increase the replica for a deployment of K8S service from 1 to 3 and verify all 3 targets are becoming healthy , and traffic are passing
* decrease the replica for a deployment of K8S service from 3 to 2, and verify 1 target are being drained
* increase the replica for a deployment of K8S service export from 1 to 3 and verify all 3 targets are becoming healthy , and traffic are passing
* decrease the replica for a deployment of K8S service export from 3 to 2, and verify 1 target are being drained

Contributor guide

Open the contributing guide

Research direction

Locate the existing end-to-end tests that cover static Pod replica counts and start by understanding how Kubernetes service and service export deployments, targets, health, traffic, and draining are verified. Extend coverage for scaling 1→3 and 3→2 in both cases; done means all new targets become healthy and pass traffic, while removed targets are drained.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go, kubernetes
Domain
infrastructure, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.