We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey there!
I've deployed nats-nack, but I can see it's missing the following important components.
not that it uses a whole pile, but it would be good to have a handle on this, with sensible defaults.
pretty important for health checks, etc.
ideally more than one, or have a PDB that would ensure its running.
I guess my questions are:
The text was updated successfully, but these errors were encountered:
Happy to accept a PR that sets these defaults 👍
Sorry, something went wrong.
Since Go 1.19 has been I think we can start adding these limits, we also should apply GOMEMLIMIT so that limits.memory actually works for the Go GC.
limits.memory
No branches or pull requests
Hey there!
I've deployed nats-nack, but I can see it's missing the following important components.
RESOURCES:
not that it uses a whole pile, but it would be good to have a handle on this, with sensible defaults.
PROBES:
pretty important for health checks, etc.
REPLICAS:
ideally more than one, or have a PDB that would ensure its running.
I guess my questions are:
The text was updated successfully, but these errors were encountered: