Uploaded image for project: 'Horizon Stream'
  1. Horizon Stream
  2. HS-4

Self-hosted deployment in Kubernetes for end users and developers



    • Epic
    • Status: To Do (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Self-hosted deployment in Kubernetes for end users and developers


      The self-hosted version of Horizon Stream is deployed in Kubernetes. It allows us and our users to deploy private/public cloud environments and is vendor-agnostic. To deploy all the components and services for an end-user there are several possibilities to deploy workloads in Kubernetes:

      1. Using Kustomize and kubectl to deploy from a set of yaml files to configure the deployment
      2. Using a Helm chart as a more formalized and versioned deployment description
      3. Using an operator for a full-featured automated deployment

      When we develop the tool we want a) to use the same methods for deployment and b) we want to have quick feedback cycles to see the result of code changes. The main goal here for developers is to have a way to quickly build containers from the source code, deploy them in a local k8s environment and have access to logs for step-by-step debugging.

      Inspiration: https://build.diligent.com/local-development-in-kubernetes-with-tilt-and-rancher-desktop-7704f4e7ea12

      The components are identified and described in




            Unassigned Unassigned
            indigo Ronny Trommer
            0 Vote for this issue
            1 Start watching this issue