merge origin master
This commit is contained in:
Binary file not shown.
|
After Width: | Height: | Size: 1.9 KiB |
BIN
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.8 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.8 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.0 KiB |
@@ -0,0 +1,3 @@
|
||||
---
|
||||
headless: true
|
||||
---
|
||||
+40
-161
@@ -6,178 +6,57 @@ cid: home
|
||||
|
||||
{{< deprecationwarning >}}
|
||||
|
||||
<!-- OCEAN NODES -->
|
||||
<section id="oceanNodes">
|
||||
<main>
|
||||
<div class="image-wrapper"><img src="images/flower.png"></div>
|
||||
<div class="content">
|
||||
<h3><a href="/docs/concepts/overview/what-is-kubernetes/">Kubernetes</a> is an open-source system for automating deployment, scaling, and management of containerized applications.</h3>
|
||||
<p>It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds
|
||||
upon <a href="http://queue.acm.org/detail.cfm?id=2898444">15 years of experience of running production workloads at Google</a>,
|
||||
combined with best-of-breed ideas and practices from the community.</p>
|
||||
</div>
|
||||
</main>
|
||||
<main>
|
||||
<div class="image-wrapper"><img src="images/scalable.png"></div>
|
||||
<div class="content">
|
||||
<h4>Planet Scale</h4>
|
||||
<p>Designed on the same principles that allows Google to run billions of containers a week, Kubernetes can scale without increasing your ops team.</p>
|
||||
</div>
|
||||
</main>
|
||||
<main>
|
||||
<div class="image-wrapper"><img src="images/blocks.png"></div>
|
||||
<div class="content">
|
||||
<h4>Never Outgrow</h4>
|
||||
<p>Whether testing locally or running a global enterprise, Kubernetes flexibility grows with you to deliver your applications consistently and easily no matter how complex your need is.</p>
|
||||
</div>
|
||||
</main>
|
||||
<main>
|
||||
<div class="image-wrapper"><img src="images/suitcase.png"></div>
|
||||
<div class="content">
|
||||
<h4>Run Anywhere</h4>
|
||||
<p>Kubernetes is open source giving you the freedom to take advantage of on-premises, hybrid, or public cloud infrastructure, letting you effortlessly move workloads to where it matters to you.</p>
|
||||
</div>
|
||||
</main>
|
||||
</section>
|
||||
{{< blocks/section id="oceanNodes" >}}
|
||||
{{% blocks/feature image="flower" %}}
|
||||
### [Kubernetes]({{< relref "/docs/concepts/overview/what-is-kubernetes" >}}) is an open-source system for automating deployment, scaling, and management of containerized applications.
|
||||
|
||||
<section id="video">
|
||||
<div class="light-text">
|
||||
<h2>The Challenges of Migrating 150+ Microservices to Kubernetes</h2>
|
||||
It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds upon [15 years of experience of running production workloads at Google](http://queue.acm.org/detail.cfm?id=2898444), combined with best-of-breed ideas and practices from the community.
|
||||
{{% /blocks/feature %}}
|
||||
|
||||
{{% blocks/feature image="scalable" %}}
|
||||
#### Planet Scale
|
||||
|
||||
Designed on the same principles that allows Google to run billions of containers a week, Kubernetes can scale without increasing your ops team.
|
||||
|
||||
{{% /blocks/feature %}}
|
||||
|
||||
{{% blocks/feature image="blocks" %}}
|
||||
#### Never Outgrow
|
||||
|
||||
Whether testing locally or running a global enterprise, Kubernetes flexibility grows with you to deliver your applications consistently and easily no matter how complex your need is.
|
||||
|
||||
{{% /blocks/feature %}}
|
||||
|
||||
{{% blocks/feature image="suitcase" %}}
|
||||
#### Run Anywhere
|
||||
|
||||
Kubernetes is open source giving you the freedom to take advantage of on-premises, hybrid, or public cloud infrastructure, letting you effortlessly move workloads to where it matters to you.
|
||||
|
||||
{{% /blocks/feature %}}
|
||||
|
||||
{{< /blocks/section >}}
|
||||
|
||||
{{< blocks/section id="video" background-image="kub_video_banner_homepage" >}}
|
||||
<div class="light-text">
|
||||
<h2>The Challenges of Migrating 150+ Microservices to Kubernetes</h2>
|
||||
<p>By Sarah Wells, Technical Director for Operations and Reliability, Financial Times</p>
|
||||
<button id="desktopShowVideoButton" onclick="kub.showVideo()">Watch Video</button>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<a href="https://events.linuxfoundation.cn/events/kubecon-cloudnativecon-china-2018/" button id= "desktopKCButton">Attend KubeCon in Shanghai on Nov. 13-15, 2018</a>
|
||||
<a href="https://www.lfasiallc.com/events/kubecon-cloudnativecon-china-2018/" button id="desktopKCButton">Attend KubeCon in Shanghai on Nov. 13-15, 2018</a>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<a href="https://events.linuxfoundation.org/events/kubecon-cloudnativecon-north-america-2018/" button id= "desktopKCButton">Attend KubeCon in Seattle on Dec. 11-13, 2018</a>
|
||||
</div>
|
||||
<button id="mobileShowVideoButton" onclick="kub.showVideo()"></button>
|
||||
</section>
|
||||
|
||||
<section id="features">
|
||||
<main>
|
||||
<h3 class="center">Kubernetes Features</h3>
|
||||
|
||||
<div class="feature-box">
|
||||
<div>
|
||||
<h4><a href="/docs/concepts/configuration/manage-compute-resources-container/">Automatic binpacking</a></h4>
|
||||
<p>Automatically places containers based on their resource requirements and other constraints, while not
|
||||
sacrificing availability. Mix critical and best-effort workloads in order to drive up utilization and save even more resources.</p>
|
||||
</div>
|
||||
<div>
|
||||
<h4><a href="/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller">Self-healing</a></h4>
|
||||
<p>Restarts containers that fail, replaces and reschedules containers when nodes die, kills containers
|
||||
that don't respond to your user-defined health check, and doesn't advertise them to clients until they are ready to serve.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="feature-box">
|
||||
<div>
|
||||
<h4><a href="/docs/tasks/run-application/horizontal-pod-autoscale/">Horizontal scaling</a></h4>
|
||||
<p>Scale your application up and down with a simple command, with a UI, or automatically based on CPU usage.</p>
|
||||
</div>
|
||||
<div>
|
||||
<h4><a href="/docs/concepts/services-networking/service/">Service discovery and load balancing</a></h4>
|
||||
<p>No need to modify your application to use an unfamiliar service discovery mechanism. Kubernetes gives
|
||||
containers their own IP addresses and a single DNS name for a set of containers, and can load-balance across them.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="feature-box">
|
||||
<div>
|
||||
<h4><a href="/docs/concepts/workloads/controllers/deployment/#what-is-a-deployment">Automated rollouts and rollbacks</a></h4>
|
||||
<p>Kubernetes progressively rolls out changes to your application or its configuration, while monitoring
|
||||
application health to ensure it doesn't kill all your instances at the same time. If something goes
|
||||
wrong, Kubernetes will rollback the change for you. Take advantage of a growing ecosystem of deployment solutions.</p>
|
||||
</div>
|
||||
<div>
|
||||
<h4><a href="/docs/concepts/configuration/secret/">Secret</a> and <a href="/docs/tasks/configure-pod-container/configure-pod-configmap/">configuration</a> management</h4>
|
||||
<p>Deploy and update secrets and application configuration without rebuilding your image and without
|
||||
exposing secrets in your stack configuration.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="feature-box">
|
||||
<div>
|
||||
<h4><a href="/docs/concepts/storage/persistent-volumes/">Storage orchestration</a></h4>
|
||||
<p>Automatically mount the storage system of your choice, whether from local storage, a public cloud provider
|
||||
such as <a href="https://cloud.google.com/storage/">GCP</a> or <a href="https://aws.amazon.com/products/storage/">AWS</a>, or a network storage system such as NFS, iSCSI,
|
||||
Gluster, Ceph, Cinder, or Flocker.</p>
|
||||
</div>
|
||||
<div>
|
||||
<h4><a href="/docs/concepts/workloads/controllers/jobs-run-to-completion/">Batch execution</a></h4>
|
||||
<p>In addition to services, Kubernetes can manage your batch and CI workloads, replacing containers that fail, if desired.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</main>
|
||||
</section>
|
||||
|
||||
<section id="talkToUs">
|
||||
<main>
|
||||
<h3>Case Studies</h3>
|
||||
<div id="caseStudiesWrapper">
|
||||
<div>
|
||||
<p>Sling TV: Marrying Kubernetes and AI to Enable Proper Web Scale</p>
|
||||
<a href="/case-studies/slingtv">Read more</a>
|
||||
</div>
|
||||
<div>
|
||||
<p>Using OpenTracing to Help Pinpoint the Bottlenecks</p>
|
||||
<a href="/case-studies/workiva">Read more</a>
|
||||
</div>
|
||||
<div>
|
||||
<p>Pinning Its Past, Present, and Future on Cloud Native</p>
|
||||
<a href="/case-studies/pinterest">Read more</a>
|
||||
</div>
|
||||
<div>
|
||||
<p>Reinventing the World’s Largest Education Company With Kubernetes</p>
|
||||
<a href="/case-studies/pearson">Read more</a>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<!--<div id="bigSocial">-->
|
||||
<!--<!–<div>–>-->
|
||||
<!--<!–<a href="https://youtu.be/OLwzSHBtxhI">Watch the video</a>–>-->
|
||||
<!--<!–<p>Creating Next Generation Kubernetes Infrastructure at Viacom</p>–>-->
|
||||
<!--<!–</div>–>-->
|
||||
<!--<div>-->
|
||||
<!--<p>Using Kubernetes to reinvent the world's largest educational company</p>-->
|
||||
<!--<a href="/case-studies/pearson/">Read more</a>-->
|
||||
<!--</div>-->
|
||||
<!--<div>-->
|
||||
<!--<p>Kubernetes at Box: Microservices at Maximum Velocity</p>-->
|
||||
<!--<a href="https://blog.box.com/blog/kubernetes-box-microservices-maximum-velocity/">Read more</a>-->
|
||||
<!--</div>-->
|
||||
<!--<div>-->
|
||||
<!--<p>Inside eBay's shift to Kubernetes and containers atop OpenStack</p>-->
|
||||
<!--<a href="http://www.nextplatform.com/2015/11/12/inside-ebays-shift-to-kubernetes-and-containers-atop-openstack/">Read the story</a>-->
|
||||
<!--</div>-->
|
||||
<!--<div>-->
|
||||
<!--<p>Migrating from a homegrown 'cluster' to Kubernetes</p>-->
|
||||
<!--<a href="https://www.youtube.com/watch?v=6XGUTu3WhBw">Watch the video</a>-->
|
||||
<!--</div>-->
|
||||
<!--</div>-->
|
||||
<h5 style="text-align: center"><a href="/case-studies/" style="color: #3371E3; font-weight: 400">View all case studies</a></h5>
|
||||
</main>
|
||||
</section>
|
||||
<section id="cncf">
|
||||
<main>
|
||||
<center>
|
||||
<p style="font-size: 20px">We are a <a href="https://cncf.io/">CNCF</a> graduated project</p>
|
||||
</center>
|
||||
</main>
|
||||
</section>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<a href="https://events.linuxfoundation.org/events/kubecon-cloudnativecon-north-america-2018/" button id="desktopKCButton">Attend KubeCon in Seattle on Dec. 11-13, 2018</a>
|
||||
</div>
|
||||
<div id="videoPlayer">
|
||||
<iframe data-url="https://www.youtube.com/embed/H06qrNmGqyE?autoplay=1" frameborder="0" allowfullscreen></iframe>
|
||||
<button id="closeButton"></button>
|
||||
</div>
|
||||
{{< /blocks/section >}}
|
||||
|
||||
{{< blocks/kubernetes-features >}}
|
||||
|
||||
{{< blocks/case-studies >}}
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
title: Blog
|
||||
title: Kubernetes Blog
|
||||
linkTitle: Blog
|
||||
menu:
|
||||
main:
|
||||
title: "Blog"
|
||||
weight: 40
|
||||
post: >
|
||||
<p>Read the latest news for Kubernetes and the containers space in general, and get technical how-tos hot off the presses.</p>
|
||||
---
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Case Studies
|
||||
linkTitle: Case Studies
|
||||
bigheader: Kubernetes User Case Studies
|
||||
abstract: A collection of users running Kubernetes in production.
|
||||
layout: basic
|
||||
|
||||
@@ -1,6 +1,12 @@
|
||||
---
|
||||
title: "Community"
|
||||
weight: 80
|
||||
menu:
|
||||
main:
|
||||
title: "Community"
|
||||
weight: 30
|
||||
post: >
|
||||
<p>If you need help, you can connect with other Kubernetes users and the Kubernetes authors, attend community events, and watch video presentations from around the web.</p>
|
||||
---
|
||||
|
||||
This section of the Kubernetes documentation surfaces key topics imported from the [kubernetes/community](https://github.com/kubernetes/community) repo. It is the starting point for becoming a contributor -- improving docs, improving code, giving talks etc.
|
||||
|
||||
@@ -2,6 +2,10 @@
|
||||
title: Managing Compute Resources for Containers
|
||||
content_template: templates/concept
|
||||
weight: 20
|
||||
feature:
|
||||
title: Automatic binpacking
|
||||
description: >
|
||||
Automatically places containers based on their resource requirements and other constraints, while not sacrificing availability. Mix critical and best-effort workloads in order to drive up utilization and save even more resources.
|
||||
---
|
||||
|
||||
{{% capture overview %}}
|
||||
|
||||
@@ -3,6 +3,10 @@ reviewers:
|
||||
- mikedanese
|
||||
title: Secrets
|
||||
content_template: templates/concept
|
||||
feature:
|
||||
title: Secret and configuration management
|
||||
description: >
|
||||
Deploy and update secrets and application configuration without rebuilding your image and without exposing secrets in your stack configuration.
|
||||
weight: 50
|
||||
---
|
||||
|
||||
|
||||
@@ -2,6 +2,11 @@
|
||||
reviewers:
|
||||
- bprashanth
|
||||
title: Services
|
||||
feature:
|
||||
title: Service discovery and load balancing
|
||||
description: >
|
||||
No need to modify your application to use an unfamiliar service discovery mechanism. Kubernetes gives containers their own IP addresses and a single DNS name for a set of containers, and can load-balance across them.
|
||||
|
||||
content_template: templates/concept
|
||||
weight: 10
|
||||
---
|
||||
|
||||
@@ -5,6 +5,11 @@ reviewers:
|
||||
- thockin
|
||||
- msau42
|
||||
title: Persistent Volumes
|
||||
feature:
|
||||
title: Storage orchestration
|
||||
description: >
|
||||
Automatically mount the storage system of your choice, whether from local storage, a public cloud provider such as <a href="https://cloud.google.com/storage/">GCP</a> or <a href="https://aws.amazon.com/products/storage/">AWS</a>, or a network storage system such as NFS, iSCSI, Gluster, Ceph, Cinder, or Flocker.
|
||||
|
||||
content_template: templates/concept
|
||||
weight: 20
|
||||
---
|
||||
|
||||
@@ -3,6 +3,11 @@ reviewers:
|
||||
- bgrant0607
|
||||
- janetkuo
|
||||
title: Deployments
|
||||
feature:
|
||||
title: Automated rollouts and rollbacks
|
||||
description: >
|
||||
Kubernetes progressively rolls out changes to your application or its configuration, while monitoring application health to ensure it doesn't kill all your instances at the same time. If something goes wrong, Kubernetes will rollback the change for you. Take advantage of a growing ecosystem of deployment solutions.
|
||||
|
||||
content_template: templates/concept
|
||||
weight: 30
|
||||
---
|
||||
|
||||
@@ -4,6 +4,10 @@ reviewers:
|
||||
- soltysh
|
||||
title: Jobs - Run to Completion
|
||||
content_template: templates/concept
|
||||
feature:
|
||||
title: Batch execution
|
||||
description: >
|
||||
In addition to services, Kubernetes can manage your batch and CI workloads, replacing containers that fail, if desired.
|
||||
weight: 70
|
||||
---
|
||||
|
||||
|
||||
@@ -3,6 +3,12 @@ reviewers:
|
||||
- bprashanth
|
||||
- janetkuo
|
||||
title: ReplicationController
|
||||
feature:
|
||||
title: Self-healing
|
||||
anchor: How a ReplicationController Works
|
||||
description: >
|
||||
Restarts containers that fail, replaces and reschedules containers when nodes die, kills containers that don't respond to your user-defined health check, and doesn't advertise them to clients until they are ready to serve.
|
||||
|
||||
content_template: templates/concept
|
||||
weight: 20
|
||||
---
|
||||
|
||||
@@ -181,7 +181,7 @@ status:
|
||||
lastTransitionTime: 2018-01-01T00:00:00Z
|
||||
- type: "www.example.com/feature-1" # an extra PodCondition
|
||||
status: "False"
|
||||
lastProbeTIme: null
|
||||
lastProbeTime: null
|
||||
lastTransitionTime: 2018-01-01T00:00:00Z
|
||||
containerStatuses:
|
||||
- containerID: docker://abcd...
|
||||
|
||||
@@ -263,6 +263,29 @@ The output is:
|
||||
**Warning:** Beware.
|
||||
{{< /warning >}}
|
||||
|
||||
### Katacoda Embedded Live Environment
|
||||
|
||||
This button lets users run Minikube in their browser using the [Katacoda Terminal](https://www.katacoda.com/embed/panel).
|
||||
It lowers the barier of entry by allowing users to use Minikube with one click instead of going through the complete
|
||||
Minikube and Kubectl installation process locally.
|
||||
|
||||
The Embedded Live Environment is configured to run `minikube start` and lets users complete tutorials in the same window
|
||||
as the documentation.
|
||||
|
||||
{{< caution >}}
|
||||
**Caution:** The session is limited to 15 minutes.
|
||||
{{< /caution >}}
|
||||
|
||||
For example:
|
||||
|
||||
```
|
||||
{{</* kat-button */>}}
|
||||
```
|
||||
|
||||
The output is:
|
||||
|
||||
{{< kat-button >}}
|
||||
|
||||
## Common Shortcode Issues
|
||||
|
||||
### Ordered Lists
|
||||
|
||||
@@ -8,7 +8,13 @@ cid: userJourneys
|
||||
css: /css/style_user_journeys.css
|
||||
js: /js/user-journeys/home.js, https://use.fontawesome.com/4bcc658a89.js
|
||||
display_browse_numbers: true
|
||||
linkTitle: "Home"
|
||||
linkTitle: Documentation
|
||||
main_menu: true
|
||||
weight: 10
|
||||
menu:
|
||||
main:
|
||||
title: "Documentation"
|
||||
weight: 20
|
||||
post: >
|
||||
<p>Learn how to use Kubernetes with the use of walkthroughs, samples, and reference documentation. You can even <a href="/editdocs/" data-auto-burger-exclude>help contribute to the docs</a>!</p>
|
||||
---
|
||||
|
||||
@@ -9,7 +9,7 @@ weight: 60
|
||||
{{% capture overview %}}
|
||||
|
||||
Kubeadm defaults to running a single member etcd cluster in a static pod managed
|
||||
by the kubelet on the control plane node. This is not a high availability setup
|
||||
by the kubelet on the control plane node. This is not a high availability setup
|
||||
as the etcd cluster contains only one member and cannot sustain any members
|
||||
becoming unavailable. This task walks through the process of creating a high
|
||||
availability etcd cluster of three members that can be used as an external etcd
|
||||
@@ -107,8 +107,8 @@ this example.
|
||||
|
||||
If you already have a CA then the only action that is copying the CA's `crt` and
|
||||
`key` file to `/etc/kubernetes/pki/etcd/ca.crt` and
|
||||
`/etc/kubernetes/pki/etcd/ca.key`. After those files have been copied, please
|
||||
proceed to "Create certificates for each member".
|
||||
`/etc/kubernetes/pki/etcd/ca.key`. After those files have been copied,
|
||||
proceed to the next step, "Create certificates for each member".
|
||||
|
||||
If you do not already have a CA then run this command on `$HOST0` (where you
|
||||
generated the configuration files for kubeadm).
|
||||
|
||||
@@ -210,8 +210,8 @@ Now lets validate that Kubernetes automatically labeled the zone & region the PV
|
||||
|
||||
```shell
|
||||
> kubectl get pv --show-labels
|
||||
NAME CAPACITY ACCESSMODES STATUS CLAIM REASON AGE LABELS
|
||||
pv-gce-mj4gm 5Gi RWO Bound default/claim1 46s failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a
|
||||
NAME CAPACITY ACCESSMODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE LABELS
|
||||
pv-gce-mj4gm 5Gi RWO Retain Bound default/claim1 manual 46s failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a
|
||||
```
|
||||
|
||||
So now we will create a pod that uses the persistent volume claim.
|
||||
|
||||
@@ -198,7 +198,7 @@ We recommend that you use the etcd version which is provided in the Kubernetes b
|
||||
were tested extensively with this version of etcd and not with any other version.
|
||||
The recommended version number can also be found as the value of `TAG` in `kubernetes/cluster/images/etcd/Makefile`.
|
||||
|
||||
For the miniumum recommended version of etcd, please refer to
|
||||
For the miniumum recommended version of etcd, refer to
|
||||
[Configuring and Updating etcd](/docs/tasks/administer-cluster/configure-upgrade-etcd/)
|
||||
|
||||
The remainder of the document assumes that the image identifiers have been chosen and stored in corresponding env vars. Examples (replace with latest tags and appropriate registry):
|
||||
@@ -419,7 +419,7 @@ Note that on some Linux platforms, you may need to manually install the
|
||||
`conntrack` package which is a dependency of kube-proxy, or else kube-proxy
|
||||
cannot be started successfully.
|
||||
|
||||
For more details on debugging kube-proxy problems, please refer to
|
||||
For more details about debugging kube-proxy problems, refer to
|
||||
[Debug Services](/docs/tasks/debug-application-cluster/debug-service/)
|
||||
|
||||
### Networking
|
||||
@@ -864,7 +864,7 @@ pinging or SSH-ing from one node to another.
|
||||
|
||||
### Getting Help
|
||||
|
||||
If you run into trouble, please see the section on [troubleshooting](/docs/setup/turnkey/gce/#troubleshooting), post to the
|
||||
If you run into trouble, see the section on [troubleshooting](/docs/setup/turnkey/gce/#troubleshooting), post to the
|
||||
[kubernetes-users group](https://groups.google.com/forum/#!forum/kubernetes-users), or come ask questions on [Slack](/docs/troubleshooting#slack).
|
||||
|
||||
## Support Level
|
||||
|
||||
@@ -31,7 +31,7 @@ Configuring the [aggregation layer](/docs/concepts/api-extension/apiserver-aggre
|
||||
Enable the aggregation layer via the following kube-apiserver flags. They may have already been taken care of by your provider.
|
||||
|
||||
--requestheader-client-ca-file=<path to aggregator CA cert>
|
||||
--requestheader-allowed-names=aggregator
|
||||
--requestheader-allowed-names=front-proxy-client
|
||||
--requestheader-extra-headers-prefix=X-Remote-Extra-
|
||||
--requestheader-group-headers=X-Remote-Group
|
||||
--requestheader-username-headers=X-Remote-User
|
||||
|
||||
@@ -390,7 +390,9 @@ TARGET_VERSION=2.2.1
|
||||
STORAGE_MEDIA_TYPE=application/json
|
||||
```
|
||||
|
||||
** Note: this upgrade procedure is for getting from 2.x to 3.x. Version `3.0.17` is not recommended for running in production (see [prerequisites](#prereqisites) for minimum recommended etcd versions.
|
||||
{{< note >}}
|
||||
**Note:** This procedure upgrades from 2.x to 3.x. Version `3.0.17` is not recommended for running in production (see [prerequisites](#prerequisites) for minimum recommended etcd versions).
|
||||
{{< /note >}}
|
||||
|
||||
## Notes for etcd Version 2.2.1
|
||||
|
||||
|
||||
@@ -4,6 +4,11 @@ reviewers:
|
||||
- jszczepkowski
|
||||
- directxman12
|
||||
title: Horizontal Pod Autoscaler
|
||||
feature:
|
||||
title: Horizontal scaling
|
||||
description: >
|
||||
Scale your application up and down with a simple command, with a UI, or automatically based on CPU usage.
|
||||
|
||||
content_template: templates/concept
|
||||
weight: 90
|
||||
---
|
||||
|
||||
@@ -346,3 +346,7 @@ To add shortcodes to includes.
|
||||
{{< note >}}
|
||||
{{< include "federation-current-state.md" >}}
|
||||
{{< /note >}}
|
||||
|
||||
## Katacoda Embedded Live Environment
|
||||
|
||||
{{< kat-button >}}
|
||||
|
||||
@@ -2,6 +2,12 @@
|
||||
title: Hello Minikube
|
||||
content_template: templates/tutorial
|
||||
weight: 5
|
||||
menu:
|
||||
main:
|
||||
title: "Get Started"
|
||||
weight: 10
|
||||
post: >
|
||||
<p>Ready to get your hands dirty? Build a simple Kubernetes cluster that runs "Hello World" for Node.js.</p>
|
||||
---
|
||||
|
||||
{{% capture overview %}}
|
||||
|
||||
@@ -10,8 +10,6 @@ weight: 10
|
||||
|
||||
<body>
|
||||
|
||||
<link href="./public/css/styles.css" rel="stylesheet">
|
||||
|
||||
<div class="layout" id="top">
|
||||
|
||||
<main class="content">
|
||||
|
||||
Reference in New Issue
Block a user