Kubernetes - Revision history

Rorist: /* Add your own Service */

2021-08-08T21:07:50Z

‎Add your own Service

2021-08-08T21:07:41Z

‎Add your own

2021-08-08T21:06:22Z

‎SSL

2021-08-08T21:05:43Z

2021-07-26T08:15:54Z

‎Kubernetes @ FIXME

2021-07-26T07:28:56Z

‎Certificate expiration

2021-07-18T21:56:43Z

‎Certificate expiration

2021-07-15T08:43:34Z

2020-11-03T23:41:02Z

‎Services

2019-04-09T15:10:38Z

@@ Line 23: / Line 23: @@
 A service is composed of:
-- A deployment
+* A deployment
-- A service
+* A service
-- An ingress controller
+* An ingress controller
 at minimum

@@ Line 20: / Line 20: @@
 ** gitlab: ongoing
-=== Add your own ===
+=== Add your own Service ===
 ==== SSL ====

@@ Line 26: / Line 26: @@
 * We use cert-manager to manage LetsEncrypt certs, you only need to add this annotation to your Ingress Controller for it to manage your cert,
 <pre>
 metadata:
    annotations:
      cert-manager.io/cluster-issuer: letsencrypt
-<pre>
+[...]
 === Debug ===

@@ Line 19: / Line 19: @@
 ** [[MQTT|MQTT gateway]]
 ** gitlab: ongoing
 === Debug ===

@@ Line 20: / Line 20: @@
 ** gitlab: ongoing
-=== Access impossible ===
+=== Debug ===
 Sometimes the eth interface is in the sauce (to investigate), you have to reconfigure it.
@@ Line 38: / Line 39: @@
 </pre>
-=== Certificate expiration ===
+==== Certificate expiration ====
 Sometimes K8S is in the sauce, something like this might help regenerate the certs

@@ Line 25: / Line 25: @@
 <pre>
 systemctl stop kubelet.service
 systemctl restart docker.service
 rsync -av /etc/kubernetes/ /root/kubernetes-$(date +%s)/
 rsync -av /var/lib/etcd/ /root/etcd-$(date +%s)/
@@ Line 37: / Line 39: @@
 rm {apiserver.crt,apiserver-etcd-client.key,apiserver-kubelet-client.crt,front-proxy-ca.crt,front-proxy-client.crt,front-proxy-client.key,front-proxy-ca.key,apiserver-kubelet-client.key,apiserver.key,apiserver-etcd-client.crt}
 cd
 kubeadm init phase certs all --apiserver-advertise-address 62.220.135.205 --ignore-preflight-errors=all
@@ Line 42: / Line 45: @@
 cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
 kubeadm join 62.220.135.205:6443 --token XXX --discovery-token-ca-cert-hash YYY --ignore-preflight-errors=all
 kubectl get nodes
 kubectl get all
 </pre>

← Older revision		Revision as of 08:43, 15 July 2021
Line 19:		Line 19:
	** [[MQTT\|MQTT gateway]]		** [[MQTT\|MQTT gateway]]
	** gitlab: ongoing		** gitlab: ongoing
		+
		+	=== Certificate expiration ===
		+
		+	Sometimes K8S is in the sauce, something like this might help regenerate the certs
		+
		+	<pre>
		+	systemctl stop kubelet.service
		+	systemctl restart docker.service
		+
		+	rsync -av /etc/kubernetes/ /root/kubernetes-$(date +%s)/
		+	rsync -av /var/lib/etcd/ /root/etcd-$(date +%s)/
		+
		+	cd /etc/kubernetes
		+	rm {admin.conf,controller-manager.conf,kubelet.conf,scheduler.conf}
		+
		+	cd /etc/kubernetes/pki
		+	rm {apiserver.crt,apiserver-etcd-client.key,apiserver-kubelet-client.crt,front-proxy-ca.crt,front-proxy-client.crt,front-proxy-client.key,front-proxy-ca.key,apiserver-kubelet-client.key,apiserver.key,apiserver-etcd-client.crt}
		+
		+	cd
		+	kubeadm init phase certs all --apiserver-advertise-address 62.220.135.205 --ignore-preflight-errors=all
		+	kubeadm init phase kubeconfig all
		+	cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
		+
		+	kubeadm join 62.220.135.205:6443 --token XXX --discovery-token-ca-cert-hash YYY --ignore-preflight-errors=all
		+	kubectl get nodes
		+	kubectl get all
		+	</pre>

@@ Line 15: / Line 15: @@
 ** [[Power|Power monitoring]]
 ** Fablab wiki
-** [[Control|Led API endpoint]]
+** [[LED_Lighting|Led API endpoint]]
 ** [[Trigger]]
 ** [[MQTT|MQTT gateway]]