Kubernetes - Revision history

Busk at 20:38, 29 July 2019

2019-07-29T20:38:18Z

Busk at 23:47, 25 July 2019

2019-07-25T23:47:51Z

Busk at 21:37, 25 July 2019

2019-07-25T21:37:15Z

Busk at 21:31, 25 July 2019

2019-07-25T21:31:17Z

Busk at 19:52, 24 July 2019

2019-07-24T19:52:51Z

Busk at 16:39, 24 July 2019

2019-07-24T16:39:30Z

Busk at 22:36, 21 July 2019

2019-07-21T22:36:09Z

Busk at 21:30, 21 July 2019

2019-07-21T21:30:08Z

Busk at 19:38, 21 July 2019

2019-07-21T19:38:50Z

Busk at 18:41, 21 July 2019

2019-07-21T18:41:26Z

← Older revision		Revision as of 20:38, 29 July 2019
Line 16:		Line 16:

	# Install 1		# Install 1
		+
		+	https://kubernetes.io/docs/setup/production-environment/container-runtimes/

	https://medium.com/@zhimin.wen/gitlab-on-onprem-kubernetes-icp-3-1-b06dcd09df7c		https://medium.com/@zhimin.wen/gitlab-on-onprem-kubernetes-icp-3-1-b06dcd09df7c

← Older revision		Revision as of 23:47, 25 July 2019
Line 6:		Line 6:

	https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/		https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/
		+
		+	https://www.digitalocean.com/community/tutorials/how-to-inspect-kubernetes-networking

	# Working		# Working

← Older revision		Revision as of 21:37, 25 July 2019
Line 4:		Line 4:

	https://kubernetes.io/docs/reference/kubectl/cheatsheet/		https://kubernetes.io/docs/reference/kubectl/cheatsheet/
		+
	https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/		https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/

← Older revision		Revision as of 21:31, 25 July 2019
Line 3:		Line 3:
	# Best		# Best

		+	https://kubernetes.io/docs/reference/kubectl/cheatsheet/
	https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/		https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/

← Older revision		Revision as of 19:52, 24 July 2019
Line 92:		Line 92:
	* https://kubedex.com/local-kubernetes/		* https://kubedex.com/local-kubernetes/
	* https://cloudowski.com/articles/10-differences-between-openshift-and-kubernetes/		* https://cloudowski.com/articles/10-differences-between-openshift-and-kubernetes/
		+
		+	# Firewall
		+
		+	https://docs.oracle.com/cd/E52668_01/E88884/html/kube_admin_config_iptables.html
		+	```
		+	Kubernetes and iptables Rules
		+	Kubernetes uses iptables to handle many networking and port forwarding rules. Be careful of using services that may create conflicting iptables rules. You can check the rules by running iptables-save, which dumps the rule set to STDOUT.
		+
		+	If you intend to expose application services externally, by either using the NodePort or LoadBalancing service types, traffic forwarding must be enabled in your iptables rule set. If you find that you are unable to access a service from outside of the network used by the pod where your application is running, check that your iptables rule set does not contain a rule similar to the following:
		+
		+	:FORWARD DROP [0:0]
		+	If you have a rule to drop all forwarding traffic, you may need to run:
		+
		+	# iptables -P FORWARD ACCEPT
		+	If you are running iptables as a service instead of firewalld, you can save current iptables configuration so that it is persistent across reboots. To do this, run:
		+
		+	# iptables-save > /etc/sysconfig/iptables
		+	Note that you must have the iptables-services package installed for this to work. Oracle recommends using the default firewalld service as this provides a more consistent experience and allows you to make changes to the firewall configuration without flushing existing rules and reloading the firewall.
		+
		+	Nodes running applications that need to communicate directly between pods and that are IP aware, may require additional custom iptables configuration to bypass the default firewalld masquerading rules. For example, setting these two iptables rules on the nodes running a server application on IP address 192.0.2.15 and a client application on IP address 192.0.2.16 enables direct communication between them:
		+
		+	# iptables -t nat -I POST_public_allow -s 192.0.2.15/32 -d 192.0.2.16/32 -j RETURN
		+	# iptables -t nat -I POST_public_allow -s 192.0.2.16/32 -d 192.0.2.15/32 -j RETURN
		+	```

← Older revision		Revision as of 16:39, 24 July 2019
Line 1:		Line 1:
	You have two basic general flavors. Kubernetes and OKD (used to be OpenShift Origin). OKD uses HAProxy for routes while Kubernetes uses ingress and supports a bunch of different reverse proxy mechanisms including nginx. I think Kubernetes is developed enough over the last couple of years that it is a good option, maybe even better than openshift. Ubuntu Kubernetes is probably the best fit for now over kubeadm and other options.		You have two basic general flavors. Kubernetes and OKD (used to be OpenShift Origin). OKD uses HAProxy for routes while Kubernetes uses ingress and supports a bunch of different reverse proxy mechanisms including nginx. I think Kubernetes is developed enough over the last couple of years that it is a good option, maybe even better than openshift. Ubuntu Kubernetes is probably the best fit for now over kubeadm and other options.
		+
		+	# Best
		+
		+	https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/

	# Working		# Working

← Older revision		Revision as of 22:36, 21 July 2019
Line 4:		Line 4:

	https://github.com/kubernetes/ingress-nginx/tree/master/docs/examples/static-ip		https://github.com/kubernetes/ingress-nginx/tree/master/docs/examples/static-ip
		+
		+	https://docs.gitlab.com/ee/user/project/clusters/

	# Install 1		# Install 1

← Older revision		Revision as of 21:30, 21 July 2019
Line 1:		Line 1:
	You have two basic general flavors. Kubernetes and OKD (used to be OpenShift Origin). OKD uses HAProxy for routes while Kubernetes uses ingress and supports a bunch of different reverse proxy mechanisms including nginx. I think Kubernetes is developed enough over the last couple of years that it is a good option, maybe even better than openshift. Ubuntu Kubernetes is probably the best fit for now over kubeadm and other options.		You have two basic general flavors. Kubernetes and OKD (used to be OpenShift Origin). OKD uses HAProxy for routes while Kubernetes uses ingress and supports a bunch of different reverse proxy mechanisms including nginx. I think Kubernetes is developed enough over the last couple of years that it is a good option, maybe even better than openshift. Ubuntu Kubernetes is probably the best fit for now over kubeadm and other options.
		+
		+	# Working
		+
		+	https://github.com/kubernetes/ingress-nginx/tree/master/docs/examples/static-ip

	# Install 1		# Install 1

← Older revision		Revision as of 19:38, 21 July 2019
Line 1:		Line 1:
	You have two basic general flavors. Kubernetes and OKD (used to be OpenShift Origin). OKD uses HAProxy for routes while Kubernetes uses ingress and supports a bunch of different reverse proxy mechanisms including nginx. I think Kubernetes is developed enough over the last couple of years that it is a good option, maybe even better than openshift. Ubuntu Kubernetes is probably the best fit for now over kubeadm and other options.		You have two basic general flavors. Kubernetes and OKD (used to be OpenShift Origin). OKD uses HAProxy for routes while Kubernetes uses ingress and supports a bunch of different reverse proxy mechanisms including nginx. I think Kubernetes is developed enough over the last couple of years that it is a good option, maybe even better than openshift. Ubuntu Kubernetes is probably the best fit for now over kubeadm and other options.

		+	# Install 1
		+
		+	https://medium.com/@zhimin.wen/gitlab-on-onprem-kubernetes-icp-3-1-b06dcd09df7c

	# Getting Started with Calico as network control plane		# Getting Started with Calico as network control plane

← Older revision		Revision as of 18:41, 21 July 2019
Line 3:		Line 3:

	# Getting Started with Calico as network control plane		# Getting Started with Calico as network control plane
		+
		+	https://docs.projectcalico.org/v3.8/getting-started/

	## Install		## Install