address yet another comment

gardener · Jan 17, 2025 · 18fa5e3 · 18fa5e3
1 parent d4cf901
commit 18fa5e3
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/docs/operations/operations.md b/docs/operations/operations.md
@@ -231,7 +231,8 @@ After the service principal secret has been rotated and the corresponding secret
 Changes to the `Shoot` worker-pools are applied in-place where possible. In case this is not possible a rolling update of the workers will be performed to apply the new configuration, as outlined in [the Gardener documentation](https://github.com/gardener/gardener/blob/master/docs/usage/shoot-operations/shoot_updates.md#in-place-vs-rolling-updates). The exact fields that trigger this behaviour depend on whether the feature gate `NewWorkerPoolHash` is enabled. If it is not enabled, the fields mentioned in the [Gardener doc](https://github.com/gardener/gardener/blob/master/docs/usage/shoot-operations/shoot_updates.md#rolling-update-triggers) are used, with a few additions:
 
 - `.spec.provider.infrastructureConfig.identity`
-- `.spec.provider.workers[].dataVolumes[].size` and `.spec.provider.workers[].dataVolumes[].type` (only the affected worker pool)
+- `.spec.provider.workers[].dataVolumes[].size` (only the affected worker pool)
+- `.spec.provider.workers[].dataVolumes[].type` (only the affected worker pool)
 
 If the feature gate _is_ enabled, instead of the complete provider config only the fields explicitly mentioned above are used, with the addition of