Closed mboersma closed 1 year ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
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 and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Hi @mboersma, gen2 reference images are still missing. Do you know why?
Hi @ffais! I guess we never really committed to switching to -gen2
images by default, and this work item fell by the wayside.
The reference images are primarily for tests, and we try to keep the matrix of (k8s version * OS distro) small to keep costs down. There hasn't been a business justification that drove us to complete this switch.
Our strong recommendation if you're using CAPZ is to build and host your own images, because we may not publish every variation you need, and because we don't patch them with security fixes or other updates.
Also note that CAPZ switched from defaulting to Azure Marketplace to a community gallery in the main
branch.
Thanks for the clarification, everything is clearer now.
/kind feature
Describe the solution you'd like
The CAPZ reference images use Azure generation 2 VMs by default.
Describe alternatives you've considered
We could leave gen1 as the default. We could publish both gen1 and gen2 reference images.
Additional context
See also #1003 and https://github.com/kubernetes-sigs/image-builder/pull/878#discussion_r866291520