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

Prow: stop using volumes and use local disk instead #922

Closed
tuminoid opened this issue Nov 28, 2024 · 6 comments · Fixed by #924
Closed

Prow: stop using volumes and use local disk instead #922

tuminoid opened this issue Nov 28, 2024 · 6 comments · Fixed by #924
Labels
triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@tuminoid
Copy link
Member

With the new private infrastructure servers deployed, Prow should stop using slow volumes and use local disk instead.

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Nov 28, 2024
@tuminoid
Copy link
Member Author

@lentzi90 as discussed offline.

@lentzi90
Copy link
Member

Let's just confirm that we have capacity first. It would not be nice to reserve local disk for prow if that makes the jenkins tests starved for resources.

@tuminoid
Copy link
Member Author

For the reference, can you summarize how the disk space was spent right now? @lentzi90

@lentzi90
Copy link
Member

Sure! Prow is currently using 100 GiB volumes. The cluster consists of 1 control plane node and minimum 3 worker nodes at the moment. The workers can scale up to a total of 6. The bastion host does not use any volume.

In total, that can be maximum 700 GiB. Most of the time we are at 400 GiB.

(Outside of this is 1 volume for ghproxy, also 100 GiB. This is attached to a pod so using local disk for it may not be a good idea. It would lose all state every image bump or eviction.)

@tuminoid
Copy link
Member Author

Thank you. I think we are safe to do the change next week. Leave ghproxy with a volume.

@tuminoid
Copy link
Member Author

/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants