criscola / kubernetes-dbaas

A unique Kubernetes Database-as-a-Service (DBaaS) Operator for declarative, self-service database provisioning in DBMS solutions.

Hi there 👋

kubernetes-dbaas's Issues

mdatabase.kb.io webhook error

Hello,

I use:
Kubernetes v1.21.1
cert-manager 1.4.4

This is my configuration:
values.yaml:

enableMetricsRbac: false
dbms:
  - databaseClassName: "postgres-default"
    endpoints:
      - name: "postgres-default"
        dsn: "postgres://postgres@REDACTED"

postgres-example.yaml:

apiVersion: database.dbaas.bedag.ch/v1
kind: Database
metadata:
  name: database-sample  
spec:
  endpoint: postgres-default

I get a the following error message on kubectl apply -f postgres-example.yaml:

Error from server (InternalError): error when creating "postgres-example.yaml": Internal error occurred: failed calling webhook "mdatabase.kb.io": Post "https://kubernetes-dbaas-webhook-service.kubernetes-dbaas-system.svc:443/mutate-database-dbaas-bedag-ch-v1-database?timeout=10s": dial tcp 10.250.98.125:443: connect: connection refused

Trival flow for Postgres

Hi,

Your software seems great, but I try the simpliest flow but I cannot get it run.
Especially, the stored procedure deployment is not documented (there is examples in the test data).
The Usage specify apiVersion: dbaas.bedag.ch/v1 whereas it seems that apiVersion: database.dbaas.bedag.ch/v1 should be used instead.

I think you should describe a minimal working flow that is sure to be working:

• Get a cluster with the right version
• Install cert-manager
• Install prometeus (I think you should disable it be default to start with)
• Execute Stored Procedure creation script (it would be even better if these are auto-created if not specified otherwise)
• Configure a database class (without SecretRef to start with) in values.yaml
• Install kubernetes-dbaas
• apply a database creation file

By just doing that I should I should have a database up & running with a secret in my namespace