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.

Sign up for GitHub

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

Jump to bottom

ARM64 integration testing in backup-restore-operator #45420

Open
MKlimuszka opened this issue May 8, 2024 · 0 comments
Open

ARM64 integration testing in backup-restore-operator #45420

MKlimuszka opened this issue May 8, 2024 · 0 comments
Assignees
@alexandreLamarre
Labels
area/backup-recover kind/tech-debt Formerly issues labeled as ci-improvements, tasks, flaky tests, and post-release. priority/4 team/observability&backup the team that is responsible for monitoring/logging and BRO

Comments

@MKlimuszka
Copy link
Collaborator

MKlimuszka commented May 8, 2024 •
edited

Most of backup-restore was migrated to GHA with integration testing in this PR
rancher/backup-restore-operator#455

But testing for ARM64 support was not included. This ticket will fix that.
@MKlimuszka MKlimuszka added area/backup-recover kind/enhancement Issues that improve or augment existing functionality labels May 8, 2024
@MKlimuszka MKlimuszka added the team/observability&backup the team that is responsible for monitoring/logging and BRO label May 8, 2024
@MKlimuszka MKlimuszka changed the title ARM64 support for Github Actions in backup-restore-operator ARM64 integration testing in backup-restore-operator May 14, 2024
@MKlimuszka MKlimuszka added priority/4 kind/tech-debt Formerly issues labeled as ci-improvements, tasks, flaky tests, and post-release. and removed kind/enhancement Issues that improve or augment existing functionality labels May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexandreLamarre alexandreLamarre

Labels
area/backup-recover kind/tech-debt Formerly issues labeled as ci-improvements, tasks, flaky tests, and post-release. priority/4 team/observability&backup the team that is responsible for monitoring/logging and BRO
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MKlimuszka @alexandreLamarre