-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 for #5210 #5790
Fix for #5210 #5790
Conversation
Remove these from the unrecoverable errors list. Containers are ephemeral in k8s, so errors in them may be recoverable at a system level. E.g. when they are waiting for another resource to stablelize.
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
@googlebot I signed it! |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
Too many hoops to associate my email address. I put these whopping 2 lines of code in the public domain. |
Codecov Report
@@ Coverage Diff @@
## master #5790 +/- ##
========================================
Coverage 70.78% 70.79%
========================================
Files 432 436 +4
Lines 16242 16356 +114
========================================
+ Hits 11497 11579 +82
- Misses 3901 3923 +22
- Partials 844 854 +10
Continue to review full report at Codecov.
|
This behavior was added intentionally to quit status check on exited containers especially for GCP cloud run integration. Maybe we could achieve this via statusCheck config.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This behavior was added for Cloud run to make sure status check terminates quickly.
This needs further exploration on
- When to terminate quickly Vs when to wait.
- Shd it be user configurable?
Sorry @casret, but we do need you to sign the CLA. Let us know if you don't plan to work on this anymore. |
I would love to, and I did, but it won't take my email address. Not sure
where to go from here.
…On Tue, May 11, 2021 at 7:25 AM Tejal Desai ***@***.***> wrote:
Too many hoops to associate my email address. I put these whopping 2 lines
of code in the public domain.
Sorry @casret <https://github.com/casret>, but we do need you to sign the
CLA. Let us know if you don't plan to work on this anymore.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5790 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACLBFO6YUAICPZVOVXHNDTNBTPXANCNFSM44FQWPKQ>
.
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
Just wanted to make sure, you are signing the CLA for email address associated with your github profile. Please let me know if that works. |
@googlebot I fixed it |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
@tejal29 Thanks for guiding me through the process. Wasn't very clear from the instructions where I was to add the alternate email. I thought It was to my google account. Now that the red tape is cleared, I'll try a version with the config. |
@casret Please see your development guide section to make config changes in DEVELOPMENT.md |
@casret ping! |
Fixes: #5210
Description
Remove these from the unrecoverable errors list. Containers are
ephemeral in k8s, so errors in them may be recoverable at a system
level. E.g. when they are waiting for another resource to stablelize.
User facing changes (remove if N/A)
The deploy status check will wait for the deployment to stabilize even if the container errors out. This restores the 1.12 behaviour.