Corentin Néau

> Tried with Basic Auth, using PAT(authorized it for the org). Would something like `https://:@github.com/org/repo.git` work and be acceptable from a security point of view?

Hi @codering, self-signed certificates should [already be supported](https://github.com/rancher/fleet/pull/1591); have you tried specifying a secret from your self-signed cert and referencing it in your GitRepo, as explained [here](http://fleet.rancher.io/gitrepo-add#using-private-helm-repositories)?

Already done.

## Additional QA ### Problem `namespaceLabels` and `namespaceAnnotations`, specified as bundle deployment options in [fleet.yaml](https://fleet.rancher.io/ref-fleet-yaml#reference), could only be specified once for all clusters, but could not be overridden on a...

The issue mentioned in the previous comment should be fixed by #3052.

This is unsupported, and was probably broken by [this commit](https://github.com/helm/helm/commit/dc158f6208782b888fc5be6d23d8991042cf9f9c) in Helm v3.17.0, with v0.11.7 using v3.16.

Closing as duplicate of #3596.

Closing as the approach we have in mind is rather #3399.

## Additional QA ### Problem Fleet fails to deploy a workload pointing to a Helm registry using a custom CA. ### Solution Fleet takes Rancher-configured CA bundle [secrets](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-references/helm-chart-options#additional-trusted-cas) into account,...

> @manno #2917 got merged into `main` while the issue here is scheduled for `2.9.3` 🤔 /cc @weyfonk Good catch. Updated the milestone to `v2.10.0` on this issue and created...