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

Show Docker Image Tag on Deployments #135

Closed
blancsys opened this issue Jul 28, 2019 · 2 comments · Fixed by #158
Closed

Show Docker Image Tag on Deployments #135

blancsys opened this issue Jul 28, 2019 · 2 comments · Fixed by #158
Milestone

Comments

@blancsys
Copy link

@blancsys blancsys commented Jul 28, 2019

Hi, this bot looks awesome, it has a lot of great features, good work.

I', trying to find a bot that is able to notify about the upgrades of docker images.

For example, let's suppose that we are running a k8s Deployment that uses using a Docker image tagged as "myapp:v0.1.0" Then, we upgrade that deployment to a newer image ("myapp:v0.2.0"). I would like to see a bot message on Slack showing that the deployment is now running the new Docker image version ("myapp:v.0.2.0")

I took a look at the screenshots at https://www.botkube.io/examples/ but I don't see that kind of information there. Is it supported right now? Is it in the roadmap?

Thank you very much!

@codenio
Copy link
Contributor

@codenio codenio commented Jul 29, 2019

Hi @blancsys, FYI we get a generic notifications on update events (Resource Updated), which has no info about the actual change happening in under the hood. i.e, it isn't supported right now.

However Feature Request #131 covers this and it is in the roadmap (Comming soon).

@sanketsudake sanketsudake added this to the v0.9.0 milestone Jul 29, 2019
@blancsys
Copy link
Author

@blancsys blancsys commented Jul 29, 2019

Thanks for your info! Let's wait for v0.9.0 then

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

Successfully merging a pull request may close this issue.

3 participants