Add EKS module

Author: burmek

.terraform.lock.hcl

@@ -0,0 +1 @@
+Subproject commit b6fa04f65bdcb26869215fb840f5ee088a096bc8

.terraform/modules/eks_deployment.eks

@@ -0,0 +1 @@
+Subproject commit b026981f6b80240f8d22ca7ebcee61d67d1e9256

.terraform/modules/eks_deployment.eks.kms

@@ -0,0 +1 @@
+Subproject commit 80bd3b92e0f82f45a187805d6d847db320a01c31

.terraform/modules/eks_deployment.eks_blueprints_kubernetes_addons

@@ -0,0 +1 @@
+Subproject commit bf6d1f68eee97052cac105563bebf19a5e6f4512

.terraform/modules/eks_deployment.eks_blueprints_kubernetes_addons.portworx

@@ -0,0 +1,18 @@
+# Who is using EKS Blueprints for Terraform?
+
+EKS Blueprints for Terraform has a variety of users and use cases to configure and manage complete EKS clusters that are fully bootstrapped with the operational software that is needed to deploy and operate kubernetes workloads.
+Many customers want to learn from others who have already implemented EKS Blueprints for Terraform in their environments.
+
+The following is a self-reported list of users to help identify adoption and points of contact.
+
+## Add yourself
+
+If you are using EKS Blueprints for Terraform please consider adding yourself as a user by opening a pull request to this file.
+
+## Adopters (Alphabetical)
+
+| Organization | Description | Contacts | Link |
+| --- | --- | --- | --- |
+| PITS Global Data Recovery Services | PITS Global Data Recovery Services is a leading global recovery company based in the United States. With a team of highly skilled and experienced data recovery experts, we are dedicated to providing top-notch data recovery services to businesses and individuals across the country. Our team understands how critical data is and takes pride in recovering lost, corrupted, or deleted files quickly and effectively. Regardless of the data loss scenario, our team of experts has the tools and expertise to get your data back.| [email protected] | https://www.pitsdatarecovery.net/ |
+| AlgoDx AB | At AlgoDx, we are dedicated to developing and implementing clinically validated ML-based clinical decision support software that save lives and reduce costs in healthcare, primarily targeting intensive and critical care. We achieve this through the integration of our state-of-the-art AI precision medicine platform with health systems’ electronic medical records. | [email protected], [email protected] | https://www.algodx.com/ |
+| Swyft Logistics | Swyft is an award-winning, tech-enabled last-mile e-Parcel delivery service provider, primarily operating in the fashion, electronics, and personal care industries. Swyft aspires to reinvent logistics in Pakistan and connecting people beyond possibilities. Our focus is on innovation, development of technologies and processes. | [email protected], [email protected], [email protected],   | https://www.swyftlogistics.com/ |

.terraform/modules/eks_deployment.eks_blueprints_kubernetes_addons.portworx.helm_addon/ADOPTERS.md

@@ -0,0 +1 @@
+* @aws-ia/internal-terraform-eks-admins

.terraform/modules/eks_deployment.eks_blueprints_kubernetes_addons.portworx.helm_addon/CODEOWNERS

@@ -0,0 +1,4 @@
+## Code of Conduct
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+[email protected] with any additional questions or comments.

.terraform/modules/eks_deployment.eks_blueprints_kubernetes_addons.portworx.helm_addon/CODE_OF_CONDUCT.md

@@ -0,0 +1,57 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
+documentation, we greatly value feedback and contributions from our community.
+
+Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
+information to effectively respond to your bug report or contribution.
+
+## Reporting Bugs/Feature Requests
+
+We welcome you to use the GitHub issue tracker to report bugs or suggest features.
+
+When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
+reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
+
+- A reproducible test case or series of steps
+- The version of our code being used
+- Any modifications you've made relevant to the bug
+- Anything unusual about your environment or deployment
+
+## Contributing via Pull Requests
+
+Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
+
+1. You are working against the latest source on the _main_ branch.
+2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
+3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
+
+To send us a pull request, please:
+
+1. Fork the repository.
+2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
+3. Ensure local tests pass.
+4. Commit to your fork using clear commit messages.
+5. Send us a pull request, answering any default questions in the pull request interface.
+6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
+
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
+
+## Finding contributions to work on
+
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
+
+## Code of Conduct
+
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+[email protected] with any additional questions or comments.
+
+## Security issue notifications
+
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
+
+## Licensing
+
+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.