-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
fix: Resource requests on init/wait containers. Fixes #6809 #6879
fix: Resource requests on init/wait containers. Fixes #6809 #6879
Conversation
Signed-off-by: zorulo <artist.swimmer.cheng@gmail.com>
01ccefc
to
ca955e5
Compare
Hi @zorulo |
Codecov Report
@@ Coverage Diff @@
## master #6879 +/- ##
==========================================
- Coverage 48.65% 48.51% -0.14%
==========================================
Files 265 265
Lines 19161 19258 +97
==========================================
+ Hits 9322 9343 +21
- Misses 8790 8863 +73
- Partials 1049 1052 +3
Continue to review full report at Codecov.
|
…rgoproj#6879) Signed-off-by: zorulo <artist.swimmer.cheng@gmail.com> Signed-off-by: kriti-sc <kathuriakriti1@gmail.com>
Signed-off-by: zorulo
Fixes #6809. I understand we probably want tests on this (?) but I'm unfamiliar with how to do so (sorry for newbieness).
I wasn't quite clear on how to run this locally; followed the running locally guide but ran into the issue mentioned here, amongst others, also trying to use
minikube
,v1.22.2
of both minikube/kubectl.As such, submitting the test workflow as noted in #6809 did not run because of the issue, but I was able to look at the pod and check that the requests were being applied without needing to specify limits.