Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request: allow for more configurations #34

Open
vmarchaud opened this issue Mar 23, 2020 · 0 comments
Open

request: allow for more configurations #34

vmarchaud opened this issue Mar 23, 2020 · 0 comments

Comments

@vmarchaud
Copy link

@vmarchaud vmarchaud commented Mar 23, 2020

Hi,

I'm deploying statusbay on GKE with the following setup:

  • one cluster used to host ui+api+database
  • one staging cluster that connect to the db
  • one prod cluster that connect to the db

Every cluster is using a different GCP account to i must expose the db to internet so i can monitor the deployments on all cluster (would better to use the api instead of the database in the future).

However i had some issues with the chart as it is today:

  • API + UI services are ClusterIP, GKE only allow ingress to service that are NodePort or LoadBalancer so that would be helpful if configurable
  • By default GKE Ingress use / to check if the service is working, it's working on the UI since it expose the frontend but the API is failing because of that. I believe you should add the readinessProbe and livenessProbe to both.
  • I use cert-manager to get SSL cert for both the API/UI with annonations on the ingress, however i need to define the tls config. Should be perfect if you could add the options on the chart !

I've had other issue because of the database need to be exposed to internet but that's not really whats the chart is about. However you could rely on the official stable mysql chart to ease that part

Thanks for statusbay by the way, cool software !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.