summaryrefslogtreecommitdiff
path: root/keps
diff options
context:
space:
mode:
authorramnar <raam.soft@gmail.com>2018-11-28 02:15:12 +0530
committerk8s-ci-robot <k8s-ci-robot@users.noreply.github.com>2018-11-27 12:45:12 -0800
commitc701c750ac1464a45fd5a5bd360e905bdc1423cd (patch)
tree816f969c305eed6b7d9b1b1b9a5cb25280199478 /keps
parent6f60b8f68d2cb8b8ea3164c556a2c793f25da085 (diff)
Fix for #2696 (#2969)
* Fix for 2696 FILE: ./keps/sig-cluster-lifecycle/0003-cluster-api.md [✖] https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/apis/kubeadm/v1alpha1/types.go → Status: 404 FILE: ./keps/sig-auth/0014-dynamic-audit-configuration.md [✖] http://github.com/kubernetes/community/blob/master/Users/patrick/go/src/k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/authorization/authorizer/interfaces.go → Status: 404 FILE: ./sig-apps/agenda.md [✖] www.github.com/kubernetes/helm → Status: 400 Error: ENOENT: no such file or directory, access '/home/jorge/src/kubernetes/community/sig-apps/www.github.com/kubernetes/helm' [✖] https://deis.com/ → Status: 0 Error: ETIMEDOUT FILE: ./sig-cli/migrated-from-wiki/roadmap-kubectl.md [✖] http://kubernetes.sh/kploy/ → Status: 404 * Review Comments incorporated for 2969 FILE: ./sig-apps/agenda.md [✖] www.github.com/kubernetes/helm → Status: 400 Error: ENOENT: no such file or directory, access '/home/jorge/src/kubernetes/community/sig-apps/www.github.com/kubernetes/helm' [✖] https://deis.com/ → Status: 0 Error: ETIMEDOUT * Fix for 2696 FILE: ./keps/sig-cluster-lifecycle/0003-cluster-api.md [✖] https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/apis/kubeadm/v1alpha1/types.go → Status: 404 FILE: ./keps/sig-auth/0014-dynamic-audit-configuration.md [✖] http://github.com/kubernetes/community/blob/master/Users/patrick/go/src/k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/authorization/authorizer/interfaces.go → Status: 404 FILE: ./sig-apps/agenda.md [✖] www.github.com/kubernetes/helm → Status: 400 Error: ENOENT: no such file or directory, access '/home/jorge/src/kubernetes/community/sig-apps/www.github.com/kubernetes/helm' [✖] https://deis.com/ → Status: 0 Error: ETIMEDOUT FILE: ./sig-cli/migrated-from-wiki/roadmap-kubectl.md [✖] http://kubernetes.sh/kploy/ → Status: 404 Review Comments incorporated for 2969 FILE: ./sig-apps/agenda.md [✖] www.github.com/kubernetes/helm → Status: 400 Error: ENOENT: no such file or directory, access '/home/jorge/src/kubernetes/community/sig-apps/www.github.com/kubernetes/helm' [✖] https://deis.com/ → Status: 0 Error: ETIMEDOUT
Diffstat (limited to 'keps')
-rw-r--r--keps/sig-auth/0014-dynamic-audit-configuration.md2
-rw-r--r--keps/sig-cluster-lifecycle/0003-cluster-api.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/keps/sig-auth/0014-dynamic-audit-configuration.md b/keps/sig-auth/0014-dynamic-audit-configuration.md
index 3863c058..8a7df026 100644
--- a/keps/sig-auth/0014-dynamic-audit-configuration.md
+++ b/keps/sig-auth/0014-dynamic-audit-configuration.md
@@ -201,7 +201,7 @@ parameters. It will then utilize the `LevelAndStages` method in the policy
and drop any unneeded sections. The new dynamic backend will implement the `EnforcedSink` interface, and update its state
based on a shared informer. For the existing backends to comply, a method will be added that implements the `EnforcedSink` interface.
-Implementing the [attribute interface](/Users/patrick/go/src/k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/authorization/authorizer/interfaces.go)
+Implementing the [attribute interface](https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/apiserver/pkg/authorization/authorizer/interfaces.go)
based on the Event struct was also explored. This would allow us to keep the existing `Sink` interfaces, however it would
require parsing the request URI twice in the pipeline due to how that field is represented in the Event. This was determined
to not be worth the cost.
diff --git a/keps/sig-cluster-lifecycle/0003-cluster-api.md b/keps/sig-cluster-lifecycle/0003-cluster-api.md
index b6f6a14c..66dc0edf 100644
--- a/keps/sig-cluster-lifecycle/0003-cluster-api.md
+++ b/keps/sig-cluster-lifecycle/0003-cluster-api.md
@@ -128,7 +128,7 @@ These use cases are out of scope entirely:
This level of the Cluster Management API describes the global configuration of a cluster. It should be capable of representing the versioning and configuration of the entire control plane, irrespective of the representation of nodes.
-Given the recent efforts of SIG Cluster Lifecycle to make kubeadm the de facto standard toolkit for cloud- and vendor-agnostic cluster initialization, and because kubeadm has [an existing API](https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/apis/kubeadm/v1alpha1/types.go) to define the global configuration for a cluster, it makes sense to coalesce the global portion of the Cluster API with the API used by “kubeadm init” to configure a cluster master.
+Given the recent efforts of SIG Cluster Lifecycle to make kubeadm the de facto standard toolkit for cloud- and vendor-agnostic cluster initialization, and because kubeadm has [an existing API](https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/apis/kubeadm/v1alpha3/types.go) to define the global configuration for a cluster, it makes sense to coalesce the global portion of the Cluster API with the API used by “kubeadm init” to configure a cluster master.
A current goal is to make these APIs as cloud-agnostic as possible, so that the entire definition of a Cluster could remain reasonably in-sync across different deployments potentially in different cloud providers, which would help enable hybrid usecases where it’s desirable to have key configuration stay in sync across different clusters potentially in different clouds/environments. However, this goal is balanced against making the APIs coherent and usable, which strict separation may harm.