Kubernetes/Amazon EKS - Revision history

Pio2pio: /* Cluster Autoscaler (CA) */

2021-06-08T01:37:53Z

Cluster Autoscaler (CA)

← Older revision		Revision as of 03:37, 8 June 2021
Line 959:		Line 959:
	=== [https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md Cluster Autoscaler] (CA) ===		=== [https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md Cluster Autoscaler] (CA) ===
	Complimentary projects:		Complimentary projects:
	* [https://github.com/kubernetes-sigs/descheduler descheduler]		* [https://github.com/awslabs/karpenter awslabs/karpenter] [https://www.twitch.tv/videos/1010593737?t=141m50s Video]
			* [https://github.com/kubernetes-sigs/descheduler kubernetes-sigs/descheduler]
	* [https://github.com/kube-aws/kube-spot-termination-notice-handler kube-spot-termination-notice-handler], [https://github.com/helm/charts/tree/master/stable/k8s-spot-termination-handler helm] - watches only spot notifications and then drains the node it's running on		* [https://github.com/kube-aws/kube-spot-termination-notice-handler kube-spot-termination-notice-handler], [https://github.com/helm/charts/tree/master/stable/k8s-spot-termination-handler helm] - watches only spot notifications and then drains the node it's running on
	* [https://github.com/aws/aws-node-termination-handler aws-node-termination-handler] - handles more events but requires EventBridge and SQS		* [https://github.com/aws/aws-node-termination-handler aws-node-termination-handler] - handles more events but requires EventBridge and SQS

Pio2pio: /* Cluster Autoscaler (CA) */

2020-10-24T10:40:07Z

Cluster Autoscaler (CA)

← Older revision		Revision as of 12:40, 24 October 2020
Line 960:		Line 960:
	Complimentary projects:		Complimentary projects:
	* [https://github.com/kubernetes-sigs/descheduler descheduler]		* [https://github.com/kubernetes-sigs/descheduler descheduler]
	* [https://github.com/kube-aws/kube-spot-termination-notice-handler kube-spot-termination-notice-handler], [https://github.com/helm/charts/tree/master/stable/k8s-spot-termination-handler helm]		* [https://github.com/kube-aws/kube-spot-termination-notice-handler kube-spot-termination-notice-handler], [https://github.com/helm/charts/tree/master/stable/k8s-spot-termination-handler helm] - watches only spot notifications and then drains the node it's running on
	* [https://github.com/aws/aws-node-termination-handler aws-node-termination-handler] - handles more events but requires EventBridge and SQS		* [https://github.com/aws/aws-node-termination-handler aws-node-termination-handler] - handles more events but requires EventBridge and SQS
	* [https://github.com/pusher/k8s-spot-rescheduler k8s-spot-rescheduler] move nodes from on-demand instances to spot instances when space is available.		* [https://github.com/pusher/k8s-spot-rescheduler k8s-spot-rescheduler] move nodes from on-demand instances to spot instances when space is available.

Pio2pio: /* Cluster Autoscaler (CA) */

2020-10-24T10:39:19Z

Cluster Autoscaler (CA)

← Older revision		Revision as of 12:39, 24 October 2020
Line 960:		Line 960:
	Complimentary projects:		Complimentary projects:
	* [https://github.com/kubernetes-sigs/descheduler descheduler]		* [https://github.com/kubernetes-sigs/descheduler descheduler]
	* [https://github.com/kube-aws/kube-spot-termination-notice-handler] kube-spot-termination-notice-handler, [https://github.com/helm/charts/tree/master/stable/k8s-spot-termination-handler helm]		* [https://github.com/kube-aws/kube-spot-termination-notice-handler kube-spot-termination-notice-handler], [https://github.com/helm/charts/tree/master/stable/k8s-spot-termination-handler helm]
	* [https://github.com/aws/aws-node-termination-handler aws-node-termination-handler] - handles more events but requires EventBridge and SQS		* [https://github.com/aws/aws-node-termination-handler aws-node-termination-handler] - handles more events but requires EventBridge and SQS
	* [https://github.com/pusher/k8s-spot-rescheduler k8s-spot-rescheduler] move nodes from on-demand instances to spot instances when space is available.		* [https://github.com/pusher/k8s-spot-rescheduler k8s-spot-rescheduler] move nodes from on-demand instances to spot instances when space is available.

Pio2pio: /* Cluster Autoscaler (CA) */

2020-10-24T10:38:58Z

Cluster Autoscaler (CA)

Show changes

Pio2pio: /* aws-auth | Managing users or IAM roles for your cluster */

2020-09-29T23:24:45Z

aws-auth | Managing users or IAM roles for your cluster

← Older revision		Revision as of 01:24, 30 September 2020
Line 337:		Line 337:
	== aws-auth \| [https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html Managing users or IAM roles for your cluster] ==		== aws-auth \| [https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html Managing users or IAM roles for your cluster] ==
	* [https://stackoverflow.com/questions/54258516/can-kubectl-work-from-an-assumed-role-from-aws kubectl work from an assumed role from AWS]		* [https://stackoverflow.com/questions/54258516/can-kubectl-work-from-an-assumed-role-from-aws kubectl work from an assumed role from AWS]
	<~~source~~ lang=yaml>		<syntaxhighlightjs lang=yaml>
	# kubectl -n kube-system edit aws-auth		# kubectl -n kube-system edit aws-auth
	apiVersion: v1		apiVersion: v1
Line 355:		Line 355:
	groups:		groups:
	- system:masters		- system:masters
	</~~source~~>		</syntaxhighlightjs>
	The 'username' can actually be set to about anything. It appears to only be important if there are custom roles and bindings added to your EKS cluster.		The 'username' can actually be set to about anything. It appears to only be important if there are custom roles and bindings added to your EKS cluster.

Pio2pio: /* Managing users or IAM roles for your cluster aka aws-auth */

2020-09-29T23:23:52Z

Managing users or IAM roles for your cluster aka aws-auth

← Older revision		Revision as of 01:23, 30 September 2020
Line 335:		Line 335:


	== [https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html Managing users or IAM roles for your cluster] ~~aka aws-auth~~ ==		== aws-auth \| [https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html Managing users or IAM roles for your cluster] ==
	* [https://stackoverflow.com/questions/54258516/can-kubectl-work-from-an-assumed-role-from-aws kubectl work from an assumed role from AWS]		* [https://stackoverflow.com/questions/54258516/can-kubectl-work-from-an-assumed-role-from-aws kubectl work from an assumed role from AWS]
	<source lang=yaml>		<source lang=yaml>

Pio2pio: /* = Managing users or IAM roles for your cluster aka aws-auth */

2020-09-29T23:23:17Z

= Managing users or IAM roles for your cluster aka aws-auth

← Older revision		Revision as of 01:23, 30 September 2020
Line 335:		Line 335:


	== [https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html Managing users or IAM roles for your cluster] aka aws-auth =		== [https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html Managing users or IAM roles for your cluster] aka aws-auth ==
	* [https://stackoverflow.com/questions/54258516/can-kubectl-work-from-an-assumed-role-from-aws kubectl work from an assumed role from AWS]		* [https://stackoverflow.com/questions/54258516/can-kubectl-work-from-an-assumed-role-from-aws kubectl work from an assumed role from AWS]
	<source lang=yaml>		<source lang=yaml>

Pio2pio: /* Authentication mapping IAM users and roles to K8s groups */

2020-09-29T23:22:47Z

Authentication mapping IAM users and roles to K8s groups

← Older revision		Revision as of 01:22, 30 September 2020
Line 335:		Line 335:


	== ~~Authentication mapping~~ IAM ~~users and~~ roles ~~to K8s groups =~~=		== [https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html Managing users or IAM roles for your cluster] aka aws-auth =
	* [https://stackoverflow.com/questions/54258516/can-kubectl-work-from-an-assumed-role-from-aws kubectl work from an assumed role from AWS]		* [https://stackoverflow.com/questions/54258516/can-kubectl-work-from-an-assumed-role-from-aws kubectl work from an assumed role from AWS]
	<source lang=yaml>		<source lang=yaml>
			# kubectl -n kube-system edit aws-auth
	apiVersion: v1		apiVersion: v1
	kind: ConfigMap		kind: ConfigMap
Line 356:		Line 357:
	</source>		</source>
	The 'username' can actually be set to about anything. It appears to only be important if there are custom roles and bindings added to your EKS cluster.		The 'username' can actually be set to about anything. It appears to only be important if there are custom roles and bindings added to your EKS cluster.

	== Create admin user and roles ==		== Create admin user and roles ==
	Create administrative account and role binding		Create administrative account and role binding

Pio2pio: /* Create admin user and roles */

2020-09-29T23:21:26Z

Create admin user and roles

@@ Line 335: / Line 335: @@
 == Create admin user and roles ==
 Create administrative account and role binding
@@ Line 369: / Line 390: @@
 kubectl edit -n kube-system configmap/aws-auth
 </source>
 == Access the dashboard ==
 When running from local machine (laptop) proxy is required, [https://kubernetes.io/docs/tasks/access-kubernetes-api/http-proxy-access-api/ read more...]

Pio2pio: /* Helm - charts (refers to helm2) */

2020-09-13T14:26:02Z

Helm - charts (refers to helm2)

Show changes