diff --git a/_data/glossary/annotation.yaml b/_data/glossary/annotation.yaml new file mode 100644 index 0000000000..f680440b08 --- /dev/null +++ b/_data/glossary/annotation.yaml @@ -0,0 +1,9 @@ +id: annotation +name: Annotation +full-link: docs/concepts/overview/working-with-objects/annotations +tags: +- fundamental +short-description: > + A key-value pair that is used to attach arbitrary non-identifying metadata to objects. +long-description: > + The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by labels. Clients such as tools and libraries can retrieve this metadata. diff --git a/_data/glossary/horizontal-pod-autoscaler.yaml b/_data/glossary/horizontal-pod-autoscaler.yaml new file mode 100644 index 0000000000..534a0c80b8 --- /dev/null +++ b/_data/glossary/horizontal-pod-autoscaler.yaml @@ -0,0 +1,15 @@ +id: horizontal-pod-autoscaler +name: Horizontal Pod Autoscaler +full-link: /docs/tasks/run-application/horizontal-pod-autoscale/ +aka: +- HPA +related: +- pod +tags: +- operation +short-description: > + An API resource that automatically scales the number of pod replicas based on targeted CPU + utilization or custom metric targets. +long-description: > + HPA is typically used with replication controllers, deployments or replica sets and cannot be + applied to objects that cannot be scaled, for example DaemonSets. diff --git a/_data/glossary/labels.yaml b/_data/glossary/labels.yaml new file mode 100644 index 0000000000..024620571c --- /dev/null +++ b/_data/glossary/labels.yaml @@ -0,0 +1,9 @@ +id: labels +name: Labels +full-link: /docs/concepts/overview/working-with-objects/labels +tags: +- fundamental +short-description: > + Used to tag objects with identifying attributes that are meaningful and relevant to users. +long-description: > + Labels are key/value pairs that are attached to objects, such as pods. They can be used to organize and to select subsets of objects. \ No newline at end of file diff --git a/community/index.html b/community/index.html index e78541e9e4..d15a52f0e8 100644 --- a/community/index.html +++ b/community/index.html @@ -7,7 +7,7 @@ cid: community

Community

-KubeConNA +KubeConEU
diff --git a/docs/tasks/administer-cluster/securing-a-cluster.md b/docs/tasks/administer-cluster/securing-a-cluster.md index 70645afcb5..2b3d192a49 100644 --- a/docs/tasks/administer-cluster/securing-a-cluster.md +++ b/docs/tasks/administer-cluster/securing-a-cluster.md @@ -1,6 +1,9 @@ --- approvers: - smarterclayton +- liggitt +- ericchiang +- destijl title: Securing a Cluster --- @@ -68,6 +71,15 @@ to prevent accidental escalation. You can make roles specific to your use case i Consult the [authorization reference section](/docs/admin/authorization/) for more information. +## Controlling access to the Kubelet + +Kubelets expose HTTPS endpoints which give access to data of varying sensitivity, and allow performing operations with varying levels of power on the node and within containers. + +By default, Kubelets allow full access to those endpoints. + +To secure access to those endpoints, enable Kubelet authentication and authorization. + +Consult the [Kubelet authentication/authorization reference](/docs/admin/kubelet-authentication-authorization) for more information. ## Controlling the capabilities of a workload or user at runtime @@ -151,7 +163,7 @@ access to a subset of the keyspace is strongly recommended. ### Enable audit logging -The [audit logger](/docs/tasks/debug-application-cluster/audit/) is an alpha feature that records actions taken by the +The [audit logger](/docs/tasks/debug-application-cluster/audit/) is a beta feature that records actions taken by the API for later analysis in the event of a compromise. It is recommended to enable audit logging and archive the audit file on a secure server. diff --git a/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md b/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md index d6bc7302e6..0a65970345 100644 --- a/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md +++ b/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md @@ -4,14 +4,14 @@ approvers: - jszczepkowski - justinsb - directxman12 -title: Horizontal Pod Autoscaling Walkthrough +title: Horizontal Pod Autoscaler Walkthrough --- -Horizontal Pod Autoscaling automatically scales the number of pods +Horizontal Pod Autoscaler automatically scales the number of pods in a replication controller, deployment or replica set based on observed CPU utilization (or, with beta support, on some other, application-provided metrics). -This document walks you through an example of enabling Horizontal Pod Autoscaling for the php-apache server. For more information on how Horizontal Pod Autoscaling behaves, see the [Horizontal Pod Autoscaling user guide](/docs/tasks/run-application/horizontal-pod-autoscale/). +This document walks you through an example of enabling Horizontal Pod Autoscaler for the php-apache server. For more information on how Horizontal Pod Autoscaler behaves, see the [Horizontal Pod Autoscaler user guide](/docs/tasks/run-application/horizontal-pod-autoscaler/). ## Prerequisites @@ -24,7 +24,7 @@ heapster monitoring will be turned-on by default). To specify multiple resource metrics for a Horizontal Pod Autoscaler, you must have a Kubernetes cluster and kubectl at version 1.6 or later. Furthermore, in order to make use of custom metrics, your cluster must be able to communicate with the API server providing the custom metrics API. -See the [Horizontal Pod Autoscaling user guide](/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-custom-metrics) for more details. +See the [Horizontal Pod Autoscaler user guide](/docs/tasks/run-application/horizontal-pod-autoscaler/#support-for-custom-metrics) for more details. ## Step One: Run & expose php-apache server diff --git a/docs/tasks/run-application/horizontal-pod-autoscale.md b/docs/tasks/run-application/horizontal-pod-autoscale.md index 3fdf3ffc57..84b3373a0e 100644 --- a/docs/tasks/run-application/horizontal-pod-autoscale.md +++ b/docs/tasks/run-application/horizontal-pod-autoscale.md @@ -3,18 +3,18 @@ approvers: - fgrzadkowski - jszczepkowski - directxman12 -title: Horizontal Pod Autoscaling +title: Horizontal Pod Autoscaler --- -This document describes the current state of Horizontal Pod Autoscaling in Kubernetes. +This document describes the current state of the Horizontal Pod Autoscaler in Kubernetes. -## What is Horizontal Pod Autoscaling? +## What is the Horizontal Pod Autoscaler? -With Horizontal Pod Autoscaling, Kubernetes automatically scales the number of pods +The Horizontal Pod Autoscaler automatically scales the number of pods in a replication controller, deployment or replica set based on observed CPU utilization (or, with [custom metrics](https://git.k8s.io/community/contributors/design-proposals/instrumentation/custom-metrics-api.md) support, on some other application-provided metrics). Note that Horizontal -Pod Autoscaling does not apply to objects that can't be scaled, for example, DaemonSet. +Pod Autoscaling does not apply to objects that can't be scaled, for example, DaemonSets. The Horizontal Pod Autoscaler is implemented as a Kubernetes API resource and a controller. The resource determines the behavior of the controller. diff --git a/images/KubeCon_EU_Community.jpg b/images/KubeCon_EU_Community.jpg new file mode 100644 index 0000000000..51584150ae Binary files /dev/null and b/images/KubeCon_EU_Community.jpg differ diff --git a/index.html b/index.html index cf22d1e40c..92850a4b91 100644 --- a/index.html +++ b/index.html @@ -64,7 +64,7 @@ cid: home

- Attend KubeCon in Austin, TX on December 6-8, 2017 + Attend KubeCon in Copenhagen on May 2-4, 2018