Deprecation complete: gpus ... (#3537)
This commit is contained in:
@@ -6,6 +6,9 @@ title: Logging and Monitoring Cluster Activity
|
||||
redirect_from:
|
||||
- "/docs/concepts/clusters/logging/"
|
||||
- "/docs/concepts/clusters/logging.html"
|
||||
redirect_from:
|
||||
- "/docs/user-guide/logging/overview/"
|
||||
- "/docs/user-guide/logging/overview.html"
|
||||
---
|
||||
|
||||
Application and systems logs can help you understand what is happening inside your cluster. The logs are particularly useful for debugging problems and monitoring cluster activity. Most modern applications have some kind of logging mechanism; as such, most container engines are likewise designed to support some kind of logging. The easiest and most embraced logging method for containerized applications is to write to the standard output and standard error streams.
|
||||
|
||||
@@ -2,6 +2,9 @@
|
||||
assignees:
|
||||
- mikedanese
|
||||
title: Resource Usage Monitoring
|
||||
redirect_from:
|
||||
- "/docs/user-guide/monitoring/"
|
||||
- "/docs/user-guide/monitoring.html"
|
||||
---
|
||||
|
||||
Understanding how an application behaves when deployed is crucial to scaling the application and providing a reliable service. In a Kubernetes cluster, application performance can be examined at many different levels: containers, [pods](/docs/user-guide/pods), [services](/docs/user-guide/services), and whole clusters. As part of Kubernetes we want to provide users with detailed resource usage information about their running applications at all these levels. This will give users deep insights into how their applications are performing and where possible application bottlenecks may be found. In comes [Heapster](https://github.com/kubernetes/heapster), a project meant to provide a base monitoring platform on Kubernetes.
|
||||
|
||||
@@ -11,6 +11,8 @@ title: PetSets
|
||||
redirect_from:
|
||||
- "/docs/concepts/abstractions/controllers/petsets/"
|
||||
- "/docs/concepts/abstractions/controllers/petsets.html"
|
||||
- "/docs/user-guide/petset/bootstrapping/"
|
||||
- "/docs/user-guide/petset/bootstrapping/index.html"
|
||||
---
|
||||
|
||||
__Warning:__ Starting in Kubernetes version 1.5, PetSet has been renamed to [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets). To use (or continue to use) PetSet in Kubernetes 1.5, you _must_ [migrate](/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set/) your existing PetSets to StatefulSets. For information on working with StatefulSet, see the tutorial on [how to run replicated stateful applications](/docs/tutorials/stateful-application/run-replicated-stateful-application).
|
||||
|
||||
@@ -1,5 +1,8 @@
|
||||
---
|
||||
title: Using Port Forwarding to Access Applications in a Cluster
|
||||
redirect_from:
|
||||
- "/docs/user-guide/connecting-to-applications-port-forward/"
|
||||
- "/docs/user-guide/connecting-to-applications-port-forward.html"
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
@@ -1,5 +1,8 @@
|
||||
---
|
||||
title: Using an HTTP Proxy to Access the Kubernetes API
|
||||
redirect_from:
|
||||
- "/docs/user-guide/connecting-to-applications-proxy/"
|
||||
- "/docs/user-guide/connecting-to-applications-proxy.html"
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
@@ -3,6 +3,9 @@ assignees:
|
||||
- jpeeler
|
||||
- pmorie
|
||||
title: Using Projected volumes
|
||||
redirect_from:
|
||||
- "/docs/user-guide/projected-volume/"
|
||||
- "/docs/user-guide/projected-volume/index.html"
|
||||
---
|
||||
|
||||
The _projected volume_ is a volume that projects several existing volume sources
|
||||
|
||||
@@ -3,6 +3,9 @@ assignees:
|
||||
- crassirostris
|
||||
- piosz
|
||||
title: Logging Using Elasticsearch and Kibana
|
||||
redirect_from:
|
||||
- "/docs/user-guide/logging/elasticsearch/"
|
||||
- "/docs/user-guide/logging/elasticsearch.html"
|
||||
---
|
||||
|
||||
On the Google Compute Engine (GCE) platform, the default logging support targets
|
||||
|
||||
@@ -3,6 +3,9 @@ assignees:
|
||||
- crassirostris
|
||||
- piosz
|
||||
title: Logging Using Stackdriver
|
||||
redirect_from:
|
||||
- "/docs/user-guide/logging/stackdriver/"
|
||||
- "/docs/user-guide/logging/stackdriver.html"
|
||||
---
|
||||
|
||||
Before reading this page, it's highly recommended to familiarize yourself
|
||||
|
||||
@@ -3,6 +3,9 @@ assignees:
|
||||
- caesarxuchao
|
||||
- mikedanese
|
||||
title: Getting a Shell to a Running Container
|
||||
redirect_from:
|
||||
- "/docs/user-guide/getting-into-containers/"
|
||||
- "/docs/user-guide/getting-into-containers.html"
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
@@ -2,6 +2,9 @@
|
||||
assignees:
|
||||
- vishh
|
||||
title: Scheduling GPUs
|
||||
redirect_from:
|
||||
- "/docs/user-guide/gpus/"
|
||||
- "/docs/user-guide/gpus.html"
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
assignees:
|
||||
- caesarxuchao
|
||||
- mikedanese
|
||||
title: Connect with Port Forwarding
|
||||
---
|
||||
|
||||
{% include user-guide-content-moved.md %}
|
||||
|
||||
[Using Port Forwarding to Access Applications in a Cluster](/docs/tasks/access-application-cluster/port-forward-access-application-cluster/)
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
assignees:
|
||||
- caesarxuchao
|
||||
- lavalamp
|
||||
title: Connect with Proxies
|
||||
---
|
||||
|
||||
{% include user-guide-content-moved.md %}
|
||||
|
||||
[Using an HTTP Proxy to Access the Kubernetes API](/docs/tasks/access-kubernetes-api/http-proxy-access-api/)
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
assignees:
|
||||
- caesarxuchao
|
||||
- mikedanese
|
||||
title: Running Commands in a Container with kubectl exec
|
||||
---
|
||||
|
||||
{% include user-guide-content-moved.md %}
|
||||
|
||||
[Getting a Shell to a Running Container](/docs/tasks/kubectl/get-shell-running-container/)
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
assignees:
|
||||
- vishh
|
||||
title: GPU Support
|
||||
---
|
||||
|
||||
{% include user-guide-content-moved.md %}
|
||||
|
||||
[Scheduling GPUs](/docs/tasks/manage-gpus/scheduling-gpus/)
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
assignees:
|
||||
- crassirostris
|
||||
- piosz
|
||||
title: Logging with Elasticsearch and Kibana
|
||||
---
|
||||
|
||||
{% include user-guide-content-moved.md %}
|
||||
|
||||
[Logging Using ElasticSearch and Kibana](/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana/)
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
assignees:
|
||||
- crassirostris
|
||||
- piosz
|
||||
title: Logging Overview
|
||||
---
|
||||
|
||||
{% include user-guide-content-moved.md %}
|
||||
|
||||
[Logging and Monitoring Cluster Activity](/docs/concepts/clusters/logging/)
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
assignees:
|
||||
- crassirostris
|
||||
- piosz
|
||||
title: Logging with Stackdriver Logging
|
||||
---
|
||||
|
||||
{% include user-guide-content-moved.md %}
|
||||
|
||||
[Logging Using Stackdriver](/docs/tasks/debug-application-cluster/logging-stackdriver/)
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
assignees:
|
||||
- mikedanese
|
||||
title: Resource Usage Monitoring
|
||||
---
|
||||
|
||||
{% include user-guide-content-moved.md %}
|
||||
|
||||
[Resource Usage Monitoring](/docs/concepts/cluster-administration/resource-usage-monitoring/)
|
||||
@@ -1,18 +0,0 @@
|
||||
---
|
||||
assignees:
|
||||
- bprashanth
|
||||
- enisoc
|
||||
- erictune
|
||||
- foxish
|
||||
- janetkuo
|
||||
- kow3ns
|
||||
- smarterclayton
|
||||
title: Bootstrapping Pet Sets
|
||||
---
|
||||
|
||||
{% include user-guide-content-moved.md %}
|
||||
|
||||
[PetSets](/docs/concepts/abstractions/controllers/petsets/)
|
||||
|
||||
|
||||
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
assignees:
|
||||
- jpeeler
|
||||
- pmorie
|
||||
title: Using Projected volumes
|
||||
---
|
||||
|
||||
{% include user-guide-content-moved.md %}
|
||||
|
||||
[Using Projected Volumes](/docs/tasks/configure-pod-container/projected-volume/)
|
||||
Reference in New Issue
Block a user