Currently externaltools is deployed manually with RPM. This is a manual process and involves packaging gem dependencies.

We do have a caasp cluster running internally which already hosts and

It would simplify development on externaltools a lot if we could switch it to be automatically deployed in CaaSP.


Example gitlab CI pipeline with caasp deployment (.gitlab-ci.yml, geekos-frontend.yml)


  • okurz
    8 months ago by okurz | Reply

    Hm, sounds interesting. I wonder in general, how does this simplify deployment? Isn't an automatic update of RPM very easy or what is the current approach used?

    • cschum
      8 months ago by cschum | Reply

      RPMs are not a natural way to package Rails applications. Containers work better there. And with Kubernetes you also get the necessary configuration of the infrastructure around the application.

      Even simpler would be to use a PaaS system. But as an exercise to learn how to do it with Kubernetes this is an interesting project.

  • kiall
    8 months ago by kiall | Reply

    Re the .gitlab-ci.yml you gave - you could also use the new GitLab Kubernetes integration with CaaSP. This can do some cool stuff, like review apps (Deploy a full instance of the stack for each PR, destroying it again when closed or merged)... Check the products "Operations -> Kubernetes" section at the side to add connection details for your cluster.

Similar Projects

move concourse instance from bare-metal to caasp production instance by m_meister

Right now our concourse instance http://salzbre...

Learn more about container from SUSE CaaS Platform by xguo

How to deploy container - Docker based on SUSE ...

Create a Kubernetes API client in Rust by robdaemon

Rust is a systems programming language from Moz...

Spring cleaning: by farahschueller

  • Make UI pretty
  • Write better tests
  • Refac...

Playing with OpenFaaS: a Serverless Framework for Docker and Kubernetes by pgeorgiadis

OpenFaaS - Functions as a Service

Get fa...