Skip to content

Failure when the helmrepository and the helmrelease are in different namespaces #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
xavidop opened this issue Sep 4, 2024 · 4 comments · Fixed by #15
Closed

Failure when the helmrepository and the helmrelease are in different namespaces #12

xavidop opened this issue Sep 4, 2024 · 4 comments · Fixed by #15
Assignees

Comments

@xavidop
Copy link

xavidop commented Sep 4, 2024

Hello,

We found an issue where we have the helmrelease in namespace X and the helmrepository in namespace Y mta fails to migrate the helmrelease with error:

FATA[0002] helmrepositories.source.toolkit.fluxcd.io "Y" not found

The command we run is:

mta helmrelease --name my-helmrelease --namespace X
@christianh814
Copy link
Member

Updating here from the Discord https://discord.com/channels/1138942074998235187/1280808653280116818/1282608495409238038

Looks like a version mismatch https://github.com/akuity/mta/blob/main/pkg/utils/utils.go#L11C56-L12C1

@nitishfy we might consider making it "backwards compatible" for whichever version Flux currently supports.

@christianh814
Copy link
Member

Looks like I was mistaken. The issue is that mta assumes HelmRelease and HelmRepo objects are in the same namespace.

@xavidop
Copy link
Author

xavidop commented Sep 10, 2024

yeah that was my thought too

@nitishfy
Copy link
Member

The fix is out now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants