Skip to content

☂️ [GEP-33] Machine Image Capabilities #11301

@Roncossek

Description

@Roncossek

How to categorize this issue?

/area usability
/kind enhancement
/kind epic

What would you like to be added:

As described in GEP-33: Machine Image Capabilities gardener plans to introduce capabilities for machineType and machineImage in the Gardener CloudProfile to ensure only shoots with a matching set of capabilities on machine type and image will be admitted by Gardener. This will prevent the creation of incompatible worker pools on shoot creation and maintenance operations. It will also provide a mechanism to filter incompatible images for a machine type in the Gardener Dashboard. These mechanisms are prerequisites for other features, like worker nodes with SecureBoot #11898.

The Implementation can be described in several phases:

  1. Capability introduction to gardener/gardener:
  1. Capability introduction to gardener/gardener-extension-provider:
  1. Architecture Deprecation
  • mark architecture on machineImage and machineType as deprecated
  • remove architecture fields during cloudprofile, worker... reconciles
  1. Capability Enforcement
  • enforce capabilities usage in cloudprofile admission
  • mark capabilities as mandatory in all relevant APIs
  1. Architecture Removal
  • remove deprecated architecture api fields

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions