Skip to content

docs(faq): drop the retired GitOps example #661

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
myasnikovdaniil merged 1 commit into from
Aug 20, 2026
Merged

docs(faq): drop the retired GitOps example #661

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions content/en/docs/next/guides/use-cases/private-cloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
4 changes: 2 additions & 2 deletions content/en/docs/next/operations/faq/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,9 +72,9 @@ Dashboard will become available under: `https://dashboard.<your_domain>`
<details>
<summary>How to configure Cozystack using FluxCD or ArgoCD</summary>

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.

</details>
<br>
Expand Down
4 changes: 0 additions & 4 deletions content/en/docs/v1.5/guides/use-cases/private-cloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
4 changes: 2 additions & 2 deletions content/en/docs/v1.5/operations/faq/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,9 +72,9 @@ Dashboard will become available under: `https://dashboard.<your_domain>`
<details>
<summary>How to configure Cozystack using FluxCD or ArgoCD</summary>

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.

</details>
<br>
Expand Down
4 changes: 0 additions & 4 deletions content/en/docs/v1.6/guides/use-cases/private-cloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
4 changes: 2 additions & 2 deletions content/en/docs/v1.6/operations/faq/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,9 +72,9 @@ Dashboard will become available under: `https://dashboard.<your_domain>`
<details>
<summary>How to configure Cozystack using FluxCD or ArgoCD</summary>

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.

</details>
<br>
Expand Down
Loading