DevOps/truecharts
2
0
Fork 0
Code Issues Pull Requests Actions 25 Packages Projects Releases 1 Wiki Activity

chore(docs): fix some mroe

Browse Source
This commit is contained in:
Stavros Kois
2024-04-14 01:31:56 +03:00
committed by GitHub
parent 8e32cbb012
commit fe741b8951
5 changed files with 16 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
charts/stable/apt-cacher-ng/docs/how-to.md
+1 -1
View File
@@ -5,7 +5,7 @@ title: How-To
To start using Apt-Cacher NG on your Debian (Based) host, create the
configuration file `/etc/apt/apt.conf.d/01proxy` with the following content:
```conf
```apache
Acquire::HTTP::Proxy "http://SERVER.IP:3142";
Acquire::HTTPS::Proxy "false";
```
charts/stable/crafty-4/docs/credentials.md
+1 -1
View File
@@ -7,6 +7,6 @@ title: Default Credentials
Shell into the app and run this command to print it to shell:
```terminal
```shell
cat /crafty/app/config/default-creds.txt
```
charts/stable/external-dns/docs/setup-guide.md
+4 -2
View File
@@ -43,7 +43,8 @@ I recommend using `noop` for `Registry Type` and leaving the rest as default, ca
Verify it works, check the logs for updates to DNS records
```2023-11-07 09:36:07.165596-05:00time="2023-11-07T09:36:07-05:00" level=info msg="Instantiating new Kubernetes client"
```shell
2023-11-07 09:36:07.165596-05:00time="2023-11-07T09:36:07-05:00" level=info msg="Instantiating new Kubernetes client"
2023-11-07 09:36:07.165633-05:00time="2023-11-07T09:36:07-05:00" level=info msg="Using inCluster-config based on serviceaccount-token"
2023-11-07 09:36:07.165850-05:00time="2023-11-07T09:36:07-05:00" level=info msg="Created Kubernetes client https://172.17.0.1:443"
2023-11-07 09:36:08.958946-05:00time="2023-11-07T09:36:08-05:00" level=info msg="Changing record." action=CREATE record=seafile.DOMAIN.com ttl=1 type=A zone=d959ce24eb85d78a7f527b6150446335
@@ -67,7 +68,8 @@ Change to `noop` for `Registry Type` and add `PiHole Server Address` (default is
Verify logs from `External-DNS` to see if it connects and updates `PiHole`
```d:false IBMCloudConfigFile:/etc/kubernetes/ibmcloud.json TencentCloudConfigFile:/etc/kubernetes/tencent-cloud.json TencentCloudZoneType: PiholeServer:http://pihole.ix-pihole.svc.cluster.local:9089 PiholePassword:****** PiholeTLSInsecureSkipVerify:false PluralCluster: PluralProvider:}"
```shell
d:false IBMCloudConfigFile:/etc/kubernetes/ibmcloud.json TencentCloudConfigFile:/etc/kubernetes/tencent-cloud.json TencentCloudZoneType: PiholeServer:http://pihole.ix-pihole.svc.cluster.local:9089 PiholePassword:****** PiholeTLSInsecureSkipVerify:false PluralCluster: PluralProvider:}"
2023-11-07 10:29:07.801555-05:00time="2023-11-07T10:29:07-05:00" level=info msg="Instantiating new Kubernetes client"
2023-11-07 10:29:07.801568-05:00time="2023-11-07T10:29:07-05:00" level=info msg="Using inCluster-config based on serviceaccount-token"
2023-11-07 10:29:07.801861-05:00time="2023-11-07T10:29:07-05:00" level=info msg="Created Kubernetes client https://172.17.0.1:443"
charts/stable/zigbee2mqtt/docs/installation.md
+9 -9
View File
@@ -12,19 +12,19 @@ Enter `MQTT User`, `MQTT Password` if necessary, as this will override the speci
For `MQTT Server` Internal DNS Cluster IP can be used (default) of `mqtt://mosquitto.ix-mosquitto.svc.cluster.local` or you can use the external IP.
![config1](images/config1.png)
![config1](images/config1.png)
![config2](images/config2.png)
![config3](images/config3.png)
![config4](images/config4.png)
![config5](images/config5.png)
![config1](./images/config1.png)
![config1](./images/config1.png)
![config2](./images/config2.png)
![config3](./images/config3.png)
![config4](./images/config4.png)
![config5](./images/config5.png)
### Mount USB Devices
Make sure `Enable the Storage is Checked` and enter your USB device by ID as per below, in this example we use `/dev/serial/by-id/usb-ithead_SONOFF`
![config6](images/config6.png)
![config6](./images/config6.png)
This guide should prevent one of the following error messages:
![error message 1](images/error_log1.png)
![error message 2](images/error_log2.png)
![error message 1](./images/error_log1.png)
![error message 2](./images/error_log2.png)
charts/system/prometheus-operator/docs/installation.md
+1 -1
View File
@@ -8,7 +8,7 @@ title: Troubleshooting
If you get
![Error message: [EFAULT] Failed to install App: Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition "alertmanagerconfigs.monitoring.coreos.com" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "prometheus-operator"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "ix-prometheus-operator"](images/install_error_message.webp)
![Error message: [EFAULT] Failed to install App: Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition "alertmanagerconfigs.monitoring.coreos.com" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "prometheus-operator"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "ix-prometheus-operator"](./images/install_error_message.webp)
> [EFAULT] Failed to install App: Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition "alertmanagerconfigs.monitoring.coreos.com" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "prometheus-operator"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "ix-prometheus-operator"