-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Document the endpoint admission controller #2443
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
Conversation
Note that {product-title} will not let most users manually create an | ||
Endpoints object that points to pod or service IPs. (Since these IPs | ||
are normally dynamically assigned, it doesn't make much sense to try | ||
to track them manually anyway.) Only |
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'd drop the parenthetical
33d0e13
to
2c80f0e
Compare
updated |
|
||
The servers that back a service are called its endpoints, and are | ||
specified by an object of type *Endpoints* with the same name as the | ||
service. When a service is backed by pods, those pods will normally be |
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.
s/those pods will normally be/those pods are normally specified
2c80f0e
to
8a3c141
Compare
@ahardin-rh updated |
@danwinship Thanks! |
[rev_history] |
Documents the changes from openshift/origin#9383.
@liggitt ok? (I didn't bother to create an extra built-in role for endpoints/restricted permission since I don't think many people are going to need it anyway. And we can always add it later if they do.)