-
Notifications
You must be signed in to change notification settings - Fork 65
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
[question] What are the risks of the "experimental" generate_node_id feature? #203
Comments
Great question. I think we can safely update this to not be considered experimental anymore. It has been used in production for a few years and it has worked as intended 👌 . It could probably default to |
Does this mean if I have Thanks in advance and thanks for creating |
Yes! It's the way to go! |
That's great! Thanks again! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seems like
generate_node_id
is a couple years old now. Is it considered experimental?We're looking at using Kubernetes autoscaling, so to handle the issue of what happens when we scale down, it's either use
generate_node_id
or migrate off ofverk
. I'd like to figure out how safe the feature is at this point.What should we be watching out for, if anything?
The text was updated successfully, but these errors were encountered: