#11809 communishift-log-detective: requesting more resources
Closed: Fixed 2 months ago by praiskup. Opened 2 months ago by praiskup.

We have troubles to run cron jobs because of memory requirements (Let's Encrypt, data gathering job), more info in the upstream issue.

We think we need:

+    limits.memory: 6Gi
+    memory: 4Gi
+    persistentvolumeclaims: '3'
+    requests.storage: 10Gi

I've prepared this PR: https://pagure.io/fedora-infra/ansible/pull-request/1823

I should have the rights to run the playbook; a quick review from someone more experienced would be nice, though.

Should be able to accommodate the memory increases fine!

Tenants may only have one persistent volume claim, but the underlying filesystem has RWX permissions, so you can mount this same volume in multiple containers.

Remove this line and you're good to go:

+    persistentvolumeclaims: '3'

Metadata Update from @zlopez:
- Issue tagged with: low-gain, low-trouble, ops

2 months ago

Metadata Update from @dkirwan:
- Issue untagged with: low-gain, ops
- Issue tagged with: OpenShift, communishift, medium-gain

2 months ago

Metadata Update from @dkirwan:
- Issue untagged with: medium-gain
- Issue tagged with: low-gain, ops

2 months ago

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

2 months ago

I was told that the PVC limit 3 is a hard requirement, so reiterating with the log-detective team :-) thank you for taking a look, David!

Seems like rwx could work with single PVC! I merged the PR with the suggested change!

David ran the playbook for us, this is resolved, thank you!

Metadata Update from @praiskup:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 months ago

Metadata Update from @dkirwan:
- Issue assigned to dkirwan

2 months ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog