weave-gitops icon indicating copy to clipboard operation
weave-gitops copied to clipboard

Weave GitOps provides insights into your application deployments, and makes continuous delivery with GitOps easier to adopt and scale across your teams.

Results 263 weave-gitops issues
Sort by recently updated
recently updated
newest added

As a user when I am done running `gitops run` I want to be able to transition my workloads to a gitops workflow. This means I need to have the...

team/denim

We currently provide no guidance within the documentation for setting appropriate controls around which updates will be automatically applied to the Weave GitOps server. By default, users will get the...

documentation
team/denim

This is enterprise only

Epic
team/denim

As a user, I understand you are trying to build a product that helps me to get the job done and to do that effectively, data can be useful. Please...

team/denim

We need to document which browsers we support. We will only support the latest and prior two versions of the following browsers: * Edge * Firefox * Chrome * Safari...

documentation
team/denim

As a user when I stop the sync by ending the process then all of my files on the local filesystem remain. However, the workloads on the cluster no longer...

team/denim

We want to simplify the OSS codebase and the CLI as a product in general. The first step is to move the enterprise CLI commands into a separate repository and...

team/denim

On enterprise pages such as https://docs.gitops.weave.works/docs/0.8.1/cluster-management/getting-started/ (0.8.1) or https://docs.gitops.weave.works/docs/cluster-management/getting-started/ (current) the little "enterprise" tier label right to the heading always links to the "next" version instead of the one that...

bug
documentation
severity/Minor

**Describe the bug** I'm trying to install Weave Gitops into an EKS cluster that was installed with Weave GitOps Enterprise 0.8.1. I'm currently building a demo to show improved developer...

bug

While doing https://github.com/weaveworks/weave-gitops/issues/1959, it was [pointed out to me](https://github.com/weaveworks/weave-gitops/pull/2008#discussion_r858781963) that: > we expect --insecure to pretty much always be set for security reasons: you'll have a separate ingress to encrypt...

type/story
team/denim