Skip to content

Outside access over hostport documented #195

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Aug 13, 2018
Merged

Outside access over hostport documented #195

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e373fc2
Outside access over hostport documented
Hermain Aug 10, 2018
8df66f2
outside access doc updated
Hermain Aug 10, 2018
fe3cff7
Outside access cosmetic change to docs
Hermain Aug 10, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 20 additions & 1 deletion outside-services/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,23 @@

Currently supported for brokers, not zookeeper.

This folder only creates sample services for NodePort access, i.e. inside any firewalls that protect your cluster. Can be switched to LoadBalancer, but then the init script for brokers must be updated to retrieve external names. See discussions around https://github.com/Yolean/kubernetes-kafka/pull/78 for examples.

### Outside access with one nodeport per broker
outside-0.yml - outside2.yml creates sample services for NodePort access, i.e. inside any firewalls that protect your cluster. Can be switched to LoadBalancer, but then the init script for brokers must be updated to retrieve external names. See discussions around https://github.com/Yolean/kubernetes-kafka/pull/78 for examples.

When using this approach a service must be created for each kafka broker.

### Outside access with hostport
An alternative is to use the hostport for the outside access. When using this only one kafka broker can run on each host, which is a good idea anyway.

In order to switch to hostport the kafka advertise address needs to be switched to the ExternalIP or ExternalDNS name of the node running the broker.
in [kafka/10broker-config.yml](../kafka/10broker-config.yml) switch to
* `OUTSIDE_HOST=$(kubectl get node "$NODE_NAME" -o jsonpath='{.status.addresses[?(@.type=="ExternalIP")].address}')`
* `OUTSIDE_PORT=${OutsidePort}`

and in [kafka/50kafka.yml ](../kafka/50kafka.yml) add the hostport:
```
- name: outside
containerPort: 9094
hostPort: 9094
```