EKS Installer deploys a production-grade SIGHUP Distribution on Amazon Elastic Kubernetes Services (EKS).
If you are new to SIGHUP Distribution please refer to the official documentation on how to get started.
The installer is composed of three terraform modules:
| Module | Description |
|---|---|
| VPC | Deploy the necessary networking infrastructure |
| VPN | Deploy the a VPN Server to connect to private clusters |
| EKS | Deploy the EKS cluster |
Click on each module to see its full documentation.
Caution
Starting from kubernetes 1.33 amy type alinux2 will not be available anymore as specified in the chapter for kubernetes 1.33 in Review release notes for Kubernetes versions on standard support
The EKS module deploys an EKS cluster.
The VPC module setups all the necessary networking infrastructure. The VPN module setups one or more bastion hosts with an OpenVPN server.
The bastion host includes an OpenVPN instance easily manageable by using furyagent to provide access to the cluster.
🕵🏻♂️ Furyagent is a tool developed by SIGHUP to manage OpenVPN and SSH user access to the bastion host.
⚠️ WARNING: if you are upgrading from v1.9.x to v1.10.0, please read the upgrade guide first.
- AWS Access Credentials of an AWS Account with the following IAM permissions.
- terraform
>=1.3.0 sshor OpenVPN Client - Tunnelblick (on macOS) or OpenVPN Connect (for other OS) are recommended.
To create the cluster via the installers:
-
Use the VPC module to deploy the networking infrastructure
-
(optional) Use the VPN module to deploy the openvpn bastion host
-
(optional) Configure access to the OpenVPN instance of the bastion host via furyagent
-
(optional) Connect to the OpenVPN instance
-
Use the EKS module to deploy the EKS cluster
Please refer to each module documentation and the examples folder for more details.
You can follow the SD on EKS quick start guide for a more detailed walkthrough
Warning
The installer-eks versions prior to 3.2.1 are incompatible with self-managed nodes using the alinux2023 AMI type. This issue occurs because Amazon Linux 2023-based EKS AMIs have deprecated the bootstrap.sh script in favor of the new nodeadm system for node initialization.
Temporary Workaround: If you must use older installer-eks versions with self-managed nodes, we recommend using the alinux2 AMI type instead.
- EKS pricing
- Reserved EC2 Instances
- Managing users or IAM roles for your cluster
- Create a kubeconfig for Amazon EKS
- Tagging your Amazon EKS resources
In case you experience any problem with the module, please open a new issue.
This module is open-source and it's released under the following LICENSE