All records are already up to date, when they shouldn't be (Nginx example)

[wizbe97]

Hi guys, I am using Oracle Cloud and have been following many variations of the documentation around setting ExternalDNS up with Oracle Cloud Infrastructure.

I have managed to get it deployed, and it is returning the list of Private Zones that I have in my specified compartment. I created an example private zone, called external-dns.com and created the test Nginx service provided in the documentation. I have added log-level=debug

{"level":"debug","msg":"Matching zones against domain filters: []","time":"2024-07-03T18:38:22Z"} {"level":"debug","msg":"Matched \"external-dns.com\" (\"ocid1.dns-zone.xxxxxxxxxx\")","time":"2024-07-03T18:38:22Z"} {"level":"debug","msg":"Matched \"sn.internal.xxx.com\" (\"ocid1.dns-zone.xxxxxxxxxx\")","time":"2024-07-03T18:38:22Z"} {"level":"debug","msg":"Matched \"4.10.in-addr.arpa\" (\"ocid1.dns-zone.xxxxxxxxxx\")","time":"2024-07-03T18:38:22Z"} {"level":"info","msg":"All records are already up to date","time":"2024-07-03T18:38:42Z"}

I have also tried with setting the domain filter, and it's the exact same output except only matching against external-dns.com and filtering out the others.

The nginx.yaml file I deployed is below:

apiVersion: v1
kind: Service
metadata:
  name: nginx
  annotations:
    external-dns.alpha.kubernetes.io/hostname: nginx.external-dns.com
    service.beta.kubernetes.io/oci-load-balancer-internal: "true"
spec:
  type: LoadBalancer
  ports:
  - port: 80
    name: http
    targetPort: 80
  selector:
    app: nginx
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx
spec:
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - image: nginx
        name: nginx
        ports:
        - containerPort: 80
          name: http

And the output of kubectl get service -n external-dns is below:

NAME    TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
nginx   LoadBalancer   <CLUSTER-IP>   <RANDOM IP>   80:30277/TCP   16h

• obviously with the IP fields populated

I have deployed as per the example, with the manifest below:

apiVersion: v1
kind: ServiceAccount
metadata:
  name: external-dns
  namespace: external-dns
automountServiceAccountToken: true
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: external-dns-cluster-admin
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: external-dns
  namespace: external-dns
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: external-dns
  namespace: external-dns
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: external-dns
  template:
    metadata:
      labels:
        app: external-dns
    spec:
      serviceAccountName: external-dns
      containers:
      - name: external-dns
        image: registry.k8s.io/external-dns/external-dns:v0.14.2
        args:
        - --source=ingress
        - --provider=oci
        - --oci-zone-scope=PRIVATE
        - --policy=upsert-only
        - --txt-owner-id=nb-test
        - --log-level=debug
        - --log-format=json
        - --request-timeout=120s
        volumeMounts:
          - name: config
            mountPath: /etc/kubernetes/
            readOnly: true
        resources:
          requests:
            memory: "64Mi"
            cpu: "250m"
          limits:
            memory: "128Mi"
            cpu: "500m"
        securityContext:
          allowPrivilegeEscalation: false
          readOnlyRootFilesystem: true
          runAsNonRoot: true
          runAsUser: 1000
      volumes:
      - name: config
        secret:
          secretName: external-dns-config-2
      automountServiceAccountToken: true

If anyone knows why no private records get created within my zone, and instead just updates that all records are up to date I would be beyond appreciative of the help!