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

Include minimum system requirements in Getting Started guide(s) #4245

Closed
Tracked by #4553
psschwei opened this issue Sep 15, 2021 · 5 comments · Fixed by #4815
Closed
Tracked by #4553

Include minimum system requirements in Getting Started guide(s) #4245

psschwei opened this issue Sep 15, 2021 · 5 comments · Fixed by #4815
Assignees
Labels
Getting started guide Related to topics in the getting started guide kind/bug Categorizes issue or PR as related to a bug. kind/good-first-issue Denotes an issue ready for a new contributor. kind/install priority/critical
Milestone

Comments

@psschwei
Copy link
Contributor

Describe the change you'd like to see
In the various getting started guides (developer, cluster admin) it would be nice to provide a set of minimum system recommendations (cpu/ram, number of nodes, etc.) within the documentation.

Additional context
This was surfaced via a user who was unable to run the KonK script locally due to not having enough system resources and suggested this addition to the docs.

@abrennan89 abrennan89 added kind/bug Categorizes issue or PR as related to a bug. kind/install priority/critical labels Sep 17, 2021
@abrennan89
Copy link
Contributor

cc @omerbensaadon

@csantanapr
Copy link
Member

we should be able to run the kn quickstart for kind and minikube and check how much CPU and memory is requested and how much resources are being consumed when doing the two getting started for serving and eventing

@snneji
Copy link
Contributor

snneji commented Feb 1, 2022

We discussed in the working group meeting. We recommend the following for Quickstart: 3 CPUs, 2 GB RAM

@snneji snneji added the kind/good-first-issue Denotes an issue ready for a new contributor. label Feb 1, 2022
@julz
Copy link
Member

julz commented Feb 13, 2022

/unassign

@omerbensaadon
Copy link

/unassign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Getting started guide Related to topics in the getting started guide kind/bug Categorizes issue or PR as related to a bug. kind/good-first-issue Denotes an issue ready for a new contributor. kind/install priority/critical
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

6 participants