-
Notifications
You must be signed in to change notification settings - Fork 67
Cannot deploy #25
Comments
I get this too, a shame, I'll have to keep looking... Connecting to Kubernetes 1.9 cluster. |
I tried it a few different way including bypassing the run.sh and moving all the the contents there to the Dockerfile. Still no luck :-( |
Anyone get any progress with this? |
I personally moved on from this. I built my own and will be opening up my work to the public on Friday |
Does anyone get some luck about this issue? @markyjackson-taulia could you share your work? thx |
@fulvi0 my work is here: https://github.com/draios/sysdigcloud-kubernetes |
Check this PR, it fixes this issue. |
Check this #23 |
Also while I was experiencing with redis, a master pod with N amount of slaves, with persistent volume, and and redis-persistence enabled is almost high-available. Even if master is gone, kubernetes just launches another one in split second, and redis master hooks back to persistent storage. All it happens under 3-5 seconds, and if you are OK with that, you will not even need that complex custom configuration of sentinel. And while master is down, you can still read from slaves. |
Using a sentinel is a good thing here |
Made my day! It works from the beginning. Maybe I take a deeper look next time. Cheers |
minikube version: v0.27.0
OS - Ubuntu 16.04
The text was updated successfully, but these errors were encountered: