Kubernetes Clusters

Shipa gives you the capability to bring together multiple Kubernetes clusters under one application layer. These clusters can be spread across multiple cloud providers and regions, such as Amazon EKS, Google GKE, etc.

This way, DevOps and platform engineering teams can quickly provide their developers with a Developer Platform with a common policy and governance engine across multiple clusters.

Frameworks and Kubernetes Clusters

For a cluster to be connected to Shipa, you will need to bind it to one or multiple frameworks. Frameworks are Shipa's policy engine that connects Shipa to your clusters and enforces defined policies when applications are deployed.

Note: It is imperative that the framework you are connecting the cluster to is not connected to any other cluster.

As a general guideline, when connecting clusters:

• A framework can belong to only one cluster
• One cluster can have many frameworks

The structure presented below is the one you should use when connecting clusters and frameworks.

Allowed Structure

Shipa frameworks are connected to a cluster namespace, so when you create a framework on Shipa and bind to a cluster, the framework translates to a namespace in the cluster. Every application then deployed through that framework will be deployed to that namespace.

As frameworks are tied to a namespace in your cluster, you can only bind a framework to a single cluster. You can create multiple frameworks and bind them to the same cluster. Still, in the end, a specific framework can only be bound to a single cluster.

The structure below should not be used because a framework can only belong to a single cluster.

📘

Managing Frameworks

For more information on creating and managing frameworks on Shipa, visit the link Framework Management