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

Send and event once an external resource is created and ready to use #385

Open
malachiobadeyi opened this issue Feb 24, 2023 · 2 comments
Open
Labels
enhancement New feature or request stale

Comments

@malachiobadeyi
Copy link

malachiobadeyi commented Feb 24, 2023

We provide a platform built on git-ops principles which allow developers to build and deploy to Kubernetes as well as create and configure external resources outside of the cluster. Crossplane plays a big part in that, however, one of the problems we have, is that Crossplane does not send a notification when an external resource such as RDS is actually created and ready for use. At the moment it just sends an event saying "Successfully requested creation of external resource". The resource can then take 10 - 20 minutes to actually become ready. In an ideal world, crossplane would emit an event when the resource is ready and we would then send a notification to our user. Because of this gap, we have had to create our own custom controller to watch the status of crossplane objects and create our own events when a resource is created and ready for use.
Can you add a feature to send events when a resource is created and ready for use.

@negz
Copy link
Member

negz commented Mar 13, 2023

It seems reasonable to send a Kubernetes event when a resource is ready. I'll see if anyone has bandwidth to take a look at your PR. Thanks!

Copy link

github-actions bot commented Sep 3, 2024

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants