internet/awx-operator
3
0
Fork 0
mirror of https://github.com/ansible/awx-operator.git synced 2026-03-26 21:33:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add tower_ingress_type NodePort

Browse Source
This commit is contained in:
stal
2021-04-14 20:15:15 +01:00
parent 0f90847c07
commit 1b87616a11
2 changed files with 19 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@@ -119,7 +119,7 @@ stringData:
By default, the AWX operator is not opinionated and won't force a specific ingress type on you. So, if `tower_ingress_type` is not specified as part of the Custom Resource specification, it will default to `none` and nothing ingress-wise will be created. By default, the AWX operator is not opinionated and won't force a specific ingress type on you. So, if `tower_ingress_type` is not specified as part of the Custom Resource specification, it will default to `none` and nothing ingress-wise will be created.
The AWX operator provides support for three kinds of `Ingress` to access AWX: `Ingress`, `Route` and `LoadBalancer`, To toggle between these options, you can add the following to your AWX CR: The AWX operator provides support for four kinds of `Ingress` to access AWX: `Ingress`, `Route`, `LoadBalancer` and `NodePort`, To toggle between these options, you can add the following to your AWX CR:
* Route * Route
@@ -150,13 +150,22 @@ spec:
tower_loadbalancer_protocol: http tower_loadbalancer_protocol: http
``` ```
* NodePort
```yaml
---
spec:
...
tower_ingress_type: NodePort
```
The AWX `Service` that gets created will have a `type` set based on the `tower_ingress_type` being used: The AWX `Service` that gets created will have a `type` set based on the `tower_ingress_type` being used:
If `tower_ingress_type: LoadBalancer` is used the `Service` will be set as `type: LoadBalancer`. | Ingress Type `tower_ingress_type` | Service Type |
| ------------------------------------- | -------------- |
If `tower_ingress_type: Ingress` is used the `Service` will be set as `type: ClusterIP`. | `LoadBalancer` | `LoadBalancer` |
| `NodePort` | `NodePort` |
If `tower_ingress_type: Route`, or no `tower_ingress_type` is specified in the Custom Resource Definition, the `Service` will be set as `type: NodePort`. | `Ingress` or `Route` or not specified | `ClusterIP` |
#### TLS Termination #### TLS Termination

8
roles/installer/templates/tower_service.yaml.j2
View File

@@ -44,8 +44,8 @@ spec:
app.kubernetes.io/component: awx app.kubernetes.io/component: awx
{% if tower_ingress_type | lower == "loadbalancer" %} {% if tower_ingress_type | lower == "loadbalancer" %}
type: LoadBalancer type: LoadBalancer
{% elif tower_ingress_type | lower == "ingress" %} {% elif tower_ingress_type | lower == "nodeport" %}
type: ClusterIP
{% elif tower_ingress_type != "none" %}
type: NodePort type: NodePort
{% endif %} {% elif %}
type: ClusterIP
{% endif %}