glasskube / operator Goto Github PK

The annotation processor provided by the JOSDK can be removed, as the generated resources are not used outside of io.javaoperatorsdk.operator.config.runtime.DefaultConfigurationService (which we do not use).

In order to install the Glasskube Operator it makes to pull the image from Docker hub:

https://hub.docker.com/repository/docker/glasskube/operator

• documentation should sit inside the kotlin file
• documentation should generate html

• Open a discussion with first version
• Link the discussion in a readme section

• Initial Setup (user creation)
• Database migrations

Depends on:

• operator-framework/java-operator-sdk#167

Integrating with OLM would allow us to publish our operator to: https://operatorhub.io/

As a user I want peristant prometheus data and a public ingress for a persitant grafana.

I suggest a data retention of 6 months.

Optionally we can research if http basic auth is possible.

On hetznercloud we want support ssl termination on their managed loadbalancers for high availablity setups.

Find related docs here: https://github.com/hetznercloud/hcloud-cloud-controller-manager/blob/main/docs/load_balancers.md

• #15
• Support secret generation
• #20
• Matomo <> MariaDB connection
• #23
• Create ingress
• #24

• Configure license
• Share repository in MTL channels
• Setup milestone plan

Release notes: https://github.com/go-gitea/gitea/releases/tag/v1.19.0

Currently we use a custom deploy.sh script that installs the operator, its resources and depended sub charts.

We created the repository: https://github.com/glasskube/charts.glasskube.eu which should received the released charts, which are maintained in this repository.

Additionally we want to publish our Helm Chart to https://artifacthub.io/.

On generic cloud enivornments we want to be able to support ssl certificates

• Add alb ingress annotations
• Storage classes

Git Repo: https://github.com/keycloak/keycloak/tree/main/operator
Install instructions: https://www.keycloak.org/operator/installation

Paketo currently configures 50 threads which lead to extensive memory allocation on bigger machines

Current:
On every non aws cloud deployment we set the ingressClassName to "nginx".
In some environments (e.g. microk8s) this can lead to failing loadbalancers as microk8s expects ingressClassName: "public".

Desired:
Dynamically set the ingressClassName. If it cannot be determined automatically it should be part of the glasskube-settings ConfigMap.

• Explain minikube setup (with a custom --profile glasskube)
• Link to #4
• crate a CONTRIBUTING.md see https://github.com/github/docs fore examples
  • Explain coventional commits

It will get handy if we get some logs in the future to log the build version, commit hash and build timestamp of the operator. The java-operator-sdk creates a version.properties file during built time. We could do something similar: https://github.com/java-operator-sdk/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/ConfigurationServiceProvider.java#L72-L74

Odoo can be configured to not include demo data on module activation (--without-demo). https://www.odoo.com/documentation/16.0/developer/cli.html#cmdoption-odoo-bin-without-demo

This command line attribute should be configureable in the custom resource

• #97
• #159
• Odoo
• Keycloak (not possible)

We could utilize an existing MariaDB Operator for running MariaDB: https://github.com/mmontes11/mariadb-operator

pods should not get scheduled if not enough resources are available. This will degrade cluster performance.

We want to migrate developer tutorials into the CONTRIBUTING.md.

Implement upgrade path as documented in: mariadb-operator/mariadb-operator#19

1. Create Backup
2. Restore to new MariaDB Version
3. Switch labels

• Custom resource definition should define custom html
• Resources (deployments, service, ingress) should be automatically created on CR appearance
• http-echo can be used as http image
• Resources should be delete on CR deletion
• document crd

Books:

• https://www.oreilly.com/library/view/kubernetes-operators/9781492048039/

Currently the operator assumes the storage class standard is present.
Instead we should look for the storage class annotated with storageclass.kubernetes.io/is-default-class: true

In order to simply Glasskube Operator installation and it's dependencies we want to create an install script that does provide this functionallity.

Additonal information:

• A switch makes sense to install Glasskube cluster-wide or namespaced

Depends on:

• #29
• #31

Create initiale gradle setup for based on the https://github.com/java-operator-sdk/java-operator-sdk
We should appear in the "used in" section of the java-operator-sdk github project.

Related:

• #4

As stated in mariadb-operator/mariadb-operator#19 the new helm chart repository url is: https://charts.mmontes.duckdns.org/

• Pin chart version in deploy script as mariadb-operator is not yet stable
• Update Chart Repo
• Renamce MariaDB CRD

Currently the logging output in our testing branch has a lot of potential.

• Use an ASCII art Logo:

   ____ _               _          _          
  / ___| | __ _ ___ ___| | ___   _| |__   ___ 
 | |  _| |/ _` / __/ __| |/ / | | | '_ \ / _ \
 | |_| | | (_| \__ \__ \   <| |_| | |_) |  __/
  \____|_|\__,_|___/___/_|\_\\__,_|_.__/ \___|
                                           

Generated via https://manytools.org/hacker-tools/ascii-banner/ (Font: Standard)

• Log time, level, processid, thread, Class, message - "spring" and "quarkus" sample projects can be used as inspiration
• Configure different colors for different logging levels
• Create example logging lines in the main class
• Create a started in 0.01s logging line to let user know when to operator is functional