diff --git a/content/en/docs/next/guides/use-cases/private-cloud.md b/content/en/docs/next/guides/use-cases/private-cloud.md index 66a82d99..071ac5bd 100644 --- a/content/en/docs/next/guides/use-cases/private-cloud.md +++ b/content/en/docs/next/guides/use-cases/private-cloud.md @@ -18,7 +18,3 @@ You can implement best GitOps practices, where users will launch their own Kuber Thanks to the standardization of the approach to deploying applications, you can expand the platform's capabilities using the functionality of standard Helm charts. ![Cozystack for private cloud](/img/case-private-cloud.png) - -Here you can find reference repository to learn how to configure Cozystack services using GitOps approach: - -- https://github.com/aenix-io/cozystack-gitops-example diff --git a/content/en/docs/next/operations/faq/_index.md b/content/en/docs/next/operations/faq/_index.md index 1d758339..1b757816 100644 --- a/content/en/docs/next/operations/faq/_index.md +++ b/content/en/docs/next/operations/faq/_index.md @@ -72,9 +72,9 @@ Dashboard will become available under: `https://dashboard.`
How to configure Cozystack using FluxCD or ArgoCD -Here you can find reference repository to learn how to configure Cozystack services using GitOps approach: +Cozystack applications are ordinary Kubernetes resources, so a GitOps workflow needs nothing specific to the platform: point FluxCD or ArgoCD at a repository holding your `Tenant`, `Kubernetes` and application manifests, and reconcile them as you would any other objects. The fields of each application are documented on its reference page. -- https://github.com/aenix-io/cozystack-gitops-example +There is no maintained reference repository at the moment. The previous example was written before Cozystack 1.0 and no longer matched the current resources, so it was retired rather than left to mislead.

diff --git a/content/en/docs/v1.5/guides/use-cases/private-cloud.md b/content/en/docs/v1.5/guides/use-cases/private-cloud.md index 0bbeb02d..eed3bd2e 100644 --- a/content/en/docs/v1.5/guides/use-cases/private-cloud.md +++ b/content/en/docs/v1.5/guides/use-cases/private-cloud.md @@ -18,7 +18,3 @@ You can implement best GitOps practices, where users will launch their own Kuber Thanks to the standardization of the approach to deploying applications, you can expand the platform's capabilities using the functionality of standard Helm charts. ![Cozystack for private cloud](/img/case-private-cloud.png) - -Here you can find reference repository to learn how to configure Cozystack services using GitOps approach: - -- https://github.com/aenix-io/cozystack-gitops-example diff --git a/content/en/docs/v1.5/operations/faq/_index.md b/content/en/docs/v1.5/operations/faq/_index.md index e627be0f..03e25df3 100644 --- a/content/en/docs/v1.5/operations/faq/_index.md +++ b/content/en/docs/v1.5/operations/faq/_index.md @@ -72,9 +72,9 @@ Dashboard will become available under: `https://dashboard.`
How to configure Cozystack using FluxCD or ArgoCD -Here you can find reference repository to learn how to configure Cozystack services using GitOps approach: +Cozystack applications are ordinary Kubernetes resources, so a GitOps workflow needs nothing specific to the platform: point FluxCD or ArgoCD at a repository holding your `Tenant`, `Kubernetes` and application manifests, and reconcile them as you would any other objects. The fields of each application are documented on its reference page. -- https://github.com/aenix-io/cozystack-gitops-example +There is no maintained reference repository at the moment. The previous example was written before Cozystack 1.0 and no longer matched the current resources, so it was retired rather than left to mislead.

diff --git a/content/en/docs/v1.6/guides/use-cases/private-cloud.md b/content/en/docs/v1.6/guides/use-cases/private-cloud.md index faef0260..14434006 100644 --- a/content/en/docs/v1.6/guides/use-cases/private-cloud.md +++ b/content/en/docs/v1.6/guides/use-cases/private-cloud.md @@ -18,7 +18,3 @@ You can implement best GitOps practices, where users will launch their own Kuber Thanks to the standardization of the approach to deploying applications, you can expand the platform's capabilities using the functionality of standard Helm charts. ![Cozystack for private cloud](/img/case-private-cloud.png) - -Here you can find reference repository to learn how to configure Cozystack services using GitOps approach: - -- https://github.com/aenix-io/cozystack-gitops-example diff --git a/content/en/docs/v1.6/operations/faq/_index.md b/content/en/docs/v1.6/operations/faq/_index.md index d7e2b8cd..b9b78b65 100644 --- a/content/en/docs/v1.6/operations/faq/_index.md +++ b/content/en/docs/v1.6/operations/faq/_index.md @@ -72,9 +72,9 @@ Dashboard will become available under: `https://dashboard.`
How to configure Cozystack using FluxCD or ArgoCD -Here you can find reference repository to learn how to configure Cozystack services using GitOps approach: +Cozystack applications are ordinary Kubernetes resources, so a GitOps workflow needs nothing specific to the platform: point FluxCD or ArgoCD at a repository holding your `Tenant`, `Kubernetes` and application manifests, and reconcile them as you would any other objects. The fields of each application are documented on its reference page. -- https://github.com/aenix-io/cozystack-gitops-example +There is no maintained reference repository at the moment. The previous example was written before Cozystack 1.0 and no longer matched the current resources, so it was retired rather than left to mislead.