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
What happened:
Error from server: failed to create typed patch object (haproxy-ingress/haproxy-nlb-service; dns.gardener.cloud/v1alpha1, Kind=DNSEntry): .spec.resolveTargetsToAddresses: field not declared in schema
What you expected to happen:
Gardener accepted our feature request: #371
Error from server: failed to create typed patch object (haproxy-ingress/haproxy-nlb-service; dns.gardener.cloud/v1alpha1, Kind=DNSEntry): .spec.resolveTargetsToAddresses: field not declared in schema
How to reproduce it (as minimally and precisely as possible):
Now:
--deleted internal references--
Anything else we need to know:
Environment:
The text was updated successfully, but these errors were encountered:
Cannot reproduce the issue. Looking on the demo-gcp-dmi shoot cluster it looks as if the CRD was overwritten with kubectl apply, as the following output suggests:
What happened:
Error from server: failed to create typed patch object (haproxy-ingress/haproxy-nlb-service; dns.gardener.cloud/v1alpha1, Kind=DNSEntry): .spec.resolveTargetsToAddresses: field not declared in schema
What you expected to happen:
Gardener accepted our feature request: #371
The PR with the feature is merged:
#377
As per the documentation, we can create an A record with a single target
The version gardener-extension-shoot-dns-service v1.49.0 contains the fix.
--deleted internal references--
How to reproduce it (as minimally and precisely as possible):
Now:
--deleted internal references--
Anything else we need to know:
Environment:
The text was updated successfully, but these errors were encountered: