Support Azure Packer plugin 2.x
mboersma opened this issue · 5 comments
Is your feature request related to a problem? Please describe.
In #1253 we were caught unaware by breaking changes to the Azure Packer plugin when running the pipeline scripts. To fix things, we pinned the plugin to a pre-2.0 version (currently that means v1.4.5).
Describe the solution you'd like
image-builder and the pipeline scripts should be updated to support Azure Packer plugin 2.0.0. This may require several changes, in particular because the SAS URLs that we use to create Managed Images are no longer provided by the plugin.
Describe alternatives you've considered
- We could stay pinned to the pre-2.0 version, but that's not a long-term solution.
Additional context
/kind feature
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale
- Close this issue with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale
- Close this issue with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The blocker for this is that 2.x drops SAS token support, but we want to stop using SAS tokens for publishing regardless as they've a security risk vector.
/assign