Mario Manno
Mario Manno
I think they are not needed, yet they show up as empty in every resource 🤷
SURE-9010 - Gitrepos are in Error state with read-only file system - [x] add emptydir mount on tmp - [ ] the security context should not be disabled when running...
Backport of #2716 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior When using fleet to deploy the following fleet...
We want to notify external services about events in Fleet, so users can build workflows around Fleet as a deployer. For now we are focusing on one type of outgoing...
Just like GitRepo for GitOps, we want a OCI/Helm resource in Fleet to deploy Helm charts in a more direct way. Ideally this leverages OCI to the fullest. ## Research...
Follow up on https://github.com/rancher/fleet/issues/2826 Installing the fleet helm chart with `--set debug` also disables the security contexts on pods to allow for a debugger to be attached. Might also be...
Gitjob is now in the fleet repo. However, we are missing system registry support and a way to set `gitjob.tag` to fleet's version. The git k8s job still uses two...
Fleet apply should not stop processing when it encounters an error in one of the bundles. was https://github.com/rancher/fleet/issues/2655
Follow up for https://github.com/rancher/fleet/issues/2962 Updated from the RFC * make sure GitOps bundle is not overwritten by helmapp of the same name, collision * support three chart sources: tarball, helm...
* Remove tests that didn't show any variation * create-1-bundle * create-1-gitrepo-1-big-bundle * create-1-gitrepo-1-bundle * Add new "150 bundles" test for targeting phase * Improve the output by adding descriptions....