Difference between revisions of "EKS Best Practices Guides"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
* [[K8s security]]: <code>[[hardeneks]]</code> | * [[K8s security]]: <code>[[hardeneks]]</code> | ||
* [[KICS]] | * [[KICS]] | ||
| − | * [[Datree]] | + | * [[Datree]] [[kubectl plugin]] |
== See also == | == See also == | ||
Revision as of 15:56, 27 February 2024
- Security: https://github.com/kubernetes/sig-security/blob/main/sig-security-external-audit/security-audit-2019/findings/Kubernetes%20White%20Paper.pdf
- Networking: https://aws.github.io/aws-eks-best-practices/networking/index/
- Karpenter: https://aws.github.io/aws-eks-best-practices/karpenter/
Related
- Amazon EKS Workshop
- AWS Well-Architected Framework
- ECS best practices
- K8s security:
hardeneks - KICS
- Datree kubectl plugin
See also
- EKS Best Practices
- EKS,
eksctl, EKS add-ons, Amazon EKS cluster role, Terraform EKS, Kubernetes Autoscaler, Karpenter, Terraform module: EKS, Terraform resource: aws eks node group, Terraform data source: aws_eks_cluster, AWS Controllers for Kubernetes, AWS Load Balancer Controller, Amazon EKS Anywhere, Kustomize,aws-iam-authenticator, ACK, tEKS, Amazon EKS authorization, Amazon EKS authentication, Nodegroup, EKS storage,aws-ebs-csi-driver, aws-efs-csi-driver, aws-load-balancer-controller, amazon-vpc-cni-k8s, EKS security, EKS Best Practices Guides,hardeneks, EKS versions,fargate-scheduler,eks-connector, Resilience in Amazon EKS, EKS control plane logging, Security groups for Pods in EKS
Advertising:
