flux2 icon indicating copy to clipboard operation
flux2 copied to clipboard

Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.

Results 272 flux2 issues
Sort by recently updated
recently updated
newest added

This is an umbrella issue used to track high-level initiatives in our [Maintainer's Focus board](https://github.com/orgs/fluxcd/projects/6/views/17?layout=board&filterQuery=label%3Aumbrella-issue). **Pre GA Tasks** - [ ] https://github.com/fluxcd/pkg/issues/333 - [ ] https://github.com/fluxcd/pkg/issues/245 - [ ] https://github.com/fluxcd/pkg/issues/334...

area/git
umbrella-issue

### Describe the bug After a local change to the yaml files, that updates some immutable fields of a `Job` , I test with `flux diff` before committing like this:...

bug
area/diff

### Describe the bug Documentation which describes different repository structure options is quite not clear. For example the mono repo scenario https://fluxcd.io/docs/guides/repository-structure/#repository-structure says apps, then inside apps next folders: base,...

Now that fluxcd/pkg#245 has been implemented, the flux CLI should use `pkg/git` for clone operations, instead of using its own custom implementation. A second step on this process is to...

area/git

### Describe the bug I've tried to upgrade helmchart using FluxCD from one version to another. However new chart had issue in .yaml file (passed helm int) When FluxCD tried...

Some clusters have egress traffic rules by which all traffic must go through specific proxies. As of v0.32.0, Flux supports: - HTTP(S) proxies when accessing Git servers via HTTP(S). -...

enhancement
area/git

Given that the artifacts produced by Flux should be immutable, we need to offer a command for deleting old artifacts from the registry.

area/oci

This issue tracks the implementation of context-based authorization across Flux controllers. Below is a list Flux features that could support such functionality, and their current status. | Status | Component...

area/security

In some scenarios Flux uses `.Name` and `.Namespace` fields from Flux objects as label values. For example: ``` kustomize.toolkit.fluxcd.io/name=flux-system kustomize.toolkit.fluxcd.io/namespace=flux-system ``` Therefore, we should add validation to ensure they respect...

### Describe the bug Here is the config file that I have for creating the `rook-ceph-cluster` as defined [here](https://artifacthub.io/packages/helm/rook/rook-ceph-cluster). I can deploy using almost the same layout for the `rook-ceph`...