[gardener/gardener-extension-shoot-lakom-service]

⚠️ Breaking Changes

[OPERATOR] extension-shoot-lakom-service no longer supports Shoots with Кubernetes version < 1.22. by @shafeeqes [#23]
[OPERATOR] The deprecated network policy annotations and kube-apiserver deployment webhook have been removed, thus this extension is not compatible with gardener<v1.71.0.
- ⚠️ make sure gardener is updated to version v1.71.0 or newer before to install this version of the extension. by @vpnachev [#18]

[OPERATOR] The seed bootstrap controller is now installing a stand-alone instance of the lakom admission controller in the kube-system namespace of the seed cluster instead of running inside the extension controller manager. This is done to avoid dead locks with other admission controllers, like the gardener-resource-manager that targets the pods in the extensions namespaces. by @vpnachev [#19]
[OPERATOR] This extension again removes the health checks for the shooт managed resource. by @vpnachev [#17]
[OPERATOR] The binaries of this extension are now build with golang 1.20.6. by @vpnachev [#27]

🏃 Others

[OPERATOR] The binaries are now build with golang 1.20.4. (gardener/gardener-extension-shoot-lakom-service#3, @vpnachev)

[OPERATOR] Lakom admission controller now have access to the metadata server also when gardener's feature gate FullNetworkPoliciesInRuntimeCluster is enabled. (gardener/gardener-extension-shoot-lakom-service#12, @vpnachev)

[OPERATOR] The following dependencies have been updated: (gardener/gardener-extension-shoot-lakom-service#15, @vpnachev)

[OPERATOR] This extension is now also doing health check on the managed resource installing the resources in the shoot cluster. (gardener/gardener-extension-shoot-lakom-service#16, @vpnachev)