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

Add more debugging scenarios for not scaling as expected #1298

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

OfficiallySomeGuy
Copy link

Reference kedacore/keda#5263, adding some more documentation for guiding debugging, and highlighting known issues.

Checklist

  • Commits are signed with Developer Certificate of Origin (DCO)

Fixes #

Update docs adding more scenarios for debugging

Reference kedacore/keda#5263, adding some more documentation for guiding debugging, and highlighting known issues

Signed-off-by: OfficiallySomeGuy <[email protected]>
@OfficiallySomeGuy OfficiallySomeGuy requested a review from a team as a code owner January 19, 2024 18:05
Copy link

netlify bot commented Jan 19, 2024

Deploy Preview for keda ready!

Name Link
🔨 Latest commit f033d28
🔍 Latest deploy log https://app.netlify.com/sites/keda/deploys/65aab9ed5eb995000990e917
😎 Deploy Preview https://deploy-preview-1298--keda.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

Thank you for your contribution! 🙏 We will review your PR as soon as possible.

While you are waiting, make sure to:

  • Add your contribution to all applicable KEDA versions
  • GitHub checks are passing
  • Is the DCO check failing? Here is how you can fix DCO issues

Learn more about:

@@ -1,14 +1,36 @@
+++
title = "Why is my `ScaledObject` paused?"
title = "Why is my `ScaledObject` not scaling as expected?"
Copy link
Member

Choose a reason for hiding this comment

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

I personally would prefer a seperate item for this; people using pausing will more likely be helped faster if we have a dedicated item.

You can still refer to the new item from within the paused entry

Copy link
Member

Choose a reason for hiding this comment

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

Agree a separate section would be great

Copy link
Member

@zroubalik zroubalik left a comment

Choose a reason for hiding this comment

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

@OfficiallySomeGuy any update on this please?

@OfficiallySomeGuy
Copy link
Author

@zroubalik unfortunately I am prohibited from making any further contributions, however if you would like to amend this PR and merge it, I would be supportive

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants