You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+78-1Lines changed: 78 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,52 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
Extending the adopted spec, each change should have a link to its corresponding pull request appended.
8
8
9
9
## [Unreleased]
10
+
11
+
## [v5.1.1] - 2019-10-25
12
+
13
+
### Fixed
14
+
15
+
* Fixed bug with setting up sandboxing on nodes. [#286]
16
+
17
+
## [v5.1.0] - 2019-10-24
18
+
10
19
### Added
11
20
21
+
* Added ability to skip local-exec provisioners. [#258]
22
+
* Added [private](https://github.com/terraform-google-modules/terraform-google-kubernetes-engine/tree/master/modules/private-cluster-update-variant) and [beta private](https://github.com/terraform-google-modules/terraform-google-kubernetes-engine/tree/master/modules/beta-private-cluster-update-variant) variants which allow node pools to be created before being destroyed. [#256]
23
+
* Add a parameter `registry_project_id` to allow connecting to registries in other projects. [#273]
24
+
25
+
### Changed
26
+
27
+
* Made `region` variable optional for zonal clusters. [#247]
28
+
* Made default metadata, labels, and tags optional. [#282]
29
+
30
+
### Fixed
31
+
32
+
* Authenticate gcloud in wait-for-cluster.sh using value of `GOOGLE_APPLICATION_CREDENTIALS`. [#284][#285]
33
+
34
+
## [v5.0.0] - 2019-09-25
35
+
v5.0.0 is a backwards-incompatible release. Please see the [upgrading guide](./docs/upgrading_to_v5.0.md).
36
+
37
+
The v5.0.0 module requires using the [2.12 version](https://github.com/terraform-providers/terraform-provider-google/blob/master/CHANGELOG.md#2120-august-01-2019) of the Google provider.
38
+
39
+
### Changed
40
+
41
+
***Breaking**: Enabled metadata-concealment by default [#248]
42
+
* All beta functionality removed from non-beta clusters, moved `node_pool_taints` to beta modules [#228]
43
+
44
+
### Added
45
+
* Added support for resource usage export config [#238]
46
+
* Added `sandbox_enabled` variable to use GKE Sandbox [#241]
47
+
* Added `grant_registry_access` variable to grant Container Registry access to created SA [#236]
12
48
* Support for Intranode Visbiility (IV) and Veritical Pod Autoscaling (VPA) beta features [#216]
49
+
* Support for Workload Identity beta feature [#234]
50
+
* Support for Google Groups based RBAC beta feature [#217]
51
+
* Support for disabling node pool autoscaling by setting `autoscaling` to `false` within the node pool variable. [#250]
52
+
53
+
### Fixed
54
+
55
+
* Fixed issue with passing a dynamically created Service Account to the module. [#27]
13
56
14
57
## [v4.1.0] 2019-07-24
15
58
@@ -28,6 +71,8 @@ Extending the adopted spec, each change should have a link to its corresponding
28
71
* Supported version of Terraform is 0.12. [#177]
29
72
30
73
## [v3.0.0] - 2019-07-08
74
+
v3.0.0 is a breaking release. Refer to the
75
+
[Upgrading to v3.0 guide][upgrading-to-v3.0] for details.
31
76
32
77
### Added
33
78
@@ -68,6 +113,8 @@ Extending the adopted spec, each change should have a link to its corresponding
68
113
2.3. [#148]
69
114
70
115
## [v2.0.0] - 2019-04-12
116
+
v2.0.0 is a breaking release. Refer to the
117
+
[Upgrading to v2.0 guide][upgrading-to-v2.0] for details.
71
118
72
119
### Added
73
120
@@ -99,6 +146,10 @@ Extending the adopted spec, each change should have a link to its corresponding
99
146
* Fix empty zone list. [#132]
100
147
101
148
## [v1.0.0] - 2019-03-25
149
+
Version 1.0.0 of this module introduces a breaking change: adding the `disable-legacy-endpoints` metadata field to all node pools. This metadata is required by GKE and [determines whether the `/0.1/` and `/v1beta1/` paths are available in the nodes' metadata server](https://cloud.google.com/kubernetes-engine/docs/how-to/protecting-cluster-metadata#disable-legacy-apis). If your applications do not require access to the node's metadata server, you can leave the default value of `true` provided by the module. If your applications require access to the metadata server, be sure to read the linked documentation to see if you need to set the value for this field to `false` to allow your applications access to the above metadata server paths.
150
+
151
+
In either case, upgrading to module version `v1.0.0` will trigger a recreation of all node pools in the cluster.
152
+
102
153
### Added
103
154
* Allow creation of service accounts. [#80]
104
155
* Add support for private clusters via submodule. [#69]
@@ -153,7 +204,10 @@ Extending the adopted spec, each change should have a link to its corresponding
This document provides guidelines for contributing to the module.
4
+
5
+
## Dependencies
6
+
7
+
The following dependencies must be installed on the development system:
8
+
9
+
-[Docker Engine][docker-engine]
10
+
-[Google Cloud SDK][google-cloud-sdk]
11
+
-[make]
12
+
13
+
## Generating Documentation for Inputs and Outputs
14
+
15
+
The Inputs and Outputs tables in the READMEs of the root module,
16
+
submodules, and example modules are automatically generated based on
17
+
the `variables` and `outputs` of the respective modules. These tables
18
+
must be refreshed if the module interfaces are changed.
19
+
20
+
## Templating
21
+
22
+
To more cleanly handle cases where desired functionality would require complex duplication of Terraform resources (i.e. [PR 51](https://github.com/terraform-google-modules/terraform-google-kubernetes-engine/pull/51)), this repository is largely generated from the [`autogen`](/autogen) directory.
23
+
24
+
The root module is generated by running `make generate`. Changes to this repository should be made in the [`autogen`](/autogen) directory where appropriate.
25
+
26
+
Note: The correct sequence to update the repo using autogen functionality is to run
27
+
`make docker_generate && make docker_generate_docs`. This will create the various Terraform files, and then
28
+
generate the Terraform documentation using `terraform-docs`.
29
+
30
+
### Autogeneration of documentation from .tf files
31
+
To generate new Inputs and Outputs tables run
32
+
```
33
+
make docker_generate_docs
34
+
```
35
+
36
+
## Integration Testing
37
+
38
+
Integration tests are used to verify the behaviour of the root module,
39
+
submodules, and example modules. Additions, changes, and fixes should
40
+
be accompanied with tests.
41
+
42
+
The integration tests are run using [Kitchen][kitchen],
43
+
[Kitchen-Terraform][kitchen-terraform], and [InSpec][inspec]. These
44
+
tools are packaged within a Docker image for convenience.
45
+
46
+
The general strategy for these tests is to verify the behaviour of the
47
+
[example modules](./examples/), thus ensuring that the root module,
48
+
submodules, and example modules are all functionally correct.
49
+
50
+
Six test-kitchen instances are defined:
51
+
52
+
-`deploy-service`
53
+
-`node-pool`
54
+
-`shared-vpc`
55
+
-`simple-regional`
56
+
-`simple-zonal`
57
+
-`stub-domains`
58
+
59
+
The test-kitchen instances in `test/fixtures/` wrap identically-named examples in the `examples/` directory.`
60
+
61
+
### Test Environment
62
+
The easiest way to test the module is in an isolated test project. The setup for such a project is defined in [test/setup](./test/setup/) directory.
63
+
64
+
To use this setup, you need a service account with Project Creator access on a folder. Export the Service Account credentials to your environment like so:
65
+
66
+
```
67
+
export SERVICE_ACCOUNT_JSON=$(< credentials.json)
68
+
```
69
+
70
+
You will also need to set a few environment variables:
0 commit comments