Skip to content

{WIP] disable nodeip-configuration service #1059

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

Open
wants to merge 1 commit into
base: release-4.18
Choose a base branch
from

Conversation

praveenkumar
Copy link
Member

@praveenkumar praveenkumar commented May 13, 2025

Summary by Sourcery

Disable the nodeip-configuration service on VMs and remove its ordering constraint from the gvisor-tap-vsock container unit.

Enhancements:

  • Disable nodeip-configuration service alongside kubelet during disk creation
  • Remove the Before=nodeip-configuration.service directive from the gvisor-tap-vsock container service unit

Copy link

sourcery-ai bot commented May 13, 2025

Reviewer's Guide

Modify the disk creation script to disable the nodeip-configuration service alongside kubelet and remove its ordering directive from the gvisor-tap-vsock container unit.

File-Level Changes

Change Details Files
Disable nodeip-configuration service together with kubelet
  • Extend systemctl disable command to include nodeip-configuration
createdisk.sh
Remove ordering dependency on nodeip-configuration in container unit
  • Delete 'Before=nodeip-configuration.service' line from the gvisor-tap-vsock unit template
createdisk.sh

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@openshift-ci openshift-ci bot requested review from cfergeau and gbraad May 13, 2025 10:11
Copy link

openshift-ci bot commented May 13, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign gbraad for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@praveenkumar praveenkumar changed the title disable nodeip-configuration service {WIP] disable nodeip-configuration service May 13, 2025
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @praveenkumar - I've reviewed your changes and they look great!

Here's what I looked at during the review
  • 🟡 General issues: 1 issue found
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment on lines 52 to +53
# Disable kubelet service
${SSH} core@${VM_IP} -- sudo systemctl disable kubelet
${SSH} core@${VM_IP} -- sudo systemctl disable kubelet nodeip-configuration
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion (bug_risk): Disabled nodeip-configuration but not stopped it

Run systemctl stop nodeip-configuration or use --now to disable and stop it.

Suggested change
# Disable kubelet service
${SSH} core@${VM_IP} -- sudo systemctl disable kubelet
${SSH} core@${VM_IP} -- sudo systemctl disable kubelet nodeip-configuration
# Disable and stop kubelet and nodeip-configuration services
${SSH} core@${VM_IP} -- sudo systemctl disable --now kubelet nodeip-configuration

@cfergeau
Copy link
Contributor

Why? What problem does it solve?

@praveenkumar
Copy link
Member Author

Why? What problem does it solve?

It shouldn't start during boot but start when kubelet service start so that it shouldn't interfere with networking and block tap-vsock to get the IP.

@openshift-merge-robot
Copy link

PR needs rebase.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants