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

feat: nsq scaler docs #1485

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Conversation

Ulminator
Copy link

@Ulminator Ulminator commented Oct 14, 2024

Added nsq scaler documentation for v2.16 release.

Checklist

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

Relates to:

@Ulminator Ulminator requested a review from a team as a code owner October 14, 2024 21:09
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:

Copy link

netlify bot commented Oct 14, 2024

Deploy Preview for keda ready!

Name Link
🔨 Latest commit 763f2d8
🔍 Latest deploy log https://app.netlify.com/sites/keda/deploys/673694e3a834e4000852ee46
😎 Deploy Preview https://deploy-preview-1485--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
Member

@JorTurFer JorTurFer left a comment

Choose a reason for hiding this comment

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

LGTM! @zroubalik @wozniakjan PTAL



> **Notice:**
> - Since ["channels are created on first use by subscribing to the named channel"](https://nsq.io/overview/design.html#simplifying-configuration-and-administration), the topic depth is used instead of the channel depth when the channel does not yet exist on an [nsqd](https://nsq.io/components/nsqd.html) instance. This allows KEDA to effectively bootstrap new channels when the `idleReplicaCount` is 0.
Copy link
Member

Choose a reason for hiding this comment

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

is it really idleReplicaCount here or should it be more generic minReplicaCount?

Copy link
Author

Choose a reason for hiding this comment

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

It looks like minReplicaCount makes more sense, making a quick fix 👍

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