-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #15 from linode/sr-fix-rebranding
- Loading branch information
Showing
165 changed files
with
108 additions
and
1,175 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,33 +1,33 @@ | ||
# Otomi Catalog quick starts | ||
# Application Platform for LKE Catalog quick starts | ||
|
||
This repository contains a set of Helm charts that will be made available as quick starts to all Teams in the Otomi Catalog. | ||
This repository contains a set of Helm charts that will be made available as quick starts to all Teams in the Application Platform for LKE Catalog. | ||
|
||
The following charts are added to the Catalog: | ||
The following Helm charts are added to the Catalog: | ||
|
||
## otomi-quickstart-k8s-deployment | ||
## Quick start for a regular K8s deployment | ||
|
||
The `otomi-quickstart-k8s-deployment` Helm chart can be used to create a Kubernetes `Deployment` (to deploy a single image), a `Service` and a `ServiceAccount`. Optionally a `HorizontalPodAutoscaler`, a Prometheus `ServiceMonitor` and a `Configmap` can be created. | ||
The `quickstart-k8s-deployment` Helm chart can be used to create a Kubernetes `Deployment` (to deploy a single image), a `Service` and a `ServiceAccount`. Optionally a `HorizontalPodAutoscaler`, a Prometheus `ServiceMonitor` and a `Configmap` can be created. | ||
|
||
## otomi-quickstart-k8s-deployment-otel | ||
## Quick start for creating a K8s Deployment with Open Telemetry Instrumentation | ||
|
||
The `otomi-quickstart-k8s-deployment-otel` Helm chart can be used to create a Kubernetes `Deployment` (to deploy a single image), a `Service`, a `ServiceAccount`, an `OpenTelemetryCollector` and an `Instrumentation`. Optionally a `HorizontalPodAutoscaler`, a Prometheus `ServiceMonitor` and a `Configmap` can be created. | ||
The `quickstart-k8s-deployment-otel` Helm chart can be used to create a Kubernetes `Deployment` (to deploy a single image), a `Service`, a `ServiceAccount`, an `OpenTelemetryCollector` and an `Instrumentation`. Optionally a `HorizontalPodAutoscaler`, a Prometheus `ServiceMonitor` and a `Configmap` can be created. | ||
|
||
## otomi-quickstart-k8s-deployments-canary | ||
## Quick start for creating 2 K8s deployments with one service for canary and blue/green | ||
|
||
The `otomi-quickstart-k8s-deployments-canary` Helm chart can be used to create 2 Kubernetes `Deployments` (to deploy 2 versions of an image), a `Service` and a `ServiceAccount`. Optionally a `HorizontalPodAutoscaler`, a Prometheus `ServiceMonitor` and a `Configmap` (for each version) can be created. | ||
The `quickstart-k8s-deployments-canary` Helm chart can be used to create 2 Kubernetes `Deployments` (to deploy 2 versions of an image), a `Service` and a `ServiceAccount`. Optionally a `HorizontalPodAutoscaler`, a Prometheus `ServiceMonitor` and a `Configmap` (for each version) can be created. | ||
|
||
## otomi-quickstart-knative-service | ||
## Quick start for creating a Knative Service | ||
|
||
The `otomi-quickstart-knative-service` Helm chart can be used to create a Knative `Service` (to deploy a single image), a `Service` and a `ServiceAccount`. Optionally a Prometheus `ServiceMonitor` can be created. | ||
The `quickstart-knative-service` Helm chart can be used to create a Knative `Service` (to deploy a single image), a `Service` and a `ServiceAccount`. Optionally a Prometheus `ServiceMonitor` can be created. | ||
|
||
## Otomi quick start for creating a PostgreSQL cluster | ||
## Quick start for creating a PostgreSQL cluster | ||
|
||
The `otomi-quickstart-postgresql` Helm chart can be used to create a cloudnativepg PostgreSQL `Cluster`. Optionally a Prometheus `PodMonitor` and a `Configmap` (for adding a postgresql dashboard to Grafana) can be created. | ||
The `quickstart-postgresql` Helm chart can be used to create a cloudnativepg PostgreSQL `Cluster`. Optionally a Prometheus `PodMonitor` and a `Configmap` (for adding a postgresql dashboard to Grafana) can be created. | ||
|
||
## Otomi quick start for creating a Redis master-replica cluster | ||
## Quick start for creating a Redis master-replica cluster | ||
|
||
The `otomi-quickstart-redis` Helm chart can be used to create a Redis master-replica cluster. | ||
The `quickstart-redis` Helm chart can be used to create a Redis master-replica cluster. | ||
|
||
## Otomi quick start for creating a RabbitMQ cluster | ||
## Quick start for creating a RabbitMQ cluster | ||
|
||
The `otomi-quickstart-rabbitmq` Helm chart can be used to create a RabbitMQ `cluster` with `queues` and `policies`. | ||
The `quickstart-rabbitmq` Helm chart can be used to create a RabbitMQ `cluster` with `queues` and `policies`. |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.