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
Fix pool CRD format in egress.md and service-loadbalancer.md #3885
Conversation
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.
LGTM but have a question
docs/egress.md
Outdated
| kind: Egress | ||
| apiVersion: crd.antrea.io/v1alpha2 |
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.
nit: why revert kind and apiVersion's order? all K8s examples put apiVersion in the first line, and it's the default order when getting one resource's yaml via kubectl.
https://kubernetes.io/docs/concepts/services-networking/service/#defining-a-service
https://kubernetes.io/docs/concepts/services-networking/network-policies/#networkpolicy-resource
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.
Humm.. In this doc, ConfigMap has kind before apiVersion. Probably let me change that together.
Signed-off-by: Jianjun Shen <shenj@vmware.com>
|
/skip-all |
Signed-off-by: Jianjun Shen shenj@vmware.com