5 ms·

I have tried k3s and microk8s. Recently setup ArgoCD, connected to our GitLab instance. Tried both Traefik and Nginx Ingress controllers. And so on. And dokku

by pas 6y ago

I have tried k3s and microk8s. Recently setup ArgoCD, connected to our GitLab instance. Tried both Traefik and Nginx Ingress controllers. And so on. And dokku is better if you want a PaaS. There are probably dokku/heroku/deis-like things that run on kubernetes, but so far I haven't found 'it'. Of course you can just run dokku on any k8s distribution. You can even use k8s as a backend for dokku instead of docker - https://github.com/dokku/dokku-scheduler-kubernetes https://github.com/dokku/dokku-scheduler-kubernetes

SheinhardtWigCo 6y ago
dokku is fun to play with but I found it too buggy for use in production.
- josegonzalez 6y ago
  Would you mind pointing out a few things that were buggy about your experience with Dokku?
  - SheinhardtWigCo 6y ago
    Deploys occasionally failing and leaving behind a lock file, requiring manual intervention. Let’s Encrypt integration not working properly without dokku-event-listener, which must be built & installed from source and is basically undocumented. At the time I used it, blue/green deployments were not available. (I see this is now supported, great to see that.) To be fair, I didn’t report any of these issues, so I may have done something wrong or there may have been solutions that I missed. This was also 6+ months ago. I also think that with all the major cloud providers now supporting Kubernetes as a first-class primitive, and with there being an abundance of CI/CD tools that can trivially deploy to Kubernetes, the PaaS concept is no longer as attractive as it once was.
    - josegonzalez 6y ago
      > Deploys occasionally failing and leaving behind a lock file, requiring manual intervention. Interesting, would have been good to have these reported. Aside, unlocking an app should just be an `apps:unlock` call. > Let’s Encrypt integration not working properly without dokku-event-listener, which must be built & installed from source and is basically undocumented. That shouldn't be the case - the letsencrypt plugin was available long before the dokku-event-listener project was, and the latter has been built/released automatically since April[1] (though didn't have documentation on it's internals till recently, as that wasn't really necessary for end users as there isn't any configuration). > At the time I used it, blue/green deployments were not available. (I see this is now supported, great to see that.) Not sure what youre referencing here. We don't have anything specific for blue/green deployments, but we have had zero-downtime checks for a while. If you can point out to me where you found this (or what you were expecting) that would be awesome :) > To be fair, I didn’t report any of these issues, so I may have done something wrong or there may have been solutions that I missed. This was also 6+ months ago. Reporting issues is always appreciated as its almost certain there were bugs on our end, but it seems you've found your solution :) > I also think that with all the major cloud providers now supporting Kubernetes as a first-class primitive, and with there being an abundance of CI/CD tools that can trivially deploy to Kubernetes, the PaaS concept is no longer as attractive as it once was. I don't think this is quite true. Kubernetes is still a large system that doesn't come "batteries included", and every setup is at least subtly different from the next. I think a large number of teams spend a disproportionate amount of time configuring their preferred toolchain - and then maintaining it - once you get to a certain scale. Additionally, a kubernetes manifest is much lower-level than is necessary for the general app developer who just wants to get things done. I'm personally hoping that Kubernetes distributions begin to mature more (Tanzu and Openshift are examples, but not the only ones) so that folks start worrying less about operating and maintaining clusters and more on either the underlying infra or the end developer experience.
alexellisuk 6y ago
I am biased as the original creator, but take a look at OpenFaaS -> https://docs.openfaas.com https://docs.openfaas.com - there are a few things that people may enjoy who would turn to Dokku otherwise.

by pas 6y ago

SheinhardtWigCo 6y ago

dokku is fun to play with but I found it too buggy for use in production.

josegonzalez 6y ago
Would you mind pointing out a few things that were buggy about your experience with Dokku?
- SheinhardtWigCo 6y ago
  Deploys occasionally failing and leaving behind a lock file, requiring manual intervention. Let’s Encrypt integration not working properly without dokku-event-listener, which must be built & installed from source and is basically undocumented. At the time I used it, blue/green deployments were not available. (I see this is now supported, great to see that.) To be fair, I didn’t report any of these issues, so I may have done something wrong or there may have been solutions that I missed. This was also 6+ months ago. I also think that with all the major cloud providers now supporting Kubernetes as a first-class primitive, and with there being an abundance of CI/CD tools that can trivially deploy to Kubernetes, the PaaS concept is no longer as attractive as it once was.
  - josegonzalez 6y ago
    > Deploys occasionally failing and leaving behind a lock file, requiring manual intervention. Interesting, would have been good to have these reported. Aside, unlocking an app should just be an `apps:unlock` call. > Let’s Encrypt integration not working properly without dokku-event-listener, which must be built & installed from source and is basically undocumented. That shouldn't be the case - the letsencrypt plugin was available long before the dokku-event-listener project was, and the latter has been built/released automatically since April[1] (though didn't have documentation on it's internals till recently, as that wasn't really necessary for end users as there isn't any configuration). > At the time I used it, blue/green deployments were not available. (I see this is now supported, great to see that.) Not sure what youre referencing here. We don't have anything specific for blue/green deployments, but we have had zero-downtime checks for a while. If you can point out to me where you found this (or what you were expecting) that would be awesome :) > To be fair, I didn’t report any of these issues, so I may have done something wrong or there may have been solutions that I missed. This was also 6+ months ago. Reporting issues is always appreciated as its almost certain there were bugs on our end, but it seems you've found your solution :) > I also think that with all the major cloud providers now supporting Kubernetes as a first-class primitive, and with there being an abundance of CI/CD tools that can trivially deploy to Kubernetes, the PaaS concept is no longer as attractive as it once was. I don't think this is quite true. Kubernetes is still a large system that doesn't come "batteries included", and every setup is at least subtly different from the next. I think a large number of teams spend a disproportionate amount of time configuring their preferred toolchain - and then maintaining it - once you get to a certain scale. Additionally, a kubernetes manifest is much lower-level than is necessary for the general app developer who just wants to get things done. I'm personally hoping that Kubernetes distributions begin to mature more (Tanzu and Openshift are examples, but not the only ones) so that folks start worrying less about operating and maintaining clusters and more on either the underlying infra or the end developer experience.

alexellisuk 6y ago

I am biased as the original creator, but take a look at OpenFaaS -> https://docs.openfaas.com https://docs.openfaas.com - there are a few things that people may enjoy who would turn to Dokku otherwise.