|
| 1 | +CHANGELOG |
| 2 | +--------- |
| 3 | + |
| 4 | +### 0.3.0 - RBAC ! |
| 5 | + |
| 6 | +#### Added |
| 7 | + * It is now possible to create `kops` clusters with RBAC enabled by default |
| 8 | + * etcd volumes are encrypted |
| 9 | + * support for kops ability to disable the automatic creation of security groups |
| 10 | + when creating a LoadBalancer service |
| 11 | + |
| 12 | +#### Fixed |
| 13 | + * During `terraform destroy`, avoid errors that occur in case the cluster has |
| 14 | + already been deleted outside of Terraform |
| 15 | + * Kops cluster domain and your cluster's kube-dns domain are now setup |
| 16 | + accordingly |
| 17 | + |
| 18 | +### 0.2.0 - Add relevant variables and outputs to our kops modules |
| 19 | + |
| 20 | +#### Fixed |
| 21 | + * premature Internet Gateway destroy triggering Terraform errors on destroyed |
| 22 | + (could be worked around by running destroy twice) |
| 23 | + |
| 24 | +#### Added |
| 25 | + * the ASG generated by kops with the `kops-ig` module now have their names |
| 26 | + exposed as outputs (so that you can - for instance - expose your ingress |
| 27 | + controllers as a NodePort on the host and wire them to an ELB) |
| 28 | + * Terraform variable to attach custom security groups to an instance group |
| 29 | + (for the same purpose essentially) |
| 30 | + * kops-created subnets now have their subnet ids exposed as outputs (so that |
| 31 | + you can use Terraform to create resources in these same subnets) |
| 32 | + |
| 33 | +### 0.1.0 - First release of Karch |
| 34 | + |
| 35 | +A Terraform module designed as a wrapper around kops, it makes it possible to |
| 36 | +spawn kops clusters using the `kops-cluster` and `kops-ip` modules, supports |
| 37 | +cluster updates and deletes and exposes resources created by kops to the rest of |
| 38 | +your Terraform code, as simple Terraform outputs. |
0 commit comments