John Gardiner Myers

Perhaps what is needed is a script that takes the cluster name and generates the policy with permissions scoped to that cluster?

Instead of documentation, perhaps we could provide a tool which takes a cluster name and generates a policy scoped to that cluster?

/remove-lifecycle stale

Per office hours, we want this to go into toolbox.

This is well within CCM's bailiwick. It's a straightforward, simple reconciliation loop copying any IPv6 prefix assignment from the cloud API to the Kubernetes Node object.

/lgtm /assign @seanmalloy

/approve On another topic, I was wondering if it would make sense to move the aws-sd registry logic into the provider. That registry can't be used with any other provider...

/test pull-external-dns-lint /test pull-external-dns-unit-test

/label tide/merge-method-squash

External-dns represents ALIAS records of type A to the planner as `Endpoint`s of type CNAME and a `ProviderSpecific` attribute with key `alias` and value `true`. So it is an expected...