aws-eks-base VS terraform-equinix-metal-eks-anywhere

Compare aws-eks-base vs terraform-equinix-metal-eks-anywhere and see what are their differences.

aws-eks-base

This boilerplate contains terraform configurations for the rapid deployment of a Kubernetes cluster, supporting services, and the underlying infrastructure in AWS. (by maddevsio)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
aws-eks-base terraform-equinix-metal-eks-anywhere
7 1
619 8
0.3% -
5.1 5.3
26 days ago 4 months ago
HCL HCL
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

aws-eks-base

Posts with mentions or reviews of aws-eks-base. We have used some of these posts to build our list of alternatives and similar projects.

terraform-equinix-metal-eks-anywhere

Posts with mentions or reviews of terraform-equinix-metal-eks-anywhere. We have used some of these posts to build our list of alternatives and similar projects.
  • Setting up EKS-Anywhere cluster on Baremetal servers in Equinix
    1 project | dev.to | 12 Jan 2023
    root@ip-172-31-86-91:~# git clone https://github.com/equinix-labs/terraform-equinix-metal-eks-anywhere.git root@ip-172-31-86-91:~# cd terraform-equinix-metal-eks-anywhere/ root@ip-172-31-86-91:~/terraform-equinix-metal-eks-anywhere# ls LICENSE README.md hardware.csv.tftpl locals.tf main.tf outputs.tf reboot_nodes.sh setup.cloud-init.tftpl variables.tf versions.tf root@ip-172-31-86-91:~/terraform-equinix-metal-eks-anywhere# terraform init Initializing the backend... Initializing provider plugins... - Finding latest version of hashicorp/local... .... <<<<<<<<<>>>>>>>>>> Terraform has been successfully initialized! root@ip-172-31-86-91:~/terraform-equinix-metal-eks-anywhere# terraform apply var.metal_api_token Equinix Metal user api token Enter a value: Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create Terraform will perform the following actions: .... <<<<<<<<<>>>>>>>>>> Plan: 19 to add, 0 to change, 0 to destroy. Changes to Outputs: + eksa_admin_ip = (known after apply) + eksa_admin_ssh_key = (known after apply) + eksa_admin_ssh_user = "root" + eksa_nodes_sos = { + "eksa-node-cp-001" = (known after apply) + "eksa-node-dp-001" = (known after apply) } Do you want to perform these actions? Terraform will perform the actions described above. Only 'yes' will be accepted to approve. Enter a value: yes tls_private_key.ssh_key_pair: Creating... equinix_metal_reserved_ip_block.public_ips: Creating... equinix_metal_vlan.provisioning_vlan: Creating... random_string.ssh_key_suffix: Creating... random_string.ssh_key_suffix: Creation complete after 0s [id=842] equinix_metal_vlan.provisioning_vlan: Creation complete after 1s [id=7bd3984e-f21b-45db-882c-dd6a5a1c72d0] equinix_metal_reserved_ip_block.public_ips: Creation complete after 1s [id=45d5c21e-d245-4a4f-95bc-94cdd92dad47] equinix_metal_device.eksa_node_cp[0]: Creating... equinix_metal_gateway.gw: Creating... equinix_metal_device.eksa_node_dp[0]: Creating... tls_private_key.ssh_key_pair: Creation complete after 2s [id=618e4bbec2485418706ef809fbfdfededa470fdd] local_file.ssh_private_key: Creating... equinix_metal_ssh_key.ssh_pub_key: Creating... local_file.ssh_private_key: Creation complete after 0s [id=df7ff74bc7f4b8a64597ae8f22ee91650d8eb7b7] equinix_metal_gateway.gw: Creation complete after 1s [id=3454fa91-8163-44a3-8230-433db5d54358] equinix_metal_ssh_key.ssh_pub_key: Creation complete after 0s [id=4eae18dc-2c56-4fab-86f5-463c7a1e702e] equinix_metal_device.eksa_admin: Creating... equinix_metal_device.eksa_node_cp[0]: Still creating... [10s elapsed] equinix_metal_device.eksa_node_dp[0]: Still creating... [10s elapsed] .... <<<<<<<<<>>>>>>>>>> null_resource.create_cluster: Still creating... [10m20s elapsed] null_resource.create_cluster (remote-exec): Installing EKS-A secrets on workload cluster null_resource.create_cluster (remote-exec): Installing resources on management cluster null_resource.create_cluster (remote-exec): Moving cluster management from bootstrap to workload cluster null_resource.create_cluster: Still creating... [10m30s elapsed] null_resource.create_cluster (remote-exec): Installing EKS-A custom components (CRD and controller) on workload cluster null_resource.create_cluster: Still creating... [10m40s elapsed] null_resource.create_cluster (remote-exec): Installing EKS-D components on workload cluster null_resource.create_cluster (remote-exec): Creating EKS-A CRDs instances on workload cluster null_resource.create_cluster: Still creating... [10m50s elapsed] null_resource.create_cluster (remote-exec): Installing AddonManager and GitOps Toolkit on workload cluster null_resource.create_cluster (remote-exec): GitOps field not specified, bootstrap flux skipped null_resource.create_cluster (remote-exec): Writing cluster config file null_resource.create_cluster (remote-exec): Deleting bootstrap cluster null_resource.create_cluster (remote-exec): πŸŽ‰ Cluster created! null_resource.create_cluster: Creation complete after 10m53s [id=2497544909566343714] Apply complete! Resources: 19 added, 0 changed, 0 destroyed. Outputs: eksa_admin_ip = "111.222.333.444" eksa_admin_ssh_key = "/root/.ssh/my-eksa-cluster-842" eksa_admin_ssh_user = "root" eksa_nodes_sos = tomap({ "eksa-node-cp-001" = "8a3418c8-11fb-4aa7-9c39-0588ed8beb0f@sos.sv15.platformequinix.com" "eksa-node-dp-001" = "197829ca-972c-4e68-8ef4-e5fb85f3df83@sos.sv15.platformequinix.com" }) root@ip-172-31-86-91:~/terraform-equinix-metal-eks-anywhere#

What are some alternatives?

When comparing aws-eks-base and terraform-equinix-metal-eks-anywhere you can also consider the following projects:

terraform-aws-vpc-peering - Terraform module to create a peering connection between two VPCs in the same AWS account.

terraform-aws-eks-node-group - Terraform module to provision a fully managed AWS EKS Node Group

terraform-aws-dms - Terraform module to create AWS DMS (Database Migration Service) resources πŸ‡ΊπŸ‡¦

terraform-aws-eks-blueprints-teams - Configure and deploy Team based multi-tenant EKS clusters.

todo-app-infra - Repository contains example application with PaaS, SaaS & IaaS

terraform-aws-eks-cluster - Terraform module for provisioning an EKS cluster

terraform-aws-route53 - Terraform module to create AWS Route53 resources πŸ‡ΊπŸ‡¦

learn-terraform-provision-eks-cluster

terraform-aws-metaflow - Deploy production-grade Metaflow cloud infrastructure on AWS

terraform-aws-eks-blueprints - Configure and deploy complete EKS clusters.

eks-tf-gitops - A fully functional and secure EKS cluster provisioned with Terraform and powered by ArgoCD

terraform-aws-eks - Terraform module to create AWS Elastic Kubernetes (EKS) resources πŸ‡ΊπŸ‡¦