Skip to content

Commit 71dd2ad

Browse files
committed
Document custom ports feature in the book
1 parent 62092ce commit 71dd2ad

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

docs/book/src/clusteropenstack/configuration.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -206,6 +206,30 @@ spec:
206206
name: <subnet-name>
207207
```
208208
209+
## Ports
210+
211+
A server can also be connected to networks by describing what ports to create. Describing a server's connection with `ports` allows for finer and more advanced configuration. For example, you can specify per-port security groups, fixed IPs or VNIC type.
212+
213+
```yaml
214+
apiVersion: infrastructure.cluster.x-k8s.io/v1alpha4
215+
kind: OpenStackMachine
216+
metadata:
217+
name: <cluster-name>-controlplane
218+
namespace: <cluster-name>
219+
spec:
220+
ports:
221+
- networkId: <your-network-id>
222+
description: <your-custom-port-description>
223+
vnicType: normal
224+
fixedIPs:
225+
- subnetId: <your-subnet-id>
226+
ipAddress: <your-fixed-ip>
227+
securityGroups:
228+
- <your-security-group-id>
229+
```
230+
231+
Any such ports are created in addition to ports used for connections to networks or subnets.
232+
209233
## Tagging
210234

211235
If your cluster supports tagging servers, you have the ability to tag all resources created by the cluster in the `cluster.yaml` file. Here is an example how to configure tagging:

0 commit comments

Comments
 (0)