Services and requirements

Services

We have several service offerings that you can use in addition to the Redpill Linpro Container Platform. First you will get a set of VM's, minimum two to serve as your hosts for container workloads.

1 - Gitlab ) If you need a version control system, we have a gitlab instance that our customers can make use of. It also has gitlab runners for all your pipeline needs.
2 - ArgoCD ) If you need a "Continuous Delivery" solution, we provide ArgoCD for our customers. This makes it so that your kubernetes objects can be automatically managed and applied.
3 - Logging ) If you need to have a logging solution based on OpenSearch, we can provide logshipping inside the platform. We also have solutions that ingests, search and visualize this log data. Sending your applications stdout to a Index / search as a service instance will make sure you have persistency of these logs since this otherwise will disappear when your pod restarts.
4 - Authentication ) If you need an Identity and Access Management (IAM) solution, we can provide this with our managed keycloak service.
5 - Password sharing ) If you need a solution to share passwords, we can provide this with our managed passwordpusher service.
6 - Database-as-a-service) Redpill Linpro offers many different flavours of opensource database solutions.
7 - Data storage and persistency ) The container platform can also provide block storage volumes or use "situla" which is our s3-bucket solution.
8 - Dedicated ingress ) We can offer dedicated ingress(aka router) pods with a dedicated public ip for incoming traffic if desired. Customers that do not use this service, use the shared ingress controller with 1 shared public ip in our platform. By default, dedicated ingress controllers only offer the usual ports 80/443 TCP, if for some reason other ports/protocols are needed, please contact us.

Requirements

The platform is multi-tenant, meaning it uses a shared controlplane where several customers have their own dedicated worker nodes. If a multi-tenant platform is not the right fit, we can set up a dedicated platform for you.

1) Your applications(containers) need to be configured to be High-Available. Sudden maintenance/reboots/other events should not lead to downtime of your application. This is true for all Kubernetes clusters, but is especially important to be aware of when running on a multi-tenant platform.

2) If you have a need to install your own operators or need cluster wide permissions through cluster roles/rolebindings, a multi-tenant platform may not be a good fit for you. Cluster wide permissions are not allowed.

3) We do not restore single kubernetes objects. We advise our customers to use GitOps tools like ArgoCD to manage their Kubernetes objects. As long everything is stored in git(version control), "restore" can happen through this. Note that we can offer an encrypted Kubernetes-secret solution so that you can store it safely in your git repositories.

4) Be sure to have a backup plan for your persistent data created by Kubernetes objects.