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

Enhance Status Reporting for Tratteria Custom Resources #45

Open
kchiranjewee63 opened this issue Aug 7, 2024 · 0 comments
Open

Enhance Status Reporting for Tratteria Custom Resources #45

kchiranjewee63 opened this issue Aug 7, 2024 · 0 comments

Comments

@kchiranjewee63
Copy link
Member

kchiranjewee63 commented Aug 7, 2024

Current Behavior

Tratteria CRDs currently provide limited status information. For example, TraTs only show two states: PENDING and DONE. This minimal status reporting limits visibility into the resource's lifecycle and potential issues.

Desired Behavior

Implement a more elaborate and informative status reporting system for Tratteria CRDs, providing detailed information about the resource's state, progress, and any issues encountered.

Example of Current Status (TraT)

Status:
  Generation Applied:    true
  Retries:               0
  Status:                DONE
  Verification Applied:  true

Some Potential Status Fields (non-exhaustive)

  • observedGeneration: The latest generation observed by the controller.
  • phase: A high-level summary of the resource's current state (e.g., "Pending", "PartiallyApplied", "Applied")
  • components: Status of individual components or stages, e.g.:
    • verification: Status of the verification rule propagation (e.g., "Pending", "PartiallyApplied", "Applied")
    • generation: Status of the generation rule propagation (e.g., "Pending", "PartiallyApplied", "Applied")
  • lastSuccessfulUpdate: Timestamp of the last successful update
  • errors: An array of any errors encountered during processing

Discussion Points

  • What additional status fields would be useful for operators and developers?
  • Should we implement a condition-based status similar to other Kubernetes resources?

Affected Resources

  • TraT
  • TratteriaConfig
  • TraTExclusion

Related Issues

#64: TraT fails silently without reporting any status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant