このページは、まだ日本語ではご利用いただけません。翻訳中です。
旧バージョンのドキュメントを参照しています。 最新のドキュメントはこちらをご参照ください。
Kong Ingress on Elastic Kubernetes Service (EKS)
Requirements
- A fully functional EKS cluster. Please follow Amazon’s Guide to set up an EKS cluster.
- Basic understanding of Kubernetes
- A working
kubectl
linked to the EKS Kubernetes cluster we will work on. The above EKS setup guide will help you set this up.
Deploy the Kong Ingress Controller
You can deploy the Kong Ingress Controller using kubectl
or Helm
:
The results should look like this:
Note: this process could take up to five minutes the first time.
Setup environment variables
Next, create an environment variable with the IP address at which Kong is accessible. This IP address sends requests to the Kubernetes cluster.
Execute the following command to get the IP address at which Kong is accessible:
$ kubectl get services -n kong
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kong-proxy LoadBalancer 10.63.250.199 example.eu-west-1.elb.amazonaws.com 80:31929/TCP,443:31408/TCP 57d
Create an environment variable to hold the ELB hostname:
$ export PROXY_IP=$(kubectl get -o jsonpath="{.status.loadBalancer.ingress[0].hostname}" service -n kong kong-proxy)
Note: It may take some time for Amazon to actually associate the IP address to the
kong-proxy
Service.
Once you’ve installed the Kong Ingress Controller, please follow our getting started tutorial to learn about how to use the Ingress Controller.
TLS configuration
Versions of Kong prior to 2.0.0 default to using the “modern” cipher suite list. This is not compatible with ELBs when the ELB terminates TLS at the edge and establishes a new session with Kong. This error will appear in Kong’s logs:
*7961 SSL_do_handshake() failed (SSL: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher) while SSL handshaking
To correct this issue, set KONG_SSL_CIPHER_SUITE=intermediate
in your
environment variables.