Skip to content

Conversation

jdenquin
Copy link
Contributor

  • Improve sidekiq liveness socket to listen to 0.0.0.0 instead of localhost

@jdenquin jdenquin requested a review from Copilot June 16, 2025 09:07
@jdenquin jdenquin self-assigned this Jun 16, 2025
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the Sidekiq liveness socket configuration to bind to 0.0.0.0 instead of localhost, thereby allowing the service to listen on all network interfaces.

  • Changed the TCPServer binding from "localhost" to "0.0.0.0" to improve liveness monitoring in environments where external access is required.
  • Modified the configuration in config/initializers/sidekiq.rb.
Comments suppressed due to low confidence (1)

config/initializers/sidekiq.rb:35

  • Binding the liveness server to 0.0.0.0 may expose it publicly. Please ensure that proper network restrictions (e.g., firewall rules) or access controls are in place to prevent unauthorized access.
server = TCPServer.new("0.0.0.0", LIVENESS_PORT)

@groyoh
Copy link
Contributor

groyoh commented Jun 16, 2025

Side note: @jdenquin we should probably make the liveliness port configurable at some point.

@jdenquin jdenquin merged commit a35972c into main Jun 16, 2025
14 checks passed
@jdenquin jdenquin deleted the sidekiq-liveness-address branch June 16, 2025 13:10
diegocharles pushed a commit that referenced this pull request Jul 11, 2025
- Improve sidekiq liveness socket to listen to `0.0.0.0` instead of
localhost
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants