Repository navigation
examine nil pointer before applying backend protocol configurations - #678
Conversation
There was a problem hiding this comment.
what do you mean by exiting?
There was a problem hiding this comment.
"..caused by an application..."
There was a problem hiding this comment.
"...revert the change on the application..."
There was a problem hiding this comment.
| "Please revert the change on application protocol to avoid this error message." | |
| "Please revert the change on the application's protocol to avoid this error message." |
I don't have a lot of insight into how the ingress-gce works internally, but I think a TODO on handling this type of change would be helpful. I think progressing from HTTP-1.1 to HTTP-2 (soon HTTP-3) or introducing changes on the protocol to adopt a service mesh will be a common occurrence.
There was a problem hiding this comment.
yeah. Agreed. In the long run we want to support this. But currently, due to GCE api changes, it was broken. So we need to put this short term fix in place so that it can be cherry picked.
There was a problem hiding this comment.
Can we add the TODO just so we remember to do it?
There was a problem hiding this comment.
| "This is usually caused by application protocol changed. " + | |
| "This is usually caused by a change of the application's protocol." + |
There was a problem hiding this comment.
| "Please revert the change on application protocol to avoid this error message." | |
| "Please revert the change on the application's protocol to avoid this error message." |
I don't have a lot of insight into how the ingress-gce works internally, but I think a TODO on handling this type of change would be helpful. I think progressing from HTTP-1.1 to HTTP-2 (soon HTTP-3) or introducing changes on the protocol to adopt a service mesh will be a common occurrence.
|
fixed. |
|
Assigning for |
|
This LGTM, but will defer to @rramkumar1 to make the final call. |
There was a problem hiding this comment.
can we give the name of the actual field involved, this error is a bit vague sounding. are we talking about the GCP object, the protocol used by the app itself, etc
There was a problem hiding this comment.
HealthCheck object contains HTTPHealthCheck configurations. It has bunch of fields.
In this case, the controller thinks that HTTP2HealthCheck configuration is nil because it was not vendored.
There was a problem hiding this comment.
can we not return immediately (same in all case above)
|
Ready for next round |
There was a problem hiding this comment.
"the %v health check configuration..."
There was a problem hiding this comment.
Can we add the TODO just so we remember to do it?
|
Done |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: freehan, rramkumar1 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Cherrypick #678 into release-1.5
Mitigates #675