-
### Expected behaviour
Kustomization name should match that which is specified, i.e. `myapp`
### Actual behaviour
Specified Kustomization name was appended to the name of the source, i.e. `my…
-
This is basically the same as https://github.com/kubernetes-sigs/kustomize/issues/119.
Reopening, as the issue was closed.
The reason for reopening is that we (Arrikto) believe that the reasons give…
-
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Repository problems
These pr…
-
### Describe the bug
Consider the following log:
```
{"level":"info","ts":"2023-07-04T15:44:34.049Z","msg":"server-side apply for cluster definitions completed","controller":"kustomization","cont…
-
We use following kustomizations structure in our projects:
`kustomize.config.k8s.io/v1beta1 -> kustomize.toolkit.fluxcd.io/v1 -> kustomize.toolkit.fluxcd.io/v1 -> helmrelease`
In my setup I have…
-
### Describe the bug
I have the following kustomization crd :
```yaml
apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
kind: Kustomization
metadata:
name: example-develop
namespace: flux…
-
[It's stated in the docs](https://fluxcd.io/docs/faq/#what-is-the-behavior-of-kustomize-used-by-flux) that
> `--reorder` is set to legacy, so the output will have namespaces and cluster roles/role…
-
Checklist:
* [X] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
* [X] I've included steps to reproduce the bug.
* [X] I've pasted the output of `argocd version`.
…
-
Given the following `GitRepository` and `Kustomization`...
```yaml
---
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
name: gitops-examples
namespace: flux-system
…
-
**Describe scenario**
I've enabled GitOps for a repository that contains HelmRepository/HelmRelease for instaling Istio.
GitOps is enabled in flux-system namespace, Cluster wide.
In my repo, und…