Skip to content

Commit

Permalink
docs: fixed table of contents
Browse files Browse the repository at this point in the history
  • Loading branch information
msvticket committed Sep 10, 2024
1 parent 774ad01 commit 5627fae
Showing 1 changed file with 1 addition and 5 deletions.
6 changes: 1 addition & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ This repository contains a Terraform module for creating an EKS cluster and all
- [Prerequisites](#prerequisites)
- [Cluster provisioning](#cluster-provisioning)
- [AWS_REGION](#aws_region)
- [Migrating to current version of module from a version prior to 3.0.0](#migrating-to-current-version-of-module-from-a-version-prior-to-300)
- [Cluster Autoscaling](#cluster-autoscaling)
- [Long Term Storage](#long-term-storage)
- [Secrets Management](#secrets-management)
Expand All @@ -30,7 +31,6 @@ This repository contains a Terraform module for creating an EKS cluster and all
- [Outputs](#outputs)
- [FAQ: Frequently Asked Questions](#faq-frequently-asked-questions)
- [IAM Roles for Service Accounts](#iam-roles-for-service-accounts)
- [Development](#development)
- [How can I contribute](#how-can-i-contribute)

<!-- /TOC -->
Expand Down Expand Up @@ -98,8 +98,6 @@ Refer to [Production cluster considerations](#production-cluster-considerations)

### Migrating to current version of module from a version prior to 3.0.0

TODO: Verify that I have covered all of https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1744#issuecomment-1027359982

If you already have created an EKS cluster using a pre 3.0.0 version of this module there is unfortunately no easy
way to upgrade without recreating the cluster. If you already create the cluster in some other way and now set
`create_eks = false` you only n eed to remove some inputs. I won't cover that much simpler case here.
Expand Down Expand Up @@ -532,8 +530,6 @@ This module sets up a series of IAM Policies and Roles. These roles will be anno
This allows us to make use of [IAM Roles for Sercive Accounts](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html) to set fine-grained permissions on a pod per pod basis.
There is no way to provide your own roles or define other Service Accounts by variables, but you can always modify the `modules/cluster/irsa.tf` Terraform file.

## Development

## How can I contribute

Contributions are very welcome! Check out the [Contribution Guidelines](./CONTRIBUTING.md) for instructions.

0 comments on commit 5627fae

Please sign in to comment.