Projects:Kubernetes - Bewerkingsoverzicht

Minnozz: Minnozz heeft pagina HSNWiki:Kubernetes hernoemd naar Projects:Kubernetes over een doorverwijzing

2020-02-05T16:15:48Z

Minnozz heeft pagina HSNWiki:Kubernetes hernoemd naar Projects:Kubernetes over een doorverwijzing

← Oudere versie

Versie van 5 feb 2020 16:15

2020-02-05T16:12:12Z

Minnozz heeft pagina Projects:Kubernetes hernoemd naar HSNWiki:Kubernetes over een doorverwijzing: Use Project: prefix

← Oudere versie

Versie van 5 feb 2020 16:12

2020-01-21T21:29:48Z

+categorie:projects

← Oudere versie		Versie van 21 jan 2020 21:29
Regel 1.112:		Regel 1.112:
	* Limiting pods in memory, CPU, I/O		* Limiting pods in memory, CPU, I/O
	* Limiting pods in network communication		* Limiting pods in network communication

			[[Categorie:Projects]]

2019-03-30T15:12:47Z

To do

← Oudere versie		Versie van 30 mrt 2019 15:12
Regel 1.101:		Regel 1.101:
	** https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-api-from-a-pod		** https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-api-from-a-pod
	** <code>wget --ca-certificate=/run/secrets/kubernetes.io/serviceaccount/ca.crt -qO- https://kubernetes.default.svc.cluster.local/api/</code>		** <code>wget --ca-certificate=/run/secrets/kubernetes.io/serviceaccount/ca.crt -qO- https://kubernetes.default.svc.cluster.local/api/</code>
			** Doesn't need using the Kubernetes API, can be done using env vars: https://kubernetes.io/docs/tasks/inject-data-application/environment-variable-expose-pod-information/
	* Play with native cronjobs		* Play with native cronjobs
	* Play with Statefulset / Daemonset		* Play with Statefulset / Daemonset

2019-03-30T00:30:51Z

To do

← Oudere versie		Versie van 30 mrt 2019 00:30
Regel 1.108:		Regel 1.108:
	** Allow K8s API communication from a pod, but only to receive information about itself		** Allow K8s API communication from a pod, but only to receive information about itself
	** Basically: Make it impossible to root a node even with "broad" privileges on the Kubernetes API server		** Basically: Make it impossible to root a node even with "broad" privileges on the Kubernetes API server
			** https://kubernetes.io/docs/concepts/policy/pod-security-policy/
	* Limiting pods in memory, CPU, I/O		* Limiting pods in memory, CPU, I/O
	* Limiting pods in network communication		* Limiting pods in network communication

2019-03-29T23:41:29Z

To do

← Oudere versie		Versie van 29 mrt 2019 23:41
Regel 1.099:		Regel 1.099:
	*** Here too, this only worked for me after unholding the kubelet and upgrading it as well.		*** Here too, this only worked for me after unholding the kubelet and upgrading it as well.
	* Try getting information on a pod from inside it using the Kubernetes API		* Try getting information on a pod from inside it using the Kubernetes API
			** https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-api-from-a-pod
	** <code>wget --ca-certificate=/run/secrets/kubernetes.io/serviceaccount/ca.crt -qO- https://kubernetes.default.svc.cluster.local/api/</code>		** <code>wget --ca-certificate=/run/secrets/kubernetes.io/serviceaccount/ca.crt -qO- https://kubernetes.default.svc.cluster.local/api/</code>
	* Play with native cronjobs		* Play with native cronjobs

2019-03-29T23:38:24Z

To do

← Oudere versie		Versie van 29 mrt 2019 23:38
Regel 1.099:		Regel 1.099:
	*** Here too, this only worked for me after unholding the kubelet and upgrading it as well.		*** Here too, this only worked for me after unholding the kubelet and upgrading it as well.
	* Try getting information on a pod from inside it using the Kubernetes API		* Try getting information on a pod from inside it using the Kubernetes API
			** <code>wget --ca-certificate=/run/secrets/kubernetes.io/serviceaccount/ca.crt -qO- https://kubernetes.default.svc.cluster.local/api/</code>
	* Play with native cronjobs		* Play with native cronjobs
	* Play with Statefulset / Daemonset		* Play with Statefulset / Daemonset

2019-03-28T22:42:19Z

To do

← Oudere versie		Versie van 28 mrt 2019 22:42
Regel 1.097:		Regel 1.097:
	** Unhold the kubelet and kubectl packages on the master, upgrade them and re-hold them, then restart the kubelet		** Unhold the kubelet and kubectl packages on the master, upgrade them and re-hold them, then restart the kubelet
	** For each worker, unhold the kubeadm package, upgrade it, rehold it; cordon (drain) the node; upgrade the node config; install the new kubelet version and restart it; uncordon the node.		** For each worker, unhold the kubeadm package, upgrade it, rehold it; cordon (drain) the node; upgrade the node config; install the new kubelet version and restart it; uncordon the node.
			*** Here too, this only worked for me after unholding the kubelet and upgrading it as well.
	* Try getting information on a pod from inside it using the Kubernetes API		* Try getting information on a pod from inside it using the Kubernetes API
	* Play with native cronjobs		* Play with native cronjobs

2019-03-28T22:40:28Z

To do

← Oudere versie		Versie van 28 mrt 2019 22:40
Regel 1.095:		Regel 1.095:
	** On the master, "kubeadm upgrade plan", then "kubeadm upgrade apply v1.14.x"		** On the master, "kubeadm upgrade plan", then "kubeadm upgrade apply v1.14.x"
	** Upgrade CNI controller by re-running the same <code>kubectl apply</code> as earlier		** Upgrade CNI controller by re-running the same <code>kubectl apply</code> as earlier
	** Unhold the kubelet ~~package~~ on the master, upgrade it and re-hold it, then restart the kubelet		** Unhold the kubelet and kubectl packages on the master, upgrade them and re-hold them, then restart the kubelet
	** For each worker, unhold the kubeadm package, upgrade it, rehold it; cordon (drain) the node; upgrade the node config; install the new kubelet version and restart it; uncordon the node.		** For each worker, unhold the kubeadm package, upgrade it, rehold it; cordon (drain) the node; upgrade the node config; install the new kubelet version and restart it; uncordon the node.
	* Try getting information on a pod from inside it using the Kubernetes API		* Try getting information on a pod from inside it using the Kubernetes API

2019-03-28T22:34:30Z

To do

← Oudere versie		Versie van 28 mrt 2019 22:34
Regel 1.092:		Regel 1.092:
	** First, do a normal apt upgrade (the kubernetes packages are held and will not be modified)		** First, do a normal apt upgrade (the kubernetes packages are held and will not be modified)
	** Then, unhold the kubeadm package on the master, upgrade it to the right version, then re-hold it		** Then, unhold the kubeadm package on the master, upgrade it to the right version, then re-hold it
			*** This only worked for me after unholding the kubelet and upgrading it as well.
	** On the master, "kubeadm upgrade plan", then "kubeadm upgrade apply v1.14.x"		** On the master, "kubeadm upgrade plan", then "kubeadm upgrade apply v1.14.x"
	** Upgrade CNI controller by re-running the same <code>kubectl apply</code> as earlier		** Upgrade CNI controller by re-running the same <code>kubectl apply</code> as earlier