Arsenii Pastushenko

Hi @gridworkz ! No, this error means that ingress object was not configured correctly. Could you share a list of ingress objects in your cluster? `kubectl get ingress --all-namespaces` Also...

Ingress object should be created by Kuberlogic operator. Also, ingress objects must reside in service namespace. What is the reason for creating ingress objects manually?

Yep, The issue was related to a broken build. It is fixed now.

Hi @gridworkz ! Please see [the documentation about templating docker-compose](https://docs.kuberlogic.com/configuring/#templating-docker-compose-yaml). It is possible to use templates to pass variables to the application container.

> The `MySQLCluster` controller/resource should not be responsible for creating any additional services (as is the case of the k8s StatefulSet controller for example). The extra services should be created...

> You can go in the `mysql-cluster` helm chart and add two additional services as extensions, and with the extensibility of the chart, a new loadbalancer can be added without...

> right That's the point of my PR. ;)

I do agree that this PR changes API layout a little bit (though, I do not think it changes UX or introduces any significant changes to the overall application design)....

This one is super annoying. Actually, it makes /oauth/userinfo endpoint useless.

@wsimmonds Thank you for reply, now it shows me everything but memory usage