From 7086146d6c9e112e5dfb6d74d586c86d1b5bfe6f Mon Sep 17 00:00:00 2001 From: khanhtc1202 Date: Tue, 5 Jul 2022 14:28:20 +0700 Subject: [PATCH] Update docs reflect archivement of manifests repository --- .../docs-dev/operator-manual/control-plane/installation.md | 6 +++--- .../piped/installation/installing-on-kubernetes.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/content/en/docs-dev/operator-manual/control-plane/installation.md b/docs/content/en/docs-dev/operator-manual/control-plane/installation.md index 896a5d61db..8cd56c7472 100644 --- a/docs/content/en/docs-dev/operator-manual/control-plane/installation.md +++ b/docs/content/en/docs-dev/operator-manual/control-plane/installation.md @@ -97,7 +97,7 @@ __Caution__: In case of using `MySQL` as Control Plane's datastore, please note ### 4. Accessing the PipeCD web -If your installation was including an [ingress](https://github.com/pipe-cd/manifests/blob/master/manifests/pipecd/values.yaml#L6), the PipeCD web can be accessed by the ingress's IP address or domain. +If your installation was including an [ingress](https://github.com/pipe-cd/pipecd/blob/master/manifests/pipecd/values.yaml#L7), the PipeCD web can be accessed by the ingress's IP address or domain. Otherwise, private PipeCD web can be accessed by using `kubectl port-forward` to expose the installed Control Plane on your localhost: ``` console @@ -112,7 +112,7 @@ This part provides guidance for a production hardened deployment of the control - Publishing the control plane - You can allow external access to the control plane by enabling the [ingress](https://github.com/pipe-cd/manifests/blob/master/manifests/pipecd/values.yaml#L6) configuration. + You can allow external access to the control plane by enabling the [ingress](https://github.com/pipe-cd/pipecd/blob/master/manifests/pipecd/values.yaml#L7) configuration. - End-to-End TLS @@ -123,7 +123,7 @@ This part provides guidance for a production hardened deployment of the control ``` console openssl req -x509 -nodes -days 3650 -newkey rsa:2048 -keyout tls.key -out tls.crt -subj "/CN={YOUR_DOMAIN}" ``` - Those key and cert can be configured via [`secret.internalTLSKey.data`](https://github.com/pipe-cd/manifests/blob/master/manifests/pipecd/values.yaml#L83) and [`secret.internalTLSCert.data`](https://github.com/pipe-cd/manifests/blob/master/manifests/pipecd/values.yaml#L86). + Those key and cert can be configured via [`secret.internalTLSKey.data`](https://github.com/pipe-cd/pipecd/blob/master/manifests/pipecd/values.yaml#L118) and [`secret.internalTLSCert.data`](https://github.com/pipe-cd/pipecd/blob/master/manifests/pipecd/values.yaml#L121). To enable internal tls connection, please set the `gateway.internalTLS.enabled` parameter to be `true`. diff --git a/docs/content/en/docs-dev/operator-manual/piped/installation/installing-on-kubernetes.md b/docs/content/en/docs-dev/operator-manual/piped/installation/installing-on-kubernetes.md index 73c68bd9ef..3ee791305c 100644 --- a/docs/content/en/docs-dev/operator-manual/piped/installation/installing-on-kubernetes.md +++ b/docs/content/en/docs-dev/operator-manual/piped/installation/installing-on-kubernetes.md @@ -85,7 +85,7 @@ helm upgrade -i dev-piped oci://ghcr.io/pipe-cd/chart/piped --version={{< blocks Note: Be sure to set `--set args.insecure=true` if your Control Plane has not TLS-enabled yet. - See [values.yaml](https://github.com/pipe-cd/manifests/blob/master/manifests/piped/values.yaml) for the full values. + See [values.yaml](https://github.com/pipe-cd/pipecd/blob/master/manifests/piped/values.yaml) for the full values. ## In the namespaced mode The previous way requires installing cluster-level resources. If you want to restrict Piped's permission within the namespace where Piped runs on, this way is for you.