Go to file
Dustin 3916e0eac9 Assign WireGuard keys to EC2 instances
In order to join the on-premises Kubernetes cluster, EC2 instances will
need to first connect to the WireGuard VPN.  The *dynk8s* provisioner
will provide keys to instances to configure their WireGuard clients.

WireGuard keys must be pre-configured on the server and stored in
Kubernetes as *dynk8s.du5t1n.me/wireguard-key* Secret resources.  They
must also have a `dynk8s.du5t1n.me/ec2-instance-id` label.  If this
label is empty, the key is available to be assigned to an instance.

When an EventBridge event is received indicating an instance is now
running, a WireGuard key is assigned to that instance (by setting the
`dynk8s.du5t1n.me/ec2-instance-id` label).  Conversely, when an event is
received indicating that the instance is terminated, any WireGuard keys
assigned to that instance are freed.
2022-10-01 12:17:32 -05:00
ci ci: Begin Jenkins build pipeline 2022-09-10 10:30:54 -05:00
src Assign WireGuard keys to EC2 instances 2022-10-01 12:17:32 -05:00
terraform terraform: Begin AWS configuration 2022-09-27 12:58:51 -05:00
test/data/sns Begin HTTP server, SNS message receiver 2022-09-03 22:58:23 -05:00
.dockerignore ci: Begin Jenkins build pipeline 2022-09-10 10:30:54 -05:00
.editorconfig ci: Begin Jenkins build pipeline 2022-09-10 10:30:54 -05:00
.gitattributes Initial commit 2022-08-31 21:02:17 -05:00
.gitignore sns: Save messages to disk 2022-09-05 09:45:44 -05:00
Cargo.lock Begin EC2 instance state event handler 2022-10-01 10:34:03 -05:00
Cargo.toml Begin EC2 instance state event handler 2022-10-01 10:34:03 -05:00
Containerfile container: Rebase on Fedora 35 2022-09-11 13:17:54 -05:00
rustfmt.toml Initial commit 2022-08-31 21:02:17 -05:00