3 ms·

I still prefer to use kubernetes for this: https://dewyatt.github.io/articles/continuous-deployment-of-pastely-with-gke-kubernetes-ansible-jenkins https://dewya

• StavrosK 10y ago
  Is it worth it for just one server? Also, how do you handle the database? Do you put that in a container too?
  • dewyatt 10y ago
    For production, it may be. Kubernetes would handle updates in a safer way, avoiding service interruptions. Yes, the database can be in a container as well, with a persistent volume. It's not that much more complex than what you just went through.
    • StavrosK 10y ago
      Ah, that sounds good. How does Kubernetes handle updates safely? That requires pretty deep integration with the thing running in the container, doesn't it?
      • dewyatt 10y ago
        > How does Kubernetes handle updates safely? It supports rolling updates where one pod (this means container, usually) is updated at a time, with traffic being sent to other pods during that time. I think the best practice right now is to use a Deployment (alternatively you can initiate a rolling update manually). Using a deployment makes updates as simple as "kubectl patch ...". It does require a load balancer, which varies from platform to platform. In AWS, I assume it uses an ELB. On premise, you might use contrib/service-loadbalancer (haproxy).
        • StavrosK 10y ago
          Sounds ideal, thanks. I'm reading the docs right now, and it looks pretty simple, conceptually.