Skip to content

Commit

Permalink
Merge pull request #225 from mattlandis/eks-1.10
Browse files Browse the repository at this point in the history
Add EKS Kubernetes v1.10 conformance test results
  • Loading branch information
taylorwaggoner committed Jun 5, 2018
2 parents 8737474 + 16adbc4 commit 780d58b
Show file tree
Hide file tree
Showing 5 changed files with 10,290 additions and 0 deletions.
8 changes: 8 additions & 0 deletions v1.10/eks/PRODUCT.yaml
@@ -0,0 +1,8 @@
vendor: Amazon Web Services
name: Amazon Elastic Container Service for Kubernetes (Amazon EKS)
version: v1.10.3
website_url: https://aws.amazon.com/eks/
documentation_url: https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html
product_logo_url: https://s3-us-west-2.amazonaws.com/amazon-eks-docs/EKS.png
type: platform
description: Amazon Elastic Container Service for Kubernetes (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on AWS without needing to install and operate your own Kubernetes clusters.
26 changes: 26 additions & 0 deletions v1.10/eks/README.md
@@ -0,0 +1,26 @@
# Conformance testing Amazon EKS

## Setup EKS Cluster

Setup EKS cluster as per the [EKS documentation](https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html). To run conformance tests, we recommend that you use a cluster that provides sufficient resources - compute, storage as well as network IPs. EKS uses [Amazon VPC CNI plugin](https://github.com/aws/amazon-vpc-cni-k8s) which uses ENIs to provide IP addresses to your Kubernetes pods. Please ensure your worker node instance type provides you sufficient ENI limits. We ran our conformance tests on a cluster with 10 m4.large worker instances.

If using the example vpc and node group templates from the EKS documentation you need to allow outbound traffic on the ControlPlaneSecurityGroup for ports 1-1024 and inbound traffic on the NodeSecurityGroup for the same ports.

## Run conformance tests

Start the conformance tests on your EKS cluster
```
curl -L https://raw.githubusercontent.com/cncf/k8s-conformance/master/sonobuoy-conformance.yaml | kubectl apply -f -
````

You can monitor the conformance tests by tracking the sonobuoy logs. Wait for the line `no-exit was specified, sonobuoy is now blocking`, which signals the end of the testing.

```
kubectl logs -f sonobuoy -n sonobuoy
```

Upon completion of the tests you can obtain the results by copying them off the sonobuoy pod.

```
kubectl cp sonobuoy/sonobuoy:/tmp/sonobuoy ./results
```

0 comments on commit 780d58b

Please sign in to comment.