souleb

Hello, can you provide `kubect describe helmrepository` output for you helmrepo? Also please verify that your secret was generated without extra characters.

yes the secret seems fine. The issue is the `.Spec.URL`. You have `oci://my_domain.azurecr.io/helm` in your `Helmreposiroty` and I think it should be `oci://my_domain.azurecr.io/helm/mongodb`. Because I think you have a `mongodb`...

Hi @ahsanemon sorry for misleading you. `https://my_domain.azurecr.io/v2/helm/mongodb/tags/list` is right. I tested it, and here is what I get ```sh Name: podinfo-private-az Namespace: default Labels: Annotations: API Version: source.toolkit.fluxcd.io/v1beta2 Kind: HelmRepository...

Hi, thanks for filling this issue. The client should definitely follow to up to 10 redirects for `301`, `302`, `303`. Let me look at the code.

Hi @aek-arm in the current code, we compute a URI for the request. In our case it would be `/rest/api/1.0/projects/?name=project_name`. When the append the it tho the base URL (set...

@Chili-Man I think it is better to ask on slack so we can provide examples.

@Thaval can we get the root of `./corpsol`?

Hello there. `kustomize-controller` expects a secret with a token with sufficient rights to fetch master keys from vault transit engine. `kustomize-controller` doesn't make any assumption on the token, so you...

when fetching the secret, `kustomize-controller` does it in the target namespace, not cluster wide, so you have an isolation at that level. That's no longer the case with an envar....

I see it the other way around. How to make sure that an env var provided to a controller that reconciles workloads cluster wide can be constrained to only specific...