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

[Crossport]Rely on only container name while parsing feature flags (#422) #431

Merged
merged 1 commit into from
Dec 7, 2021

Conversation

deepakkinni
Copy link
Collaborator

@deepakkinni deepakkinni commented Dec 7, 2021

The PR ensures that the plugin uses only the container name to determine velero container.
What this PR does / why we need it:

Which issue(s) this PR fixes:
Fixes #421

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Cherry-pick #422: Add support for velero image with sha tag

Signed-off-by: Deepak Kinni dkinni@vmware.com

…#422)

The PR ensures that the plugin uses only the container name to determine velero container.

Signed-off-by: Deepak Kinni <dkinni@vmware.com>
@xing-yang
Copy link
Contributor

Can you add a release note?

@lintongj
Copy link
Contributor

lintongj commented Dec 7, 2021

Can you add a release note?

@deepakkinni ^^

@xing-yang
Copy link
Contributor

LGTM other than that.

@deepakkinni
Copy link
Collaborator Author

Can you add a release note?

doesn't have user facing changes, it's internal. Not sure what release note needs to be added.

@svcbot-qecnsdp
Copy link

Sorry, some of the pre-check tests are failing for this PR !

Please check the Jenkins job for more details
https://container-dp.svc.eng.vmware.com/job/CNSDP-CI/660/

@xing-yang
Copy link
Contributor

@deepakkinni This is actually a user facing bug. You can add "Add support for velero image with sha tag".

@lintongj lintongj merged commit b8ffd5c into vmware-tanzu:release-1.3 Dec 7, 2021
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.

4 participants