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

[release-4.6] Bug 1928773: Set CoreDNS readiness probe period and timeout each to 3 seconds #236

Conversation

Miciah
Copy link
Contributor

@Miciah Miciah commented Feb 15, 2021

This is a manual cherry-pick of #234. This cherry-pick also includes parts of #205 that #213 did not revert and that #234 builds upon.

Set CoreDNS readiness probe period and timeout to 3

Change the readiness probe for CoreDNS from using a 10-second period and timeout to using a 3-second period and timeout in order to reduce the time to remove the endpoint if CoreDNS becomes unresponsive.

  • assets/dns/daemonset.yaml: Set readiness probe period and timeout to 3 seconds.
  • pkg/manifests/bindata.go: Regenerate.

Reconcile all readiness probe parameters

Check all parameters of the CoreDNS daemonset's readiness probe, and update the daemonset if any of the probe's parameters differ from the expected values.

Before this commit, the DNS controller ignored all changes to the readiness probe's parameters.

  • pkg/operator/controller/controller_dns_daemonset.go (daemonsetConfigChanged): Check if any of the readiness probe's parameters changed and update them if they did.
  • pkg/operator/controller/controller_dns_daemonset_test.go (TestDaemonsetConfigChanged): Add test case to verify that daemonsetConfigChanged detects changes to the readiness probe's path or periodSeconds parameters.

Change the readiness probe for CoreDNS from using a 10-second period and
timeout to using a 3-second period and timeout in order to reduce the time
to remove the endpoint if CoreDNS becomes unresponsive.

This commit is related to bug 1928773.

https://bugzilla.redhat.com/show_bug.cgi?id=1928773

* assets/dns/daemonset.yaml: Set readiness probe period and timeout to 3
seconds.
* pkg/manifests/bindata.go: Regenerate.
Check all parameters of the CoreDNS daemonset's readiness probe, and update
the daemonset if any of the probe's parameters differ from the expected
values.

Before this commit, the DNS controller ignored all changes to the readiness
probe's parameters.

* pkg/operator/controller/controller_dns_daemonset.go
(daemonsetConfigChanged): Check if any of the readiness probe's parameters
changed and update them if they did.
* pkg/operator/controller/controller_dns_daemonset_test.go
(TestDaemonsetConfigChanged): Add test case to verify that
daemonsetConfigChanged detects changes to the readiness probe's
path or periodSeconds parameters.
@openshift-ci-robot
Copy link
Contributor

@Miciah: This pull request references Bugzilla bug 1928773, which is invalid:

  • expected dependent Bugzilla bug 1928304 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is POST instead
  • expected dependent Bugzilla bug 1928304 to target a release in 4.7.0, but it targets "4.7.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.6] Bug 1928773: Set CoreDNS readiness probe period and timeout each to 3 seconds

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.

@openshift-ci-robot openshift-ci-robot added bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Feb 15, 2021
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 15, 2021
@lihongan
Copy link
Contributor

lihongan commented Mar 4, 2021

/bugzilla refresh

@openshift-ci-robot
Copy link
Contributor

@lihongan: This pull request references Bugzilla bug 1928773, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.z) matches configured target release for branch (4.6.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1928304 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1928304 targets the "4.7.z" release, which is one of the valid target releases: 4.7.0, 4.7.z
  • bug has dependents

In response to this:

/bugzilla refresh

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.

@openshift-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Mar 4, 2021
@knobunc
Copy link

knobunc commented Mar 4, 2021

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2021
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: knobunc, 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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@derekwaynecarr
Copy link
Member

(Patch-Manager) approved.

@derekwaynecarr derekwaynecarr added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 4, 2021
@openshift-merge-robot openshift-merge-robot merged commit 3017301 into openshift:release-4.6 Mar 4, 2021
@openshift-ci-robot
Copy link
Contributor

@Miciah: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 1928773 has not been moved to the MODIFIED state.

In response to this:

[release-4.6] Bug 1928773: Set CoreDNS readiness probe period and timeout each to 3 seconds

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants