-
Notifications
You must be signed in to change notification settings - Fork 326
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
Expose new options for API Gateway's High Availability feature #1261
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Syntax lines up with everything we added to the gateway yaml and I like that is all optional. Looks good to me.
# deployment: | ||
# defaultInstances: 3 | ||
# maxInstances: 8 | ||
# minInstances: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does a user know what are all possible values for deployment
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Documentation is being added alongside our 0.3.0
release here.
The 3 listed above are all that's supported with our upcoming release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to link to those docs here? Because folks will also see this through https://www.consul.io/docs/k8s/helm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can link those, noting that the docs content in the PR linked above won't actually be there for about a week after the consul-k8s release containing this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh understood. Yeah then we can add it later instead.
Co-authored-by: Iryna Shustava <ishustava@users.noreply.github.com>
Changes proposed in this PR:
GatewayClassConfig
0.3.0
in the near future.For example:
How I've tested this PR:
helm install
with various combinations of deployment config$ kubectl apply --kustomize "github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.2.1"
)deployment
at all without updating gateway CRDs0.3.0
$ kubectl apply --kustomize "github.com/hashicorp/consul-api-gateway/config/crd?ref=main"
)deployment
at alldeployment
with one field at a timedeployment
with all fields setHow I expect reviewers to test this PR:
See above
Checklist: