We are going to deploy an nginx app with 2 versions, blue and green. We will mount the index.html to the deployments to show which version we are looking at. Then we will create a service with labels pointing to both versions, and control the flow of traffic between the blue version to the green version through pod replicas in the deployment.
Create the demo namespace
k create ns demo
k config set-context $(k config current-context) --namespace=demo
The preceding steps have been tested on an OSD cluster running OCP 4.10.3
The Kong Operator is a helm operator. The values defined in the operator instance are turned into helm values. All possible fields for the operator can be found here and are the same as the helm values for this operator which can be found here.
We will Deploy the Kong Gateway using the Kong Operator and deploy the Control Plane and Data Plane in two distinct namespaces.
TOC
During this guide, we will deploy the blue app that produces metrics. We will scrape the metrics with Prometheus, define alerts, send alerts to pagerduty, stream metrics to a remote endpoints using RemoteWrite and create a custom Grafana Dashboard for our app.
| package main | |
| import ( | |
| "context" | |
| "encoding/json" | |
| "fmt" | |
| "io/ioutil" | |
| "log" | |
| "net/http" | |
| "os" |
| apiVersion: charts.starburstdata.com/v1alpha1 | |
| kind: StarburstEnterprise | |
| metadata: | |
| name: starburstenterprise-sample | |
| namespace: openshift-operators | |
| spec: | |
| additionalVolumes: [] | |
| cache: | |
| diskUsagePercentage: 80 | |
| enabled: false |
This demo has been tested in OCP 4.10.5
TOC