-
### Description
**Observed Behavior**:
When flux is managing the manifests for nodepools, the following is observed. I am starting from version 0.37.2
Update controller to v1.0.1, and then appl…
-
This architecture is one-way only. CRD changes -> Configure drivers. I know that CSI drivers are usually pretty simple and can usually just be a deployment and daemonset, so maybe this really is the a…
-
### Describe the bug
When you delete a HelmRelease, even with `uninstall.deletionPropagation=foreground`, flux, via helm or otherwise, marks all created resources to be deleted and then removes the…
-
**Describe the bug**
ProhibitedTargets require the path to end with "/*" as described here:
(https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/crds/AzureIngressProhibitedTa…
-
### Problem Statement
A Kyverno installation has minimal permissions, and users will receive an error if they try to install policies that operate on CRDs:
```sh
Error from server: error when cre…
-
Currently helm charts produced by this repository support Helm 2, which is deprecated and should not be used. Unfortunately, they are not very well compatible with Helm 3 and fail to install using Ter…
-
Add NonAdminRestore CRD
Add NonAdminRestore controller
- create restore from NonAdminBackup
- create Velero Restore object
- Namespace must exist prior to restore
-
**Describe the bug**
Hi,
When using "helm upgrade" to upgrade an aws-controller chart, helm does not upgrade CRDs that are in '/crds' folder, even if there were changes.
https://helm.sh/docs/to…
-
**Is your enhancement related to a problem? Please describe.**
Add disable operation for the disk management.
That would be helpful to ensure the replica is not scheduled to this disk.
**Describe…
-
### Describe the bug
I'm attempting a flux bootstrap and am receiving a "repository not found" error
### Steps to reproduce
flux bootstrap github --owner=$GITHUB_USER --repository=fleet-…