From ea0ea8cbfae196d5da81ad2acbd7d020122bad1a Mon Sep 17 00:00:00 2001
From: kurokobo <2920259+kurokobo@users.noreply.github.com>
Date: Fri, 10 Jun 2022 21:23:59 +0900
Subject: [PATCH] fix: change the way to patch traefik to creating yaml file

---
 galaxy/README.md        | 14 ++++++++++++--
 tips/troubleshooting.md | 14 ++++++++++++--
 2 files changed, 24 insertions(+), 4 deletions(-)

diff --git a/galaxy/README.md b/galaxy/README.md
index 20a8963..d77f002 100644
--- a/galaxy/README.md
+++ b/galaxy/README.md
@@ -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`.
diff --git a/tips/troubleshooting.md b/tips/troubleshooting.md
index 4da83dc..645fa63 100644
--- a/tips/troubleshooting.md
+++ b/tips/troubleshooting.md
@@ -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`.