Skip to content
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

Fix custom restic-restore-helper image not being used #42

Merged

Conversation

jmontleon
Copy link

@jmontleon jmontleon commented Dec 10, 2019

@sseago @dymurray can you help me get this merged to the correct branch for 1.0.1?

There are two issues. Because we went downt he route of installing velero in a custom namespaces the DefaultNamespace being used to lookup configuration is wrong and velero never finds the configmap.

The second issue is that when found we get an error message that the image is unparseable because the original code does not account for a registry with the port specified.

This was reported and fixed in velero and I have the same fix here, which resolves the problem, even though it is not particularly suited to using SHAs:
vmware-tanzu#1972
vmware-tanzu#1999

@jmontleon jmontleon changed the base branch from fusor-dev to fusor-1.1 December 10, 2019 16:00
@jmontleon jmontleon force-pushed the fix-restic-helper-configmap-ns branch from b24ac7a to 6e18531 Compare December 10, 2019 16:01
Copy link

@sseago sseago left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

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

Successfully merging this pull request may close these issues.

3 participants