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

Migrate Velero to Workload Identities #1201

Closed
4 tasks done
Tracked by #1281
sveinpj opened this issue Feb 15, 2024 · 0 comments
Closed
4 tasks done
Tracked by #1281

Migrate Velero to Workload Identities #1201

sveinpj opened this issue Feb 15, 2024 · 0 comments
Assignees
@sveinpj
Labels
security Issues related to security improvements

Comments

@sveinpj
Copy link
Contributor

sveinpj commented Feb 15, 2024 •
edited
Loading

  • Add variable and imagepolicy in flux to manage version of velero/velero-plugin-for-microsoft-azure
  • Enable workload identity (see links below)
  • Update config for BackupStorageLocation to use workload identity
  • Cleanup / Script

Links:
https://www.slideshare.net/riderkubota/aks-backup-with-velero-and-workload-identities
vmware-tanzu/velero#5116 (comment)
https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/blob/main/README.md#option-2-use-azure-ad-workload-identity
@sveinpj sveinpj self-assigned this Feb 15, 2024
@sveinpj sveinpj added the security Issues related to security improvements label Feb 15, 2024
@emirgens emirgens mentioned this issue Feb 15, 2024
Closed
8 tasks
@emirgens emirgens added the refinement needed Issues marked for refinement label Feb 26, 2024
@emirgens emirgens removed the refinement needed Issues marked for refinement label Apr 2, 2024
@emirgens emirgens mentioned this issue Apr 10, 2024
Open
2 tasks
@sveinpj sveinpj closed this as completed May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sveinpj sveinpj

Labels
security Issues related to security improvements
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@emirgens @nilsgstrabo @sveinpj