Default to a headless service for ser2sock instead of a clusterIP load balancer
Benefits
Since these generally talk to individual instances of physical hardware, it is unlikely that a user intends load balancing of multiple instances to multiple devices. Using a headless service (clusterIP: None) removes the k8s load balancer and allows clients to talk directly to the ser2sock pod via the service name.
Possible drawbacks
Users who rely on the clusterIP load balancer will need to add service.main.clusterIP: (no value) to return to the old behavior.
Applicable issues
fixes #
Additional information
Checklist
[X] Title of the PR starts with chart name (e.g. [home-assistant])
[x] Chart version bumped in Chart.yaml according to semver.
[x] Chart artifacthub.io/changes changelog annotation has been updated in Chart.yaml. See Artifact Hub documentation for more info.
[ ] Variables have been documented in the values.yaml file.
Description of the change
Default to a headless service for ser2sock instead of a clusterIP load balancer
Benefits
Since these generally talk to individual instances of physical hardware, it is unlikely that a user intends load balancing of multiple instances to multiple devices. Using a headless service (
clusterIP: None) removes the k8s load balancer and allows clients to talk directly to the ser2sock pod via the service name.Possible drawbacks
Users who rely on the clusterIP load balancer will need to add
service.main.clusterIP:(no value) to return to the old behavior.Applicable issues
Additional information
Checklist
[home-assistant])Chart.yamlaccording to semver.artifacthub.io/changeschangelog annotation has been updated inChart.yaml. See Artifact Hub documentation for more info.values.yamlfile.