Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNSEntry creation failed .spec.resolveTargetsToAddresses: field not declared in schema #389

Closed
saifulhoque26 opened this issue Aug 30, 2024 · 4 comments
Labels
kind/bug Bug status/closed Issue is closed (either delivered or triaged)

Comments

@saifulhoque26
Copy link

saifulhoque26 commented Aug 30, 2024

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--

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:

@gardener-robot
Copy link

@saifulhoque26 You have mentioned internal references in the public. Please check.

@MartinWeindel
Copy link
Member

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:

# on the demo-gcp-dmi shoot
$ k get crd dnsentries.dns.gardener.cloud -oyaml --show-managed-fields
...
   - apiVersion: apiextensions.k8s.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:labels:
          f:app.kubernetes.io/instance: {}
          f:app.kubernetes.io/name: {}
          f:hc.sap.com/hc-provisioned: {}
      f:spec:
        f:conversion:
          f:strategy: {}
        f:group: {}
        f:names:
          f:kind: {}
          f:listKind: {}
          f:plural: {}
          f:shortNames: {}
          f:singular: {}
        f:scope: {}
    manager: kubectl
    operation: Apply
    time: "2024-08-30T11:32:53Z"
...

@MartinWeindel
Copy link
Member

@saifulhoque26 You have mentioned internal references in the public. Please check.

I have removed the internal references.

@MartinWeindel
Copy link
Member

/close as root cause not in dns-controller-manager

@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Bug status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

No branches or pull requests

3 participants