Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(tests): set --max-endpoints-per-slice=2 in K8s Kind clusters used in e2e tests #4091

Merged
merged 1 commit into from
May 26, 2023

Conversation

programmer04
Copy link
Member

What this PR does / why we need it:

Since KIC should work with multiple EndpointSlices, it should be covered with tests too. By default 100 endpoints are allowed per EndpointSlice thus having Deployment with Service that uses multiple EndpointSlices is not feasible in CI tests. This PR configures Kind clusters with --max-endpoints-per-slice 2 to make possible to test KIC against Services with multiple EndpointSlices.

Next PRs will focus to ensure that test cases actually test it.

Which issue this PR fixes:

This is a part of implementing e2e tests that verifies proper handling of EndpointSlices #4026.

Special notes for your reviewer:

This is the part of implementing strategy proposed in this one too big PR #4084.

Labelled with ci/run-e2e to be sure, result has to be examined.

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

  • the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

@programmer04 programmer04 added area/tests ci/run-e2e Trigger e2e test run from PR labels May 26, 2023
@programmer04 programmer04 added this to the KIC v2.10.0 milestone May 26, 2023
@programmer04 programmer04 self-assigned this May 26, 2023
@programmer04 programmer04 requested a review from a team as a code owner May 26, 2023 13:55
@team-k8s-bot
Copy link
Collaborator

E2E (targeted) tests were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/5091614380

@team-k8s-bot team-k8s-bot removed the ci/run-e2e Trigger e2e test run from PR label May 26, 2023
@team-k8s-bot team-k8s-bot temporarily deployed to gcloud May 26, 2023 14:02 — with GitHub Actions Inactive
@team-k8s-bot team-k8s-bot temporarily deployed to gcloud May 26, 2023 14:02 — with GitHub Actions Inactive
@team-k8s-bot team-k8s-bot temporarily deployed to gcloud May 26, 2023 14:02 — with GitHub Actions Inactive
@team-k8s-bot team-k8s-bot temporarily deployed to gcloud May 26, 2023 14:02 — with GitHub Actions Inactive
@team-k8s-bot team-k8s-bot temporarily deployed to gcloud May 26, 2023 14:02 — with GitHub Actions Inactive
@team-k8s-bot team-k8s-bot temporarily deployed to gcloud May 26, 2023 14:02 — with GitHub Actions Inactive
@team-k8s-bot team-k8s-bot temporarily deployed to gcloud May 26, 2023 14:02 — with GitHub Actions Inactive
@programmer04
Copy link
Member Author

For ci/run-e2e on GKE image that does not include #4071 (from yesterday was used, thus GKE results are ignored. For Kind everything is 🟢

@programmer04 programmer04 merged commit 363e15d into main May 26, 2023
192 of 217 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants