opdev / l5-operator-demo Goto Github PK

provision certificates form cert manager operator
we need one for ingress & routes at the very least

ex: update status when app is being upgraded

nice to have feature since we will probably be restoring only if the app is already not working

https://github.com/makon57/bestie

install postgres operator / crunchy
read / familiarize with operator functionality

should we record the app version associated with a particular backup

based on https://github.com/rocrisp/go-operator-demo

During our last tests of bestie deployment into a Kind instance, we noticed that Bestie Controller is getting inside a loop till the pods get Running.

I've attached an image to help with the clarification.

when we delete, update bestie we don't want to seed data again because it will fail.

Initial notes are here https://docs.google.com/document/d/1gNa2NQzlsHDdNHBYPczCytkuokEzBCFKjlxM12X5cdk/edit#heading=h.exq8debhhixv

we need an official documentation on the repo for that.

• ensure the secret is present
• make sure the deployment is referencing it

Waiting to update to version 1.16.0 of operator-sdk to further review what is new.

This is a good example: https://github.com/opdev/demo-webhook-receiver-alertmanager

this can be with some app downtime
making restores without downtime will be addressed in #41

the status field of the cr should show the version of the application being managed

https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#scaling-on-custom-metrics

for ssl certs related to #18

OCO is a good example: https://github.com/redhat-openshift-ecosystem/operator-certification-operator

• add as dependency
• create cr for creating a postgres instance
• create cr for creating a db
• ensure that the app can talk to it
• create cr for backups

I get the following error when I apply the CR.
roc apply -f config/samples/pets_v1_bestie.yaml
Warning: resource besties/bestie is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by oc apply. oc apply should only be used on resources created declaratively by either oc create --save-config or oc apply. The missing annotation will be patched automatically.
bestie.pets.bestie.com/bestie configured

• ensure install install works
• ensure upgrade works
• ensure backups
• explore app to determine what insights (level 4) to expose
• what actions to take based on the above insights (level 5)

It may be expected that the operator presentation is tailored for vanilla kubernetes
for example: support both ingress & routes

Ex. user needs to install their own Postgres cluster

Tell the user to install a certificate manager.

how long it takes to get 200 ok from /something in the app
level 5 would be scaling based on this

Document that an ingress controller is needed for the application to work. If running on a Kubernetes cluster, an ingress controller must be pre-installed and running in order for the ingress resource to work.

Future implementation: install/integrate nginx-ingress operator.

bestie app stores images in s3

options to be explored

Add support for the Operator in GUI
Need a logo and the font size needs update, etc.

push images to opdev

seems like a manual process unsure if there is anything to gain specifically right now but eventually needs to be done

use the latest operator sdk to scaffold a project