Write the stress test for gRPC, http, and tcp probes

@aojea

Write a new e2e test that will be marked as [Serial] and will be covering this bug fix: #89898

The test will serve as a replacement for the skipped unit test: #115329

The logic of the test will be as following:

Create MANY containers (see the unit test logic)
Each container has a liveness probe with 1s interval
After some time validate that neither of containers has restartCount > 0

/cc @aojea
/sig node
/kind cleanup
/priority important-soon
/area tests
/help-wanted
/good-first-issue

This is part of KEP: kubernetes/enhancements#2727 GA requirements, but also need the same tests for http and tcp.

@SergeyKanzhelev

@SergeyKanzhelev:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

Why are we solving this issue?
To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
Does this issue have zero to low barrier of entry?
How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

Details

In response to this:

Write a new e2e test that will be marked as [Serial] and will be covering this bug fix: #89898

The test will serve as a replacement for the skipped unit test: #115329

The logic of the test will be as following:

Create MANY containers (see the unit test logic)

Each container has a liveness probe with 1s interval

After some time validate that neither of containers has restartCount > 0

/cc @aojea
/sig node
/kind cleanup
/priority important-soon
/area tests
/help-wanted
/good-first-issue

This is part of KEP: kubernetes/enhancements#2727 GA requirements, but also need the same tests for http and tcp.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@SergeyKanzhelev

@SergeyKanzhelev: The label(s) area/tests cannot be applied, because the repository doesn't have them.

Details

In response to this:

Write a new e2e test that will be marked as [Serial] and will be covering this bug fix: #89898

The test will serve as a replacement for the skipped unit test: #115329

The logic of the test will be as following:

Create MANY containers (see the unit test logic)

Each container has a liveness probe with 1s interval

After some time validate that neither of containers has restartCount > 0

/cc @aojea
/sig node
/kind cleanup
/priority important-soon
/area tests
/help-wanted
/good-first-issue

This is part of KEP: kubernetes/enhancements#2727 GA requirements, but also need the same tests for http and tcp.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/assign

+1

/assign

@antonio-mazzini

@antonio-mazzini: GitHub didn't allow me to assign the following users: antonio-mazzini.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Can't we work on this??

Can I work on this?

Hi, I’m a new contributor interested in working on this. I have QA/testing and Docker experience and would like to start by understanding the existing probe tests. Is this issue still available?

Hi, I’m interested in working on this. I see there have been previous PR attempts and multiple assignees. Is this still available for a new contributor, or is there a specific remaining piece I can help with?

test/e2e/node: add probe stress test for HTTP, TCP, and gRPC liveness…

/assign

@iho

@iho: GitHub didn't allow me to assign the following users: iho.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

/assign

@anusha1234-dot

@anusha1234-dot: GitHub didn't allow me to assign the following users: anusha1234-dot.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@SergeyKanzhelev

@SergeyKanzhelev should this issue be closed based on the merge of #135689

Hi, I am a new contributor and would like to take this on. I will start looking into the pkg/kubelet/prober/ directory to outline the stress tests for the gRPC, HTTP, and TCP probes.

/assign

@reetig

@reetig: GitHub didn't allow me to assign the following users: reetig.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Navigation Menu

Repository navigation

Write the stress test for gRPC, http, and tcp probes #115782

Guidelines

42 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Write the stress test for gRPC, http, and tcp probes #115782

Description

Activity

k8s-ci-robot commented on Feb 15, 2023

Guidelines

k8s-ci-robot commented on Feb 15, 2023

k8s-ci-robot commented on Feb 15, 2023

Octopusjust commented on Feb 15, 2023

aojea commented on Feb 15, 2023

Anis-cpu-13 commented on Feb 15, 2023

42 remaining items

k8s-ci-robot commented on Mar 4, 2026

ayushgharat234 commented on Mar 9, 2026

aayushjoshi2709 commented on May 8, 2026

vaanuthanesh2003 commented on Jun 13, 2026

adityaRaj369 commented on Jun 16, 2026

iho commented on Aug 2, 2026

kubernetes-prow commented on Aug 2, 2026

anusha1234-dot commented on Aug 12, 2026

kubernetes-prow commented on Aug 12, 2026

mikebrow commented on Aug 12, 2026

reetig commented on Sep 28, 2026

reetig commented on Sep 28, 2026

kubernetes-prow commented on Sep 28, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions