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
Bug 1834989: hashableDeployment: Fix liveness/readiness probes #391
Bug 1834989: hashableDeployment: Fix liveness/readiness probes #391
Conversation
/lgtm |
/retest Please review the full test history for this PR and help us cut down flakes. |
c041c29
to
9c1dc22
Compare
* pkg/operator/controller/ingress/deployment.go (updateRouterDeployment): Add the diff of the previous and updated deployments to the "updated router deployment" log message.
When comparing deployments to determine whether an update is required, treat implicit and explicit default values as equal. Before this commit, the update logic would keep trying to revert the default values that the API set for probe parameters. This commit fixes bug 1834989. https://bugzilla.redhat.com/show_bug.cgi?id=1834989 * pkg/operator/controller/ingress/deployment.go (hashableDeployment): Use the new hashableProbe function so that two deployments have the same hash if the only difference between them is that one does not specify liveness or readiness probe parameters and the other specifies the default parameter values. (hashableProbe): New function. Return a copy of the given probe, copying exactly the fields that should be used for computing a deployment's hash, and zeroing out any fields where the values are equal to their defaults.
a819178
to
a9e00bb
Compare
@Miciah: An error was encountered updating to the POST state for bug 1834989 on the Bugzilla server at https://bugzilla.redhat.com:
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@Miciah: This pull request references Bugzilla bug 1834989, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
/test e2e-aws-operator |
Same as #391 (comment) /test e2e-aws-operator |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danehans, ironcladlou, Miciah The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
27 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@Miciah: All pull requests linked via external trackers have merged: openshift/cluster-ingress-operator#391. Bugzilla bug 1834989 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
updateRouterDeployment
: Add diff to log messagepkg/operator/controller/ingress/deployment.go
(updateRouterDeployment
): Add the diff of the previous and updated deployments to the "updated router deployment" log message.hashableDeployment
: Fix liveness/readiness probesWhen comparing deployments to determine whether an update is required, treat implicit and explicit default values as equal.
Before this commit, the update logic would keep trying to revert the default values that the API set for probe parameters.
pkg/operator/controller/ingress/deployment.go
(hashableDeployment
): Use the newhashableProbe
function so that two deployments have the same hash if the only difference between them is that one does not specify liveness or readiness probe parameters and the other specifies the default parameter values.(
hashableProbe
): New function. Return a copy of the given probe, copying exactly the fields that should be used for computing a deployment's hash, and zeroing out any fields where the values are equal to their defaults.