summaryrefslogtreecommitdiff
path: root/nodeaffinity.md
diff options
context:
space:
mode:
Diffstat (limited to 'nodeaffinity.md')
-rw-r--r--nodeaffinity.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/nodeaffinity.md b/nodeaffinity.md
index 3d9266ae..3c29d6fe 100644
--- a/nodeaffinity.md
+++ b/nodeaffinity.md
@@ -211,7 +211,7 @@ Users should not start using `NodeAffinity` until the full implementation has
been in Kubelet and the master for enough binary versions that we feel
comfortable that we will not need to roll back either Kubelet or master to a
version that does not support them. Longer-term we will use a programatic
-approach to enforcing this (#4855).
+approach to enforcing this ([#4855](https://github.com/kubernetes/kubernetes/issues/4855)).
## Implementation plan
@@ -234,7 +234,7 @@ longer satisfies `RequiredDuringSchedulingRequiredDuringExecution` (see [this co
We assume Kubelet publishes labels describing the node's membership in all of
the relevant scheduling domains (e.g. node name, rack name, availability zone
-name, etc.). See #9044.
+name, etc.). See [#9044](https://github.com/kubernetes/kubernetes/issues/9044).
## Extensibility
@@ -268,10 +268,11 @@ Are there any other fields we should convert from `map[string]string` to
## Related issues
-The review for this proposal is in #18261.
+The review for this proposal is in [#18261](https://github.com/kubernetes/kubernetes/issues/18261).
-The main related issue is #341. Issue #367 is also related. Those issues
-reference other related issues.
+The main related issue is [#341](https://github.com/kubernetes/kubernetes/issues/341).
+Issue [#367](https://github.com/kubernetes/kubernetes/issues/367) is also related.
+Those issues reference other related issues.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->