Skip to content

CRD Source Status field is lacking  #2092

@sgreene570

Description

@sgreene570

The CRD source implementation only syncs observedGeneration to the CR's status field.

It would be useful if more information was propagated to the CRs status field when the resource was sync'd, such as whether or not ExternalDNS was successful in publishing the requested record to the relevant provider. Information available in the CRs status field could be consumed by other controller's, and potentially by cluster administrators.
For example, an administrator could check the status of their recently created DNSEndpoint CR instance to decide if they need to go review externalDNS logs and or metrics, in the event that syncing the source resource to the available provider(s) failed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/designCategorizes issue or PR as related to design.kind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions