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

Write a Getting Started guide #1364

Open
Tracked by #1361 ...
dwelsch-esi opened this issue Apr 12, 2024 · 10 comments · May be fixed by #1404
Open
Tracked by #1361 ...

Write a Getting Started guide #1364

dwelsch-esi opened this issue Apr 12, 2024 · 10 comments · May be fixed by #1404

Comments

@dwelsch-esi
Copy link
Contributor

Write a task-based, step-by-step workflow for new users. Start with the current KEDA Documentation section.

This issue tracks recommended changes resulting from an analysis of the KEDA documentation commissioned by CNCF. The analysis and supporting documents are here: https://github.com/cncf/techdocs/tree/main/assessments/0011-keda/

Use-Case

Assume the new user has no experience with KEDA and is fairly new to Kubernetes. The current documentation assumes that users know how to deploy and use Kubernetes Custom Resources, and that using KEDA is a matter of knowing the right configuration parameters and deploying the right resources. This might be true for veteran users, but new users want explicit, foolproof instructions.

Specification

The following outline has been annotated to emphasize the purpose of each section. Links are to existing pages that can be used as-is or provide a starting point. Pages with multiple procedures (for example, the "Deploying KEDA" page) should be split into multiple pages, one for each procedure.

@mhmohona
Copy link

mhmohona commented Jun 1, 2024

Hello! May I work on this issue?

@tomkerkhove
Copy link
Member

Certainly!

@shubhusion
Copy link
Contributor

@tomkerkhove I would like to work on this issue. But can you provide the directory where files needs to be added.

@mhmohona mhmohona linked a pull request Jun 7, 2024 that will close this issue
1 task
Copy link

stale bot commented Aug 6, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Aug 6, 2024
@shubhusion
Copy link
Contributor

is this issue still relevant ?

@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Aug 6, 2024
@mhmohona
Copy link

mhmohona commented Aug 6, 2024

Hey @shubhusion, I am working on it, submitted PR.

Please find other issues from here to work on.

@shubhusion
Copy link
Contributor

Hey @shubhusion, I am working on it, submitted PR.

Please find other issues from here to work on.

Great, thanks for letting me know!

Copy link

stale bot commented Oct 5, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Oct 5, 2024
Copy link

stale bot commented Oct 19, 2024

This issue has been automatically closed due to inactivity.

@nate-double-u
Copy link
Contributor

I'm not sure this has been completed, if it was just the bot that closed this could we reopen it?

@wozniakjan wozniakjan reopened this Nov 25, 2024
@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

6 participants