Skip to content

OCPBUGS-97951: add startup probes and DNS egress to network policies - #761

Open
mkowalski wants to merge 1 commit into
openshift:release-4.22from
mkowalski:fix/startup-probes-4.22
Open

OCPBUGS-97951: add startup probes and DNS egress to network policies#761
mkowalski wants to merge 1 commit into
openshift:release-4.22from
mkowalski:fix/startup-probes-4.22

Conversation

@mkowalski

Copy link
Copy Markdown

Backport of openshift/kubernetes-nmstate#759 to release-4.22.

See OCPBUGS-97951 / OCPBUGS-94072 for full description and analysis.


🤖 This PR was generated by AI on behalf of @mkowalski, who has reviewed it.

Add startupProbe to nmstate-webhook and nmstate-metrics containers to
allow sufficient time for initialization before liveness/readiness
probes begin checking. Without a startupProbe, pods that take longer
than ~30s to start are killed by the liveness probe and enter
CrashLoopBackOff.

The startupProbe uses TCP socket checks with initialDelaySeconds=10,
periodSeconds=10, and failureThreshold=18, giving containers up to
3 minutes to start. Once the startupProbe succeeds, regular
liveness/readiness probes take over (no initialDelaySeconds needed
since startup was already verified).

Additionally, add DNS egress network policies (UDP/TCP 53) for
webhook, metrics, and operator pods. The existing default-deny
policies block all egress except TCP 6443 (API server), which
prevents DNS resolution. While in-cluster API server access uses the
KUBERNETES_SERVICE_HOST IP directly, various libraries may attempt
DNS lookups during initialization, causing startup delays that
compound with aggressive probe timing.

Signed-off-by: Mateusz Kowalski <mko@redhat.com>
Generated-by: AI
Signed-off-by: Mateusz Kowalski <mko@redhat.com>
@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 35816ee9-b136-4910-901a-0e2db1b00c1c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from cybertron and phoracek July 7, 2026 15:32
@openshift-ci

openshift-ci Bot commented Jul 7, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mkowalski

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 7, 2026
@mkowalski mkowalski changed the title Bug 97951: add startup probes and DNS egress to network policies OCPBUGS-97951: add startup probes and DNS egress to network policies Jul 7, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 7, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@mkowalski: This pull request references Jira Issue OCPBUGS-97951, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-97950 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is New instead
  • expected dependent Jira Issue OCPBUGS-97950 to target a version in 5.0.0, but it targets "4.21.z" instead

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

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Backport of openshift/kubernetes-nmstate#759 to release-4.22.

See OCPBUGS-97951 / OCPBUGS-94072 for full description and analysis.


🤖 This PR was generated by AI on behalf of @mkowalski, who has reviewed it.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 7, 2026
@mkowalski

Copy link
Copy Markdown
Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@mkowalski: This pull request references Jira Issue OCPBUGS-97951, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-97952 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is New instead

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

Details

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@mkowalski

Copy link
Copy Markdown
Author

/retest

@openshift-ci

openshift-ci Bot commented Jul 9, 2026

Copy link
Copy Markdown

@mkowalski: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security 9fe736e link true /test security

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants