civo · kaihoffman · Oct 12, 2023 · Oct 11, 2023 · Oct 11, 2023 · Oct 11, 2023
diff --git a/acorn/1 b/acorn/1
@@ -3,7 +3,7 @@ name: Acorn
 version: 0.1
 maintainer: [email protected], [email protected]
 description: A simple application deployment framework for Kubernetes
-url: https://acorn.io
+url: https://www.acorn.io/
 category: management
 configuration:
   CLUSTER_ID:

diff --git a/acorn/manifest.yaml b/acorn/manifest.yaml
@@ -3,7 +3,7 @@ name: Acorn
 version: 0.7.1
 maintainer: [email protected], [email protected], [email protected]
 description: A simple application deployment framework for Kubernetes
-url: https://acorn.io
+url: https://www.acorn.io/
 category: management
 plans:
 - label: "Disabled Auto-TLS"

diff --git a/acorn/post_install.md b/acorn/post_install.md
@@ -1,4 +1,6 @@
-Acron is  simple application deployment framework for Kubernetes. This application installs the server side components to the Civo Kubernetes cluster. In order to build/deploy your application you need to download the acorn cli locally using following command.
+Acron is  simple application deployment framework for Kubernetes. This application installs the server side components to the Civo Kubernetes cluster. 
+
+In order to build/deploy your application you need to download the acorn cli locally using following command:
 
 ```
 For macOS/Linux
@@ -10,5 +12,6 @@ brew install acorn-io/cli/acorn
 curl https://get.acorn.io | sh
 ```
 
-Then head over to the [Getting started page](https://docs.acorn.io/getting-started)
-
+Then head over to:
+*[Acorn documentation getting started page](https://docs.acorn.io/getting-started)
+*[Civo Acron tutorials](https://www.civo.com/learn/categories/acorn)
diff --git a/aspnet/manifest.yaml b/aspnet/manifest.yaml
@@ -4,5 +4,5 @@ title: "ASP.NET core"
 version: "5.0.5"
 maintainer: [email protected]
 description: ASP.NET Core is an open-source framework created by Microsoft for building cloud-enabled, modern applications.
-url: https://docs.microsoft.com/en-us/aspnet/core/?view=aspnetcore-5.0
+url: https://learn.microsoft.com/en-us/aspnet/core/?view=aspnetcore-5.0
 category: management
diff --git a/aspnet/post_install.md b/aspnet/post_install.md
@@ -4,13 +4,13 @@
 
 ### Get started
 
-[ASP.NET CORE official website.](https://docs.microsoft.com/en-us/aspnet/core/?view=aspnetcore-5.0)
+[ASP.NET CORE official website.](https://learn.microsoft.com/en-us/aspnet/core/?view=aspnetcore-5.0)
 
 
 [For addition information](https://bitnami.com/stack/aspnet-core/helm)
 
 
-[ASP.NET CORE Documentations documentation.](https://docs.microsoft.com/en-us/aspnet/core/?view=aspnetcore-5.0)
+[ASP.NET CORE Documentations documentation.](https://learn.microsoft.com/en-us/aspnet/core/?view=aspnetcore-5.0)
 
 
-For advanced configurations of visit [Values.yaml](https://github.com/bitnami/charts/raw/master/bitnami/aspnet-core/values.yaml)
+For advanced configurations of visit [Values.yaml](https://github.com/bitnami/charts/blob/main/bitnami/aspnet-core/Chart.yaml)
diff --git a/bitwardenrs/manifest.yaml b/bitwardenrs/manifest.yaml
@@ -3,7 +3,7 @@ name: Bitwardenrs
 version: 1.17.0
 maintainer: [email protected]
 description: Open Source Password Manager (Bitwarden server API implementation written in Rust) 
-url: https://github.com/dani-garcia/bitwarden_rs
+url: https://github.com/dani-garcia/vaultwarden
 category: management
 dependencies:
   - cert-manager

diff --git a/chaos-mesh/post_install.md b/chaos-mesh/post_install.md
@@ -2,11 +2,11 @@
 
 ### Usage instruction
 
-See the [documentations](https://chaos-mesh.org/docs)
+See the [documentations](https://chaos-mesh.org/docs/)
 
 ### Log in Chaos Dashboard
 
-Chaos Dashboard supports a security mode, which requires users to login with a token generated by Kubernetes. Each token is linked to a `service account`. You can only perform operations within the scope as allowed by the role that is associated with the service account. By default, the security mode is enabled when using helm to install Chaos Mesh. You can refer this [documentation](https://chaos-mesh.org/docs/user_guides/dashboard#log-in) to create the account and the token. 
+Chaos Dashboard supports a security mode, which requires users to login with a token generated by Kubernetes. Each token is linked to a `service account`. You can only perform operations within the scope as allowed by the role that is associated with the service account. By default, the security mode is enabled when using helm to install Chaos Mesh. You can refer this [documentation](https://chaos-mesh.org/docs/quick-start/) to create the account and the token. 
 
 If you want to create the account later and start using Chaos Dashboard quickly, you can use the token of Chaos Mesh. Get the token by executing the command: 
 

diff --git a/code-server/manifest.yaml b/code-server/manifest.yaml
@@ -4,7 +4,7 @@ title: "Code Server"
 version: 3.11.1
 maintainer: "@ruanbekker"
 description: Run VS Code on any machine anywhere and access it through the browser.
-url: https://github.com/cdr/code-server
+url: https://github.com/coder/code-server
 category: management
 dependencies:
   - cert-manager

diff --git a/code-server/post_install.md b/code-server/post_install.md
@@ -12,6 +12,5 @@ Once you have installed this app you will be able to connect to the web interfac
 
 For more information, see the project's github repository and their documentation:
 
-* https://github.com/cdr/code-server
-* https://coder.com/docs/code-server/v3.11.1/guide 
-
+* https://github.com/coder/code-server
+* https://coder.com/docs/code-server/v3.11.1/guide
diff --git a/enroute-onestep/install.sh b/enroute-onestep/install.sh
@@ -1,9 +1,9 @@
 #!/bin/bash
 
 # Add the EnRoute One-Step API Gateway helm repository
-helm repo add saaras https://getenroute.io
+helm repo add saaras https://www.getenroute.io/
 helm repo update
 
 # Install the helm chart
-# https://getenroute.io/docs/getting-started-enroute-ingress-controller/
+# https://docs.getenroute.io/docs/prologue/introduction/
 helm install enroute-demo saaras/enroute --set enrouteService.rbac.create=true
diff --git a/enroute-onestep/manifest.yaml b/enroute-onestep/manifest.yaml
@@ -4,7 +4,7 @@ title: "EnRoute OneStep Ingress API Gateway"
 version: "0.8.0"
 maintainer: "@chintan8saaras"
 description: EnRoute OneStep is an Envoy based Kubernetes-native API Gateway.
-url: https://getenroute.io/docs/getting-started-enroute-ingress-controller/
+url: https://docs.getenroute.io/docs/prologue/introduction/
 category: architecture
 required_services:
   - loadbalancer
diff --git a/enroute-onestep/post_install.md b/enroute-onestep/post_install.md
@@ -1,10 +1,10 @@
 ## EnRoute-OneStep Kubernetes Native API Gateway - An Envoy-Powered API Gateway
 EnRoute will create enroute-demo service of type LoadBalancer which will launch a [Civo Load Balancer](https://www.civo.com/load-balancers) (at an additional charge).
 
-[EnRoute-OneStep](https://getenroute.io) is a lightweight shim on Envoy proxy that makes it extremely easy to secure and route traffic destined to microservices running inside Kubernetes Cluster.
+[EnRoute-OneStep](https://www.getenroute.io/) is a lightweight shim on Envoy proxy that makes it extremely easy to secure and route traffic destined to microservices running inside Kubernetes Cluster.
 
 EnRoute-OneStep can be programmed by a developer using one command. Policy Overlays provide a meschanism to Operations teams to retain control and specify shared policy.
 
 ## Getting Started
 
-[Getting started](https://getenroute.io/docs/getting-started-enroute-ingress-controller/) with EnRoute-OneStep involves running [only one command](https://getenroute.io/docs/one-step-ingress/)
+[Getting started](https://docs.getenroute.io/docs/prologue/introduction/) with EnRoute-OneStep involves running [only one command](https://docs.getenroute.io/docs/prologue/getting-started-standalone/)
diff --git a/ferretdb/post_install.md b/ferretdb/post_install.md
@@ -23,7 +23,7 @@ spec:
 ```
 
 This will open up `YOUR_CLUSTER_ID.k8s.civo.com:27017` to the whole world.
-You should lock this down in the [firewall](https://www.civo.com/account/firewalls)
+You should lock this down in the [firewall](https://dashboard.civo.com/firewalls)
 automatically created in Civo for your Kubernetes cluster.
 Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster,
 access from your applications within Kubernetes will not be affected.
diff --git a/flux/post_install.md b/flux/post_install.md
@@ -1,12 +1,12 @@
 ## Flux
 
 Flux is a Continuous Delivery solution for Kubernetes.
-Flux is constructed with the [GitOps Toolkit](https://fluxcd.io/docs/components/),
+Flux is constructed with the [GitOps Toolkit](https://fluxcd.io/flux/components/),
 a set of composable APIs and specialized tools for keeping Kubernetes clusters in sync
 with sources of configuration (like Git & Helm repositories), and automating updates
 to configuration when there is new code to deploy.
 
-Flux is a [CNCF](https://cncf.io) project made for:
+Flux is a [CNCF](https://www.cncf.io/) project made for:
 
 - **cluster operators** who automate provision and configuration of clusters
 - **platform engineers** who build continuous delivery for developer teams
@@ -16,10 +16,10 @@ Flux is a [CNCF](https://cncf.io) project made for:
 
 To get started with Flux, [browse the documentation](https://fluxcd.io) or try the following guides:
 
-- [Get started with Flux](https://fluxcd.io/docs/get-started/)
+- [Get started with Flux](https://fluxcd.io/flux/get-started/)
 - [GitOps workflow for multi-env deployments with Flux, Kustomize and Helm](https://github.com/fluxcd/flux2-kustomize-helm-example)
-- [Manage Kubernetes secrets with Mozilla SOPS](https://fluxcd.io/docs/guides/mozilla-sops/)
-- [Automate container image updates to Git](https://fluxcd.io/docs/guides/image-update/)
+- [Manage Kubernetes secrets with Mozilla SOPS](https://fluxcd.io/flux/guides/mozilla-sops/)
+- [Automate container image updates to Git](https://fluxcd.io/flux/guides/image-update/)
 - [Manage multi-tenant clusters with Flux](https://github.com/fluxcd/flux2-multi-tenancy)
 
 ## Upgrade instruction

diff --git a/gatekeeper/post_install.md b/gatekeeper/post_install.md
@@ -4,11 +4,11 @@ Gatekeeper is a Policy Controller for Kubernetes
 
 ### Gatekeeper is different from OPA
 
-Compared to using [OPA with its sidecar kube-mgmt](https://www.openpolicyagent.org/docs/kubernetes-admission-control.html) (aka Gatekeeper v1.0), Gatekeeper introduces the following functionality:
+Compared to using [OPA with its sidecar kube-mgmt](https://www.openpolicyagent.org/docs/latest/kubernetes-tutorial/) (aka Gatekeeper v1.0), Gatekeeper introduces the following functionality:
 
 - An extensible, parameterized policy library
 - Native Kubernetes CRDs for instantiating the policy library (aka "constraints")
 - Native Kubernetes CRDs for extending the policy library (aka "constraint templates")
 - Audit functionality
 
-### To check out how to use Gatekeeper head over [here](https://open-policy-agent.github.io/gatekeeper/website/docs/howto)
+### To check out how to use Gatekeeper head over [here](https://open-policy-agent.github.io/gatekeeper/website/docs/howto/)
diff --git a/gitea/manifest.yaml b/gitea/manifest.yaml
@@ -4,7 +4,7 @@ title: "Gitea"
 version: 1.12.5
 maintainer: "@giteaio"
 description: Gitea is a community managed lightweight code hosting solution written in Go.
-url: https://gitea.io
+url: https://about.gitea.com/
 category: management
 configuration:
   ADMIN_PASS:

diff --git a/jenkins/manifest.yaml b/jenkins/manifest.yaml
@@ -3,7 +3,7 @@ name: Jenkins
 version: 2.414.2
 maintainer: "@dirien"
 description: Jenkins is a Continuous Integration and Delivery server
-url: https://jenkins.io
+url: https://www.jenkins.io/
 category: ci_cd
 plans:
   - label: "5GB"

diff --git a/jenkins/post_install.md b/jenkins/post_install.md
@@ -26,7 +26,7 @@ spec:
                number: 8080
 ```
 
-This will open up http://jenkins.YOUR-CLUSTER-ID.k8s.civo.com to the whole world. You should lock this down in the [firewall](https://www.civo.com/account/firewalls) automatically created in Civo for your Kubernetes cluster. Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster, access from your applications within Kubernetes will not be affected.
+This will open up http://jenkins.YOUR-CLUSTER-ID.k8s.civo.com to the whole world. You should lock this down in the [firewall](https://dashboard.civo.com/firewalls) automatically created in Civo for your Kubernetes cluster. Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster, access from your applications within Kubernetes will not be affected.
 
 ### Usage instruction
 

diff --git a/keptn/post_install.md b/keptn/post_install.md
@@ -83,5 +83,5 @@ spec:
 
 ## Documentation and tutorials
 
-- Find more information in the [Keptn documentation](https://keptn.sh/docs).
+- Find more information in the [Keptn documentation](https://keptn.sh/docs/).
 - Check out the [Keptn tutorials](https://tutorials.keptn.sh/?cat=quality-gates) that help you get started with different use-cases.
diff --git a/kong-ingress-controller/post_install.md b/kong-ingress-controller/post_install.md
@@ -1,6 +1,6 @@
 ## Kong Ingress Controller
 
-[Kong Ingress Controller](https://docs.konghq.com/kubernetes-ingress-controller/) is open-source Ingress Controller for Kubernetes that offers API management capabilities with a plugin architecture.
+[Kong Ingress Controller](https://docs.konghq.com/kubernetes-ingress-controller/latest/) is open-source Ingress Controller for Kubernetes that offers API management capabilities with a plugin architecture.
 
 ### Get started
 

diff --git a/kubeclarity/post_install.md b/kubeclarity/post_install.md
@@ -18,4 +18,4 @@ $ kubectl port-forward --namespace kubeclarity svc/kubeclarity-kubeclarity 9999:
 ```
 Now access the Kubeclarity UI at `http://localhost:9999/` and then select the runtime scan tab on the left, click on start scan after selecting the namespaces you want to scan.
 
-To know more, check the [official guide](https://github.com/cisco-open/kubei).
+To know more, check the [official guide](https://github.com/openclarity/kubeclarity).
diff --git a/kubevela/post_install.md b/kubevela/post_install.md
@@ -1,7 +1,7 @@
 ## KubeVela
 
 KubeVela is a modern software delivery control plane. The goal is to make deploying and operating applications across
-today's hybrid, multi-cloud environments easier, faster and more reliable. KubeVela is a [CNCF](https://cncf.io) project.
+today's hybrid, multi-cloud environments easier, faster and more reliable. KubeVela is a [CNCF](https://www.cncf.io/) project.
 Welcome onboard and sail Vela!
 
 ### Quick Start

diff --git a/linkerd/post_install.md b/linkerd/post_install.md
@@ -14,6 +14,6 @@ This will automatically open the Linkerd dashboard in your browser, or you can v
 
 ### Usage instructions
 
-Linkerd provides instructions on [installing a demo application](https://linkerd.io/2/getting-started/#step-5-install-the-demo-app) that uses Linkerd on their site. It's worth a read and a play with service meshes to get the hang of how/when they are of benefit.
+Linkerd provides instructions on [installing a demo application](https://linkerd.io/2.14/getting-started/#step-5-install-the-demo-app) that uses Linkerd on their site. It's worth a read and a play with service meshes to get the hang of how/when they are of benefit.
 
 Linkerd's minimal install is comfortable on a cluster as small as a single node extra small instance. A single node cluster of size small or greater can accomodate installing Linkerd and any extensions you like.
diff --git a/longhorn/post_install.md b/longhorn/post_install.md
@@ -26,7 +26,7 @@ spec:
   type: LoadBalancer
 ```
 
-This will open up http://YOUR_CLUSTER_ID.k8s.civo.com:8000/dashboard to the whole world. You should lock this down in the [firewall](https://www.civo.com/account/firewalls) automatically created in Civo for your Kubernetes cluster. Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster, access from your applications within Kubernetes will not be affected.
+This will open up http://YOUR_CLUSTER_ID.k8s.civo.com:8000/dashboard to the whole world. You should lock this down in the [firewall](https://dashboard.civo.com/firewalls) automatically created in Civo for your Kubernetes cluster. Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster, access from your applications within Kubernetes will not be affected.
 
 ### Usage instructions
 

diff --git a/mariadb/post_install.md b/mariadb/post_install.md
@@ -19,11 +19,11 @@ spec:
     app: mariadb
 ```
 
-This will open up http://YOUR_CLUSTER_ID.k8s.civo.com:3306 to the whole world. You should lock this down in the [firewall](https://www.civo.com/account/firewalls) automatically created in Civo for your Kubernetes cluster. Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster, access from your applications within Kubernetes will not be affected.
+This will open up http://YOUR_CLUSTER_ID.k8s.civo.com:3306 to the whole world. You should lock this down in the [firewall](https://dashboard.civo.com/firewalls) automatically created in Civo for your Kubernetes cluster. Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster, access from your applications within Kubernetes will not be affected.
 
 ### Usage instruction
 
-You can use this application from within your cluster by just using the hostname `mariadb` and can create databases and users using the `root` access credentials above this message. For example, to create an application's database and user credentials and given that the `kubectx` and [Civo CLI](https://github.com/civo/cli) are installed, with a Civo Kubernetes cluster called `my-cluster-name`:
+You can use this application from within your cluster by just using the hostname `mariadb` and can create databases and users using the `root` access credentials above this message. For example, to create an application's database and user credentials and given that the `kubectx` and [Civo CLI](https://www.civo.com/docs/overview/civo-cli) are installed, with a Civo Kubernetes cluster called `my-cluster-name`:
 
 ```
 $ civo k3s config my-cluster-name --save

diff --git a/metrics-server/post_install.md b/metrics-server/post_install.md
@@ -24,4 +24,4 @@ kubectl top pod --all-namespaces
 
 See the Kubernetes documentation for a worked-example of how to use HPAv2.
 
-[Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/)
+[Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/debug/debug-cluster/resource-metrics-pipeline/)
diff --git a/minio/post_install.md b/minio/post_install.md
@@ -19,7 +19,7 @@ spec:
     app: minio
 ```
 
-This will open up http://YOUR_CLUSTER_ID.k8s.civo.com:9000 to the whole world. You should lock this down in the [firewall](https://www.civo.com/account/firewalls) automatically created in Civo for your Kubernetes cluster. Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster, access from your applications within Kubernetes will not be affected.
+This will open up http://YOUR_CLUSTER_ID.k8s.civo.com:9000 to the whole world. You should lock this down in the [firewall](https://dashboard.civo.com/firewalls) automatically created in Civo for your Kubernetes cluster. Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster, access from your applications within Kubernetes will not be affected.
 
 ### Usage instruction
 

diff --git a/mongodb/post_install.md b/mongodb/post_install.md
@@ -19,11 +19,11 @@ spec:
     app: mongodb
 ```
 
-This will open up YOUR_CLUSTER_ID.k8s.civo.com:27017 to the whole world. You should lock this down in the [firewall](https://www.civo.com/account/firewalls) automatically created in Civo for your Kubernetes cluster. Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster, access from your applications within Kubernetes will not be affected.
+This will open up YOUR_CLUSTER_ID.k8s.civo.com:27017 to the whole world. You should lock this down in the [firewall](https://dashboard.civo.com/firewalls) automatically created in Civo for your Kubernetes cluster. Locking down the firewall will only affect access from OUTSIDE of your Kubernetes cluster, access from your applications within Kubernetes will not be affected.
 
 ### Usage instruction
 
-You can use this application from within your cluster by just using the hostname `mongodb` and can create databases and users using the `root` access credentials above this message. For example, to create an application's database and user credentials and given that the `kubectx` and [Civo CLI](https://github.com/civo/cli) are installed, with a Civo Kubernetes cluster called `my-cluster-name`:
+You can use this application from within your cluster by just using the hostname `mongodb` and can create databases and users using the `root` access credentials above this message. For example, to create an application's database and user credentials and given that the `kubectx` and [Civo CLI](https://www.civo.com/docs/overview/civo-cli) are installed, with a Civo Kubernetes cluster called `my-cluster-name`:
 
 ```
 $ civo k3s config my-cluster-name --save

diff --git a/netdata/post_install.md b/netdata/post_install.md
@@ -8,4 +8,4 @@ kubectl port-forward deployment/netdata-parent -n netdata 19999:19999
 ```
 Now access the netdata UI at `http://localhost:19999`
 
-To know more, check the [official guide](https://learn.netdata.cloud/guides/monitor/kubernetes-k8s-netdata). Also check their [github README](https://github.com/netdata/netdata).
+To know more, check the [official guide](https://learn.netdata.cloud/docs/miscellaneous/kubernetes-monitoring-with-netdata-overview-and-visualizations). Also check their [github README](https://github.com/netdata/netdata).