Upgrade ExternalDNS

EKF 2.0.X uses ExternalDNS 0.12.2. This guide will walk you through upgrading ExternalDNS from version 0.7.6 to version 0.12.2.

Fast Forward

If you are not running on EKS or GKE, expand this box to fast-forward.

  1. Proceed to the What’s Next section.

Fast Forward

If you are upgrading from EKF 2.0 or later, expand this box to fast-forward.

  1. Proceed to the Verify section.

Procedure

  1. Go to your GitOps repository inside your rok-tools management environment:

    root@rok-tools:~# cd ~/ops/deployments

  2. Edit rok/external-dns/overlays/deploy/kustomization.yaml and ensure that you use the arrikto overlay:

    resources: - ../arrikto

    Note

    Overlays eks and gke have been removed.

  3. Commit your changes:

    root@rok-tools:~/ops/deployments# git commit -am "edns: Use arrikto overlay"

  4. Apply the manifests:

    root@rok-tools:~/ops/deployments# rok-deploy \ > --apply rok/external-dns/overlays/deploy \ > --force \ > --force-kinds Deployment

Verify

  1. Verify that the ExternalDNS deployment is up and running. Verify that field READY is 1/1:

    root@rok-tools:~# kubectl get deploy/external-dns NAME READY UP-TO-DATE AVAILABLE AGE external-dns 1/1 1 1 1m

Summary

You have successfully upgraded ExternalDNS.

What’s Next

The next step is to migrate the agent that forwards logs to Amazon CloudWatch Logs from FluentD to Fluent Bit.