Skip to content
This repository has been archived by the owner on Jan 30, 2021. It is now read-only.

Releases: cloudposse-archives/terraform-aws-kops-state-backend

0.3.0: Allow use of existing S3 bucket in other region

02 Jul 23:49
07d134b
Compare
Choose a tag to compare

Allow kops to use an existing S3 bucket in another region for its state store. #14

0.2.0 Add flag to disable public access in `kops` state bucket by default

09 Apr 15:51
Compare
Choose a tag to compare

what

  • Add flag to disable public access in kops state bucket by default

why

  • Security by design

0.1.8

09 Apr 15:31
Compare
Choose a tag to compare
Update route53-cluster-zone to 0.3.1 (#10)

0.1.7: Update terraform-aws-route53-cluster-zone to 0.3.1

06 Apr 18:05
63ad937
Compare
Choose a tag to compare

0.1.6: Update readme yaml file and rebuild md

12 Dec 09:38
2ccc658
Compare
Choose a tag to compare

what

  • updated README.yaml file
  • add tags and categories
  • rebuild README.md file

why

  • need to add categories and tags so we can pull them into the documentation

0.1.5

02 Aug 19:46
7092041
Compare
Choose a tag to compare

what

  • Add domain_enabled flag

why

  • Kops clusters created in gossip mode do not require dns zones
  • Address #6

Migrate to README.yaml format

24 Jul 09:31
0ab96cf
Compare
Choose a tag to compare

what

  • Add README.yaml

why

  • Standardize README

0.1.3

16 Apr 01:02
8c3975a
Compare
Choose a tag to compare

what

  • Change bucket_name to name

why

  • Use common naming conventions to name created resources (e.g. S3 bucket, IAM Role, IAM Policy)

0.1.2

04 Apr 18:56
8efd413
Compare
Choose a tag to compare

what

  • Separate S3 bucket name from Kops cluster name

why

  • Almost always we want to use the bucket name like this cp-prod-kops-state with kops in the name to correctly represent the technology (kops in this case) the bucket is used to store the state for

  • But for the kops cluster names, we want to use a role-based naming convention instead of technology-based, e.g. cluster-1.prod.domain.com or location-based naming convention like us-west-2.prod.domain.com

0.1.1

03 Apr 19:09
78f97dc
Compare
Choose a tag to compare

what

  • Rename repo
  • Update module
  • Update README with examples
  • Add TravisCI

why

  • Use terraform-aws-kops-* naming convention for kops modules
  • Use common conventions for naming resources
  • Cloud Posse README template
  • For terraform lint and monitoring build status

test

image

{
    "ResourceTagSets": [
        {
            "ResourceType": "hostedzone",
            "ResourceId": "Z58RWQWFVU4HT",
            "Tags": [
                {
                    "Key": "Cluster",
                    "Value": "kops.cloudxl.net"
                },
                {
                    "Key": "Stage",
                    "Value": "prod"
                },
                {
                    "Key": "Namespace",
                    "Value": "cp"
                },
                {
                    "Key": "Name",
                    "Value": "cp-prod-kops-state"
                }
            ]
        }
    ]
}