Ability to customize the port Scylla's probes listen on from 8080

[ChristopherCharlesTodd]

Feature Request Allow individuals to change the port Scylla's probes listen on. Currently, you are forced to use 8080, and adapt your existing app's configurations around Scylla. It should be the other way around.

What is use case behind this feature: While implementing Scylla in our QA envs, we received the following error: [operator/sidecar.go:422] ListenAndServe failed: %vlisten tcp :8080: bind: address already in use

The fix was to move an existing capability from 8080, so it would free the port up for Scylla. For our specific codebase, this was not an issue. However, I can envisage it causing more trouble in other customers bespoke codebases.

[tnozicka]

Just noting down here that this is an issue when using hostNetworking as the probe then listens on the node network.

[rverma-dev]

Is there any fix for this? Even in nightly builds?

[rzetelskik]

@rverma-nsl the port is not customizable at the moment, but it shouldn't cause any issues as long as you're not using hostNetworking

[scylla-operator-bot[bot]]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale