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

🐛 Deploy only required CAPIProviders in e2e #1035

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

Danil-Grigorev
Copy link
Contributor

@Danil-Grigorev Danil-Grigorev commented Jan 22, 2025

What this PR does / why we need it:

EKS cluster suffers from limited number of private IPs, which are exausted by test suites running in parallel. It affects GitRepo processing, where a pod created to update content of the repo in order to apply manifests to the cluster. Since the pod is not able to be scheduled, e2e tests are failing.

Events message, displaying the issue:

 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod. 

Successful run, affected only by #990: https://github.com/rancher/turtles/actions/runs/12924089494

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1021

Special notes for your reviewer:

Checklist:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@Danil-Grigorev Danil-Grigorev added the kind/bug Something isn't working label Jan 22, 2025
@Danil-Grigorev Danil-Grigorev requested a review from a team as a code owner January 22, 2025 16:07
@Danil-Grigorev Danil-Grigorev force-pushed the cleanup-pod-pool-eks branch 4 times, most recently from 71056b3 to fbde80d Compare January 22, 2025 18:11
@Danil-Grigorev Danil-Grigorev changed the title 🐛 Remove completed pods in e2e 🐛 Remove used CAPIProviders in e2e test Jan 22, 2025
@Danil-Grigorev Danil-Grigorev changed the title 🐛 Remove used CAPIProviders in e2e test 🐛 Remove used CAPIProviders in e2e Jan 22, 2025
@Danil-Grigorev Danil-Grigorev force-pushed the cleanup-pod-pool-eks branch 3 times, most recently from 1bc4ac2 to ff5d6c3 Compare January 23, 2025 07:20
@Danil-Grigorev Danil-Grigorev changed the title 🐛 Remove used CAPIProviders in e2e 🐛 Deploy only required CAPIProviders in e2e Jan 23, 2025
@Danil-Grigorev Danil-Grigorev requested a review from a team January 23, 2025 08:30
anmazzotti
anmazzotti previously approved these changes Jan 23, 2025
EKS cluster suffers from limited number of private IPs, which are
exausted by test suites running in parallel. It affects GitRepo
processing, where a pod created to update content of the repo in order
to apply manifests to the cluster. Since the pod is not able to be
scheduled, e2e tests are failing.

Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
Copy link
Contributor

@salasberryfin salasberryfin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so much @Danil-Grigorev

@Danil-Grigorev Danil-Grigorev enabled auto-merge (squash) January 23, 2025 10:03
@Danil-Grigorev Danil-Grigorev merged commit da2656a into rancher:main Jan 23, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Development

Successfully merging this pull request may close these issues.

E2E failures
4 participants