Skip to content

Commit d780442

Browse files
author
Aaron Lane
committed
Remove upgrade notes from CHANGELOG
This content of this section is incomplete (missing 5.0.0) and redundant with the CHANGELOG.
1 parent 1d8356d commit d780442

File tree

7 files changed

+0
-141
lines changed

7 files changed

+0
-141
lines changed

‎README.md‎

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -108,22 +108,6 @@ Then perform the following commands on the root folder:
108108
- `terraform apply` to apply the infrastructure build
109109
- `terraform destroy` to destroy the built infrastructure
110110

111-
## Upgrade to v3.0.0
112-
113-
v3.0.0 is a breaking release. Refer to the
114-
[Upgrading to v3.0 guide][upgrading-to-v3.0] for details.
115-
116-
## Upgrade to v2.0.0
117-
118-
v2.0.0 is a breaking release. Refer to the
119-
[Upgrading to v2.0 guide][upgrading-to-v2.0] for details.
120-
121-
## Upgrade to v1.0.0
122-
123-
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.
124-
125-
In either case, upgrading to module version `v1.0.0` will trigger a recreation of all node pools in the cluster.
126-
127111
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
128112
## Inputs
129113

@@ -251,9 +235,6 @@ The project has the following folders and files:
251235
- /README.MD: This file.
252236
- /modules: Private and beta sub modules.
253237

254-
255-
[upgrading-to-v2.0]: docs/upgrading_to_v2.0.md
256-
[upgrading-to-v3.0]: docs/upgrading_to_v3.0.md
257238
[terraform-provider-google]: https://github.com/terraform-providers/terraform-provider-google
258239
[3.0.0]: https://registry.terraform.io/modules/terraform-google-modules/kubernetes-engine/google/3.0.0
259240
[terraform-0.12-upgrade]: https://www.terraform.io/upgrade-guides/0-12.html

‎autogen/README.md‎

Lines changed: 0 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -125,22 +125,6 @@ Then perform the following commands on the root folder:
125125
- `terraform apply` to apply the infrastructure build
126126
- `terraform destroy` to destroy the built infrastructure
127127

128-
## Upgrade to v3.0.0
129-
130-
v3.0.0 is a breaking release. Refer to the
131-
[Upgrading to v3.0 guide][upgrading-to-v3.0] for details.
132-
133-
## Upgrade to v2.0.0
134-
135-
v2.0.0 is a breaking release. Refer to the
136-
[Upgrading to v2.0 guide][upgrading-to-v2.0] for details.
137-
138-
## Upgrade to v1.0.0
139-
140-
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.
141-
142-
In either case, upgrading to module version `v1.0.0` will trigger a recreation of all node pools in the cluster.
143-
144128
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
145129
<!-- END OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
146130

@@ -199,17 +183,6 @@ The project has the following folders and files:
199183
- /README.MD: This file.
200184
- /modules: Private and beta sub modules.
201185

202-
203-
{% if private_cluster %}
204-
[upgrading-to-v2.0]: ../../docs/upgrading_to_v2.0.md
205-
{% else %}
206-
[upgrading-to-v2.0]: docs/upgrading_to_v2.0.md
207-
{% endif %}
208-
{% if private_cluster or beta_cluster %}
209-
[upgrading-to-v3.0]: ../../docs/upgrading_to_v3.0.md
210-
{% else %}
211-
[upgrading-to-v3.0]: docs/upgrading_to_v3.0.md
212-
{% endif %}
213186
{% if beta_cluster %}
214187
[terraform-provider-google-beta]: https://github.com/terraform-providers/terraform-provider-google-beta
215188
{% else %}

‎modules/beta-private-cluster-update-variant/README.md‎

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -116,22 +116,6 @@ Then perform the following commands on the root folder:
116116
- `terraform apply` to apply the infrastructure build
117117
- `terraform destroy` to destroy the built infrastructure
118118

119-
## Upgrade to v3.0.0
120-
121-
v3.0.0 is a breaking release. Refer to the
122-
[Upgrading to v3.0 guide][upgrading-to-v3.0] for details.
123-
124-
## Upgrade to v2.0.0
125-
126-
v2.0.0 is a breaking release. Refer to the
127-
[Upgrading to v2.0 guide][upgrading-to-v2.0] for details.
128-
129-
## Upgrade to v1.0.0
130-
131-
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.
132-
133-
In either case, upgrading to module version `v1.0.0` will trigger a recreation of all node pools in the cluster.
134-
135119
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
136120
## Inputs
137121

@@ -287,9 +271,6 @@ The project has the following folders and files:
287271
- /README.MD: This file.
288272
- /modules: Private and beta sub modules.
289273

290-
291-
[upgrading-to-v2.0]: ../../docs/upgrading_to_v2.0.md
292-
[upgrading-to-v3.0]: ../../docs/upgrading_to_v3.0.md
293274
[terraform-provider-google-beta]: https://github.com/terraform-providers/terraform-provider-google-beta
294275
[3.0.0]: https://registry.terraform.io/modules/terraform-google-modules/kubernetes-engine/google/3.0.0
295276
[terraform-0.12-upgrade]: https://www.terraform.io/upgrade-guides/0-12.html

‎modules/beta-private-cluster/README.md‎

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -116,22 +116,6 @@ Then perform the following commands on the root folder:
116116
- `terraform apply` to apply the infrastructure build
117117
- `terraform destroy` to destroy the built infrastructure
118118

119-
## Upgrade to v3.0.0
120-
121-
v3.0.0 is a breaking release. Refer to the
122-
[Upgrading to v3.0 guide][upgrading-to-v3.0] for details.
123-
124-
## Upgrade to v2.0.0
125-
126-
v2.0.0 is a breaking release. Refer to the
127-
[Upgrading to v2.0 guide][upgrading-to-v2.0] for details.
128-
129-
## Upgrade to v1.0.0
130-
131-
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.
132-
133-
In either case, upgrading to module version `v1.0.0` will trigger a recreation of all node pools in the cluster.
134-
135119
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
136120
## Inputs
137121

@@ -287,9 +271,6 @@ The project has the following folders and files:
287271
- /README.MD: This file.
288272
- /modules: Private and beta sub modules.
289273

290-
291-
[upgrading-to-v2.0]: ../../docs/upgrading_to_v2.0.md
292-
[upgrading-to-v3.0]: ../../docs/upgrading_to_v3.0.md
293274
[terraform-provider-google-beta]: https://github.com/terraform-providers/terraform-provider-google-beta
294275
[3.0.0]: https://registry.terraform.io/modules/terraform-google-modules/kubernetes-engine/google/3.0.0
295276
[terraform-0.12-upgrade]: https://www.terraform.io/upgrade-guides/0-12.html

‎modules/beta-public-cluster/README.md‎

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -111,22 +111,6 @@ Then perform the following commands on the root folder:
111111
- `terraform apply` to apply the infrastructure build
112112
- `terraform destroy` to destroy the built infrastructure
113113

114-
## Upgrade to v3.0.0
115-
116-
v3.0.0 is a breaking release. Refer to the
117-
[Upgrading to v3.0 guide][upgrading-to-v3.0] for details.
118-
119-
## Upgrade to v2.0.0
120-
121-
v2.0.0 is a breaking release. Refer to the
122-
[Upgrading to v2.0 guide][upgrading-to-v2.0] for details.
123-
124-
## Upgrade to v1.0.0
125-
126-
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.
127-
128-
In either case, upgrading to module version `v1.0.0` will trigger a recreation of all node pools in the cluster.
129-
130114
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
131115
## Inputs
132116

@@ -278,9 +262,6 @@ The project has the following folders and files:
278262
- /README.MD: This file.
279263
- /modules: Private and beta sub modules.
280264

281-
282-
[upgrading-to-v2.0]: docs/upgrading_to_v2.0.md
283-
[upgrading-to-v3.0]: ../../docs/upgrading_to_v3.0.md
284265
[terraform-provider-google-beta]: https://github.com/terraform-providers/terraform-provider-google-beta
285266
[3.0.0]: https://registry.terraform.io/modules/terraform-google-modules/kubernetes-engine/google/3.0.0
286267
[terraform-0.12-upgrade]: https://www.terraform.io/upgrade-guides/0-12.html

‎modules/private-cluster-update-variant/README.md‎

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -113,22 +113,6 @@ Then perform the following commands on the root folder:
113113
- `terraform apply` to apply the infrastructure build
114114
- `terraform destroy` to destroy the built infrastructure
115115

116-
## Upgrade to v3.0.0
117-
118-
v3.0.0 is a breaking release. Refer to the
119-
[Upgrading to v3.0 guide][upgrading-to-v3.0] for details.
120-
121-
## Upgrade to v2.0.0
122-
123-
v2.0.0 is a breaking release. Refer to the
124-
[Upgrading to v2.0 guide][upgrading-to-v2.0] for details.
125-
126-
## Upgrade to v1.0.0
127-
128-
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.
129-
130-
In either case, upgrading to module version `v1.0.0` will trigger a recreation of all node pools in the cluster.
131-
132116
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
133117
## Inputs
134118

@@ -260,9 +244,6 @@ The project has the following folders and files:
260244
- /README.MD: This file.
261245
- /modules: Private and beta sub modules.
262246

263-
264-
[upgrading-to-v2.0]: ../../docs/upgrading_to_v2.0.md
265-
[upgrading-to-v3.0]: ../../docs/upgrading_to_v3.0.md
266247
[terraform-provider-google]: https://github.com/terraform-providers/terraform-provider-google
267248
[3.0.0]: https://registry.terraform.io/modules/terraform-google-modules/kubernetes-engine/google/3.0.0
268249
[terraform-0.12-upgrade]: https://www.terraform.io/upgrade-guides/0-12.html

‎modules/private-cluster/README.md‎

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -113,22 +113,6 @@ Then perform the following commands on the root folder:
113113
- `terraform apply` to apply the infrastructure build
114114
- `terraform destroy` to destroy the built infrastructure
115115

116-
## Upgrade to v3.0.0
117-
118-
v3.0.0 is a breaking release. Refer to the
119-
[Upgrading to v3.0 guide][upgrading-to-v3.0] for details.
120-
121-
## Upgrade to v2.0.0
122-
123-
v2.0.0 is a breaking release. Refer to the
124-
[Upgrading to v2.0 guide][upgrading-to-v2.0] for details.
125-
126-
## Upgrade to v1.0.0
127-
128-
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.
129-
130-
In either case, upgrading to module version `v1.0.0` will trigger a recreation of all node pools in the cluster.
131-
132116
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
133117
## Inputs
134118

@@ -260,9 +244,6 @@ The project has the following folders and files:
260244
- /README.MD: This file.
261245
- /modules: Private and beta sub modules.
262246

263-
264-
[upgrading-to-v2.0]: ../../docs/upgrading_to_v2.0.md
265-
[upgrading-to-v3.0]: ../../docs/upgrading_to_v3.0.md
266247
[terraform-provider-google]: https://github.com/terraform-providers/terraform-provider-google
267248
[3.0.0]: https://registry.terraform.io/modules/terraform-google-modules/kubernetes-engine/google/3.0.0
268249
[terraform-0.12-upgrade]: https://www.terraform.io/upgrade-guides/0-12.html

0 commit comments

Comments
 (0)