Comment 3 for bug 1943786
Revision history for this message
| Connor Chamberlain (lcvcode) wrote Re: Connections fail when using a vip with a port in Charmed Operator Framework | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
It looks like Kubernetes may be setting service target ports to 65535 by default. This breaks networking when two Charmed Operator charms attempt to communicate using cluster IPs.
In my case, I'm deploying:
* Pulsar https:/
* Bookie https:/
After deploying Pulsar, I can see:
```
kubectl describe service -n pulsar pulsar
Name: pulsar
Namespace: pulsar
...
IP: 10.152.183.12
IPs: 10.152.183.12
Port: placeholder 65535/TCP
TargetPort: 65535/TCP
Endpoints: 10.1.195.
...
```
TargetPort should be configurable from within a charm, otherwise other applications cannot communicate using cluster IP.
A workaround for this is to use each unit's IP address (ops.model.
[0] - https:/
[1] - https:/