mrichardson03 / sample-aws Goto Github PK

Kubernetes 1.23 needs the Amazon EBS-CSI driver installed, or it can't create persistent volumes.

Certain resources that need unique names are leaving leftovers after failed tests, causing later CI runs to fail (that should have succeeded) due to not being able to create a resource with that name.

Resources that need names generated:

• Instance profile
• Budget name

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: .github/renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid schedule: 'Invalid schedule: Failed to parse "schedule:monthly"'

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update helm release jenkins to v4.3.28
• chore(deps): update pre-commit hook antonbabenko/pre-commit-terraform to v1.81.0
• chore(deps): update terraform aws to ~> 5.4.0
• chore(deps): update terraform terraform-aws-modules/s3-bucket/aws to ~> 3.14.0
• chore(deps): update terraform terraform-aws-modules/security-group/aws to ~> 5.1.0

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

https://aws.amazon.com/about-aws/whats-new/2022/12/amazon-s3-automatically-enable-block-public-access-disable-access-control-lists-buckets-april-2023/

Policy migration guide:
https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-ownership-migrating-acls-prerequisites.html#migrate-acl-permissions-bucket-policies

CI jobs are failing when trying to deploy the Helm release and Kubernetes manifest. Logs are showing an i/o timeout:

Error: Post "https://21085EA8FBC406133DE3F0792256CBA5.yl4.us-east-1.eks.amazonaws.com/apis/rbac.authorization.k8s.io/v1/clusterrolebindings": dial tcp 18.211.52.163:443: i/o timeout

Deploying both with the same plan seems to be too problematic, even with using depends_on = [module.eks.cluster_id], which is supposed to not return until the cluster is fully ready, or other workarounds.