You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix hub webhook DRA version gating to skip cluster version check
The ManagedClusterModule webhook on the hub was incorrectly using the
hub cluster's Kubernetes version to gate DRA usage.
Since the hub cannot know the target managed cluster's version, this could wrongly reject
valid specs or accept invalid ones.
Fix by passing an empty KubeVersion to the hub validator and skipping
the version gate in validateDRA when the version is zero. Field format
validation (driverName, deviceClasses) still runs unconditionally. The
spoke cluster's own Module webhook enforces the version requirement.
Also moves DiscoverKubeVersion inside the enableModule branch so that
webhook modes that don't need cluster version (namespace, preflight)
no longer require ClusterVersion API access.
0 commit comments