mirror of
https://github.com/Expand-sys/awx-on-k3s
synced 2025-12-15 21:42:15 +11:00
fix: change the way to patch traefik to creating yaml file
This commit is contained in:
parent
f1536b16d3
commit
ea0ea8cbfa
2 changed files with 24 additions and 4 deletions
|
|
@ -186,10 +186,20 @@ This project is still under active development and there is no support, however,
|
|||
|
||||
If you use Traefik which is K3s' Ingress controller as completely default, the Pod may not be able to get the client's IP address (see [k3s-io/k3s#2997](https://github.com/k3s-io/k3s/discussions/2997) for details). In the current implementation of Pulp, this causes problems with the web UI being unreachable.
|
||||
|
||||
For this reason, you should fix the Traefik configuration. For a single node like doing in this repository, the following command is easy to use.
|
||||
For this reason, you should fix the Traefik configuration. For a single node like doing in this repository, reconfiguring your Traefik by creating YAML file is the easy way.
|
||||
|
||||
```bash
|
||||
kubectl -n kube-system patch deployment traefik --patch '{"spec":{"template":{"spec":{"hostNetwork":true}}}}'
|
||||
sudo tee /var/lib/rancher/k3s/server/manifests/traefik-config.yaml <<EOF
|
||||
---
|
||||
apiVersion: helm.cattle.io/v1
|
||||
kind: HelmChartConfig
|
||||
metadata:
|
||||
name: traefik
|
||||
namespace: kube-system
|
||||
spec:
|
||||
valuesContent: |-
|
||||
hostNetwork: true
|
||||
EOF
|
||||
```
|
||||
|
||||
Then wait until your `traefik` by the following command is `1/1` `READY`.
|
||||
|
|
|
|||
|
|
@ -315,10 +315,20 @@ sudo systemctl restart k3s
|
|||
|
||||
If you use Traefik which is K3s' Ingress controller as completely default, the Pod may not be able to get the client's IP address (see [k3s-io/k3s#2997](https://github.com/k3s-io/k3s/discussions/2997) for details). Therefore, the feature called Provisioning Callback in AWX does not work properly since AWX can't determine actual IP address of the remote host who request callback.
|
||||
|
||||
For this reason, you should fix the Traefik configuration. For a single node like doing in this repository, the following command is easy to use.
|
||||
For this reason, you should fix the Traefik configuration. For a single node like doing in this repository, reconfiguring your Traefik by creating YAML file is the easy way.
|
||||
|
||||
```bash
|
||||
kubectl -n kube-system patch deployment traefik --patch '{"spec":{"template":{"spec":{"hostNetwork":true}}}}'
|
||||
sudo tee /var/lib/rancher/k3s/server/manifests/traefik-config.yaml <<EOF
|
||||
---
|
||||
apiVersion: helm.cattle.io/v1
|
||||
kind: HelmChartConfig
|
||||
metadata:
|
||||
name: traefik
|
||||
namespace: kube-system
|
||||
spec:
|
||||
valuesContent: |-
|
||||
hostNetwork: true
|
||||
EOF
|
||||
```
|
||||
|
||||
Then wait until your `traefik` by the following command is `1/1` `READY`.
|
||||
|
|
|
|||
Loading…
Reference in a new issue