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

(fleet/kuma) deploy a temporary kuma dev monitoring instance #633

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions fleet/lib/kuma/fleet.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
defaultNamespace: kuma
labels:
bundle: kuma
helm:
chart: &chart uptime-kuma
releaseName: *chart
repo: https://dirsigler.github.io/uptime-kuma-helm
version: 2.20.0
timeoutSeconds: 300
waitForJobs: true
valuesFiles:
- values.yaml
35 changes: 35 additions & 0 deletions fleet/lib/kuma/values.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
ingress:
enabled: true
annotations:
cert-manager.io/cluster-issuer: letsencrypt
kubernetes.io/ingress.class: nginx
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This annotation is deprecated and we should try to stop using it for new bundles. Does the chart support setting ingressClassName ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nginx.ingress.kubernetes.io/backend-protocol: HTTP
nginx.ingress.kubernetes.io/server-snippet: |
proxy_ssl_verify off;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't necessary unless using HTTPS as the backend protocol.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I will clean up line 7.

nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is an hour long timeout needed?

nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
hosts:
- host: kuma.dev.lsst.org
paths:
- path: /
pathType: Prefix
tls:
- secretName: kuma-dashboard-ingress-tls
hosts:
- kuma.dev.lsst.org


volume:
enabled: true
accessMode: ReadWriteOnce
size: 4Gi
existingClaim: ""
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need to be set?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer so if possible, as i did not find a persistence key on the values chart.


resources:
limits:
cpu: "2"
memory: 8Gi
requests:
cpu: "2"
memory: 8Gi
1 change: 1 addition & 0 deletions fleet/s/dev/c/kueyen/kuma
Loading