-
Notifications
You must be signed in to change notification settings - Fork 162
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
Port 9443 conflict #715
Comments
Hey, the 9443 port is used for the webhook HTTP calls required by Capsule and is a bit of a standard with Operators. This port is exposed by the Capsule pods and not directly as a Service, which is backed by the 443 port. May I ask you what's the error you're reporting, your Kubernetes platform, and the installation method? No problem for making it configurable, we just need first to replicate the error to properly address it. |
we in the cluster cannot use 9443 as that is already been in use by other applications. we want to know the process of how to get this on any other port eg 9447 and get it up and running. |
I'm not sure about OP specific issue, but IMHO this port should be configurable. My use case is private GKE clusters (configured with |
i guess there is confusion around firewall vs other. it is not a firewall issue. let me re-explain the issue
|
Had the time to work on this 🙃 |
We see that capsule-webhook-service is using port 9443 which conflicts with other running services in the cluster. We tried changing the port in the webhook-service.yaml but it is throwing error. We are able to install Capsule only when the port is 9443 so it looks like the port is hard-coded in the Capsule code.
Tested on current and previous version
chart: capsule-0.3.5
app version: 0.2.1
The text was updated successfully, but these errors were encountered: