-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Getting Started deployment is broken (missing redis when using the guestbook) #126
Comments
Thanks for opening this @fungiboletus! Agreed that the sample app should be connected to redis and work as expected. We could use the kubernetes/example manifest shown here. Unfortunately, the app is broken as I discovered/mentioned in this issue. We could maybe think about hosting our own frontend image to help resolve this and get the example fixed sooner if there isn't a new image made available soon. |
I also ran into this issue, is there another example here that would work? |
@jamesdesmond If you are looking for a working guestbook app synced by Argo CD, you could use the following repo/commands:
It's my own personal repository with my own guestbook image on dockerhub. In this repository, the app deployed is just the UI at the moment. |
Really! This makes me worry about using this product within a commercial production environment. The Demo is broken and doesn't run?? If this CD tool is so good, how can it not also deploy the Redis Service to allow the demo to run.. This is scary that this is over a year old and oneone has reviewed this? |
For some reason this post became a honeypot for spam. Apologies for all the delete messages. |
This thread became just spam bots, so locking for now. Feel free to open another issue with the same description. |
Hi,
I'm following the "Getting Started" ArgoCD documentation. I successfully deployed the guestbook, but you may want to know that the deployment is broken. Redis is missing.
I get the following PHP exception when I post a message:
It's not critical to understand ArgoCD, but I think it would look better if the first deployment you do using ArgoCD works 🙂
The text was updated successfully, but these errors were encountered: