Kubernetes - Revision history

Pchero: /* See also */

2020-03-03T07:37:23Z

Pchero: /* Storage */

2020-02-26T12:20:15Z

Storage

@@ Line 48: / Line 48: @@
 == Storage ==
 === Volumes ===
 A Kubernetes volume has an explicit lifetime - the same as the Pod that encloses it. Consequently, a volume outlives any Containers that run within the Pod, and data is preserved across Container restarts. Of course, when a Pod ceases to exist, the volume will sease to exist, too. Perhaps more importantly than this, Kubernetes supports many types of volumes, and a Pod can use any number of them simultaneously.

Pchero: /* gcePersistentDisk */

2020-02-21T13:34:58Z

gcePersistentDisk

← Older revision		Revision as of 13:34, 21 February 2020
Line 71:		Line 71:

	==== gcePersistentDisk ====		==== gcePersistentDisk ====
			* https://kubernetes.io/docs/concepts/storage/volumes/#gcepersistentdisk

	A gcePeristentDisk volume mounts a Google Compute Engine Persistent Disk into your Pod. Unlike emptyDir, which is erased when a Pod is removed, the contents of a PD are preserved and the volume is merely unmounted. This means that a PD can be pre-populated with data, and that data can be "handed off" between Pods.		A gcePeristentDisk volume mounts a Google Compute Engine Persistent Disk into your Pod. Unlike emptyDir, which is erased when a Pod is removed, the contents of a PD are preserved and the volume is merely unmounted. This means that a PD can be pre-populated with data, and that data can be "handed off" between Pods.
	<pre>		<pre>

Pchero: /* gcePersistentDisk */

2020-02-21T13:34:33Z

gcePersistentDisk

@@ Line 74: / Line 74: @@
 <pre>
 You must create a Persistent Disk using gcloud or the GCE API or UI before you can use it.
 </pre>

Pchero: /* Persistent volume */

2020-02-21T13:27:52Z

Persistent volume

← Older revision		Revision as of 13:27, 21 February 2020
Line 56:		Line 56:

	=== Persistent volume ===		=== Persistent volume ===
			* https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes

	PersistentVolume resources are used to manage durable storage in a cluster. On GKE, PersistentVolumes are typically backed by Compute Engine persistent disks. PersistentVolumes can also be used with other storage types like NFS. Refer to the Kubernetes documentation for an exhaustive overview of PersistentVolumes.		PersistentVolume resources are used to manage durable storage in a cluster. On GKE, PersistentVolumes are typically backed by Compute Engine persistent disks. PersistentVolumes can also be used with other storage types like NFS. Refer to the Kubernetes documentation for an exhaustive overview of PersistentVolumes.

Pchero: /* gcePersistentDisk */

2020-02-21T13:27:39Z

gcePersistentDisk

← Older revision		Revision as of 13:27, 21 February 2020
Line 73:		Line 73:
	You must create a Persistent Disk using gcloud or the GCE API or UI before you can use it.		You must create a Persistent Disk using gcloud or the GCE API or UI before you can use it.
	</pre>		</pre>

	* https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes

	== Tutorial ==		== Tutorial ==

Pchero: /* Persistent volume */

2020-02-21T13:22:41Z

Persistent volume

← Older revision		Revision as of 13:22, 21 February 2020
Line 67:		Line 67:

	Portability is another advantage of using PersistentVolumes and PersistentVolumeClaims. You can easily use the same Pod specification across different clusters and environments because PersistentVolume is an interface to the actual backing storage.		Portability is another advantage of using PersistentVolumes and PersistentVolumeClaims. You can easily use the same Pod specification across different clusters and environments because PersistentVolume is an interface to the actual backing storage.

			==== gcePersistentDisk ====
			A gcePeristentDisk volume mounts a Google Compute Engine Persistent Disk into your Pod. Unlike emptyDir, which is erased when a Pod is removed, the contents of a PD are preserved and the volume is merely unmounted. This means that a PD can be pre-populated with data, and that data can be "handed off" between Pods.
			<pre>
			You must create a Persistent Disk using gcloud or the GCE API or UI before you can use it.
			</pre>

	* https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes		* https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes

Pchero: /* Volumes */

2020-02-21T13:19:37Z

Volumes

← Older revision		Revision as of 13:19, 21 February 2020
Line 54:		Line 54:

	* https://kubernetes.io/docs/concepts/storage/volumes/		* https://kubernetes.io/docs/concepts/storage/volumes/

			=== Persistent volume ===
			PersistentVolume resources are used to manage durable storage in a cluster. On GKE, PersistentVolumes are typically backed by Compute Engine persistent disks. PersistentVolumes can also be used with other storage types like NFS. Refer to the Kubernetes documentation for an exhaustive overview of PersistentVolumes.

			Unlike Volumes, the PersistenVolumes lifecycle is managed by Kubernetes. PersistentVolume can be dynamically provisioned; the user does not have to manually create and delete the backing storage.

			PersistentVolumes are cluster resources that exist independently of Pods. This means that the disk and data represented by a PersistentVolume continue to exist as the cluster changes and as Pods are deleted and recreated. PersistentVolume resources can be provisioned dynamically through PersistentVolumeClaims, or they can be explicitly created by a cluster administrator.

			A PersistentVolumeClaim is a request for and claim to a PersistentVolume resource. PersistentVolumeClaim objects request a specific size, access mode, and StorageClass for the PersistentVolume. If a PersistentVolume that satisfies the request exists or can be provisioned, the PersistentVolumeClaim is bound to that PeristentVolume.

			Pods are claims as Volumes. The cluster inspects the claim to find the bound Volume and mounts that Volume for the Pod.

			Portability is another advantage of using PersistentVolumes and PersistentVolumeClaims. You can easily use the same Pod specification across different clusters and environments because PersistentVolume is an interface to the actual backing storage.

			* https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes

	== Tutorial ==		== Tutorial ==

Pchero: /* Tutorial */

2020-02-21T09:28:34Z

Tutorial

← Older revision		Revision as of 09:28, 21 February 2020
Line 46:		Line 46:

	The kube-node-lease which holds node lease objects used for node heartbeat data.		The kube-node-lease which holds node lease objects used for node heartbeat data.

			== Storage ==
			=== Volumes ===
			A Kubernetes volume has an explicit lifetime - the same as the Pod that encloses it. Consequently, a volume outlives any Containers that run within the Pod, and data is preserved across Container restarts. Of course, when a Pod ceases to exist, the volume will sease to exist, too. Perhaps more importantly than this, Kubernetes supports many types of volumes, and a Pod can use any number of them simultaneously.

			At its core, a volume is just a directory, possibly with some data in it, which is accessible to the Containers in a Pod. How that directory comes to be, the medium that backs it, and the contents of it are determined by the particular volume type used.

			* https://kubernetes.io/docs/concepts/storage/volumes/

	== Tutorial ==		== Tutorial ==

Pchero at 23:17, 6 January 2020

2020-01-06T23:17:38Z

← Older revision		Revision as of 23:17, 6 January 2020
Line 169:		Line 169:
	* https://kubernetes.io/ko/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/		* https://kubernetes.io/ko/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/

	[[category:~~system~~]]		[[category:kubernetes]]

← Older revision		Revision as of 07:37, 3 March 2020
Line 246:		Line 246:
	=== See also ===		=== See also ===
	* https://kubernetes.io/ko/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/		* https://kubernetes.io/ko/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/

			== Errors ==
			=== nodes are available: 1 Insufficient cpu, 1 Insufficient memory ===
			CPU 자원 및 Memory 자원이 충족되지 않음을 나타낸다.

	[[category:kubernetes]]		[[category:kubernetes]]