summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authoreduartua <eduartua@gmail.com>2019-01-24 11:57:12 -0600
committereduartua <eduartua@gmail.com>2019-01-24 11:57:12 -0600
commitaec30530356f433729658d1e682ade3ee65e31fe (patch)
tree7d6d48d28acb6e274b1b823b62c88cf9bbe22b6c
parentb42c86ea6b061cc34d195ddf3524db29b357dc11 (diff)
Grouping files by sig-architecture - fixed links
-rw-r--r--contributors/design-proposals/api-machinery/customresource-conversion-webhook.md2
-rw-r--r--contributors/design-proposals/auth/apparmor.md2
-rw-r--r--contributors/design-proposals/cluster-lifecycle/runtimeconfig.md2
-rw-r--r--contributors/design-proposals/network/external-lb-source-ip-preservation.md2
-rw-r--r--contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md2
-rw-r--r--contributors/guide/coding-conventions.md2
-rw-r--r--sig-architecture/api-review-process.md2
7 files changed, 7 insertions, 7 deletions
diff --git a/contributors/design-proposals/api-machinery/customresource-conversion-webhook.md b/contributors/design-proposals/api-machinery/customresource-conversion-webhook.md
index 2b4aeb25..453884e4 100644
--- a/contributors/design-proposals/api-machinery/customresource-conversion-webhook.md
+++ b/contributors/design-proposals/api-machinery/customresource-conversion-webhook.md
@@ -148,7 +148,7 @@ in *CRD v1* (apiextensions.k8s.io/v1), there will be only version list with no t
#### Alternative approaches considered
-First a defaulting approach is considered which per-version fields would be defaulted to top level fields. but that breaks backward incompatible change; Quoting from API [guidelines](https://github.com/kubernetes/community/blob/master/contributors/devel/api_changes.md#backward-compatibility-gotchas):
+First a defaulting approach is considered which per-version fields would be defaulted to top level fields. but that breaks backward incompatible change; Quoting from API [guidelines](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md#backward-compatibility-gotchas):
> A single feature/property cannot be represented using multiple spec fields in the same API version simultaneously
diff --git a/contributors/design-proposals/auth/apparmor.md b/contributors/design-proposals/auth/apparmor.md
index a88154bb..7fd30b46 100644
--- a/contributors/design-proposals/auth/apparmor.md
+++ b/contributors/design-proposals/auth/apparmor.md
@@ -63,7 +63,7 @@ and is supported on several
# Alpha Design
This section describes the proposed design for
-[alpha-level](../devel/api_changes.md#alpha-beta-and-stable-versions) support, although
+[alpha-level](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md#alpha-beta-and-stable-versions) support, although
additional features are described in [future work](#future-work). For AppArmor alpha support
(targeted for Kubernetes 1.4) we will enable:
diff --git a/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md b/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md
index c247eff8..ff6335a1 100644
--- a/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md
+++ b/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md
@@ -47,7 +47,7 @@ feature's owner(s). The following are suggested conventions:
- Features that touch multiple components should reserve the same key
in each component to toggle on/off.
- Alpha features should be disabled by default. Beta features may
- be enabled by default. Refer to docs/devel/api_changes.md#alpha-beta-and-stable-versions
+ be enabled by default. Refer to [this file](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md#alpha-beta-and-stable-versions)
for more detailed guidance on alpha vs. beta.
## Upgrade support
diff --git a/contributors/design-proposals/network/external-lb-source-ip-preservation.md b/contributors/design-proposals/network/external-lb-source-ip-preservation.md
index 50140a0e..11359e1a 100644
--- a/contributors/design-proposals/network/external-lb-source-ip-preservation.md
+++ b/contributors/design-proposals/network/external-lb-source-ip-preservation.md
@@ -50,7 +50,7 @@ lot of applications and customer use-cases.
# Alpha Design
This section describes the proposed design for
-[alpha-level](../devel/api_changes.md#alpha-beta-and-stable-versions) support, although
+[alpha-level](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md#alpha-beta-and-stable-versions) support, although
additional features are described in [future work](#future-work).
## Overview
diff --git a/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md b/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md
index cdfe1e1c..2a492b38 100644
--- a/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md
+++ b/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md
@@ -49,7 +49,7 @@ This was asked on the mailing list here[2] and here[3], too.
Several alternatives have been considered:
* Add a mode to the API definition when using secrets: this is backward
- compatible as described in (docs/devel/api_changes.md) IIUC and seems like the
+ compatible as described [here](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md) IIUC and seems like the
way to go. Also @thockin said in the ML that he would consider such an
approach. But it might be worth to consider if we want to do the same for
configmaps or owners, but there is no need to do it now either.
diff --git a/contributors/guide/coding-conventions.md b/contributors/guide/coding-conventions.md
index 63cc18ce..0ce3203d 100644
--- a/contributors/guide/coding-conventions.md
+++ b/contributors/guide/coding-conventions.md
@@ -55,7 +55,7 @@ the name of the directory in which the .go file exists.
sync.Mutex`). When multiple locks are present, give each lock a distinct name
following Go conventions - `stateLock`, `mapLock` etc.
- - [API changes](/contributors/devel/api_changes.md)
+ - [API changes](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md)
- [API conventions](/contributors/devel/api-conventions.md)
diff --git a/sig-architecture/api-review-process.md b/sig-architecture/api-review-process.md
index f3f23a62..7e69a4b2 100644
--- a/sig-architecture/api-review-process.md
+++ b/sig-architecture/api-review-process.md
@@ -227,7 +227,7 @@ Aspiring reviewers should reach out the moderator on slack. The moderator will
* [Updating-docs-for-feature-changes.md](https://git.k8s.io/sig-release/release-team/role-handbooks/documentation-guides/updating-docs-for-feature-changes.md#when-making-api-changes)
-* [https://github.com/kubernetes/community/blob/be9eeca6ee3becfa5b4c96bedf62b5b3ff5b1f8d/contributors/devel/api_changes.md](https://github.com/kubernetes/community/blob/be9eeca6ee3becfa5b4c96bedf62b5b3ff5b1f8d/contributors/devel/api_changes.md)
+* [https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md](/contributors/devel/sig-architecture/api_changes.md)
* [https://github.com/kubernetes/community/blob/be9eeca6ee3becfa5b4c96bedf62b5b3ff5b1f8d/contributors/devel/api-conventions.md](https://github.com/kubernetes/community/blob/be9eeca6ee3becfa5b4c96bedf62b5b3ff5b1f8d/contributors/devel/api-conventions.md)