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.

Sign up for GitHub

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

Jump to bottom

Config Connector should output kstatus-compatible resource status #410

Closed
toumorokoshi opened this issue Feb 24, 2021 · 4 comments
Closed

Config Connector should output kstatus-compatible resource status #410

toumorokoshi opened this issue Feb 24, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@toumorokoshi
Copy link
Contributor

Today, Config Connector does not include some of the fields and behavior to be compatible with kstatus, which is becoming a standard for querying resource status.

Some specific requirements:
@toumorokoshi toumorokoshi added the enhancement New feature or request label Feb 24, 2021
@toumorokoshi
Copy link
Contributor Author

Update: this is is currently being investigate, to be delivered near the end of Q1 (March / April)

@toumorokoshi toumorokoshi mentioned this issue Feb 24, 2021
Open
@snuggie12
Copy link

@toumorokoshi Do you want additonal issues for other resources? I experienced this on a GCS bucket recently.

@toumorokoshi
Copy link
Contributor Author

toumorokoshi commented Mar 25, 2021 via email

@toumorokoshi
Copy link
Contributor Author

As an update: observedGeneration is now supported by KCC. I'll close this ticket as #387 is tracking the other issue (ready state flapping, which is not specific to kstatus)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@toumorokoshi @snuggie12