ca408f7e8f
Set default volume type to "gp3" for etcd-manager volumes in AWS
2021-01-27 06:23:27 +02:00
d889d61ddb
Set default IMDS v2 to "required" for instances in AWS
2021-01-21 11:35:41 +02:00
c8a9b2fb3e
Set default volume encryption to "true" for instances in AWS
2021-01-21 11:27:02 +02:00
18bb14ffed
Set default volume type to "gp3" for instances in AWS
2021-01-21 11:27:02 +02:00
afbd057286
Use consistent naming for the remaining SGRs
2021-01-14 12:57:33 +01:00
2b3a8f133e
Add control-plane node role annotation to cp nodes
...
Update docs/releases/1.20-NOTES.md
Co-authored-by: John Gardiner Myers <jgmyers@proofpoint.com>
2021-01-08 12:39:42 +01:00
5406744c55
Update integration test output
2020-12-23 15:13:45 -06:00
cebe171805
Explicitly specify http_endpoint in launch_template terraform
...
http_endpoint has to be explicitly specified in the metadata_options block
of the launch template terraform according to issue
https://github.com/hashicorp/terraform-provider-aws/issues/12564
2020-12-10 01:37:15 +05:30
bee16c052d
Merge pull request #10324 from bharath-123/feature/aws-imdv2
...
Add support for AWS IMDS v2
2020-12-07 22:55:11 -08:00
174f405e39
Update expected outputs of integration tests
2020-12-08 07:08:32 +02:00
ee5d8a3435
update integration tests
2020-12-07 02:57:32 +05:30
0c3e3784c8
Use LaunchTemplate name instead of name_prefix for Terraform
2020-11-09 21:40:36 +02:00
fab694d290
Add ability to consistently name sgrs
...
In order to let kops fully control the rules for each security group we need to be able to generate names from the info in AWS. This is similar to the approach we used for openstack
Update pkg/model/firewall.go
Co-authored-by: Ciprian Hacman <ciprianhacman@gmail.com>
2020-11-07 10:27:19 +01:00
b7f66a6d98
Merge pull request #10109 from bmelbourne/set-minimum-terraform-0.12
...
Set minimum Terraform version to 0.12.26/0.13.0
2020-10-29 01:52:58 -07:00
84417c330b
Set minimum Terraform version to 0.12.26/0.13.0
2020-10-28 20:24:41 +00:00
82d0ebdb56
Prevent unintended resource updates to LB attatchments
2020-10-26 17:29:07 -07:00
54c280eed5
update-expected.sh
2020-09-10 20:59:28 -07:00
0326ce4ad7
Dont generate the ssl_certificate_id field on TCP listeners in Terraform
2020-08-30 09:44:16 -05:00
f3e6ac874d
Update integration test outputs with new ssh key tags
2020-07-28 13:35:10 -05:00
f213854330
Update integration test outputs with filebase64
2020-07-08 23:24:11 -05:00
69f2c71cc3
Add tag support to AWS launch templates
...
In addition to TagSpecifications which allow tagging of instances and volumes, launch templates support tags of their own.
This adds the usual tags to LTs, as seen in the kubernetes.tf additions. Cloudformation does not yet support it [0], so only "api" and "terraform" targets are updated.
[0] https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-launchtemplatedata.html
2020-07-07 22:43:45 -05:00
1b03e7237b
hack/update-expected.sh
2020-06-10 09:34:48 -07:00
fa2d64c3a3
Update expected outputs of terraform tests
2020-04-05 21:24:49 -05:00
ee86488d98
Don't set terraform's user_data if it is an empty string
...
Bastion hosts have no user_data by default.
This is not valid in terraform, based on the error messages reported here [0]
The Terraform provider code says user_data is optional for both LaunchConfigurations and LaunchTemplates [1] [2]
This change prevents the user_data property from being added to aws_launch_configuration and aws_launch_template resources unless the string is not empty.
[0] https://travis-ci.org/github/kubernetes/kops/jobs/662472020
[1] 04d24f80f3/aws/resource_aws_launch_configuration.go (L74-L76)04d24f80f3/aws/resource_aws_launch_template.go (L510-L512)
2020-03-31 09:33:16 -05:00
661bd6dfbd
Add "owned" tag for all instance groups related resources
2020-03-02 10:39:50 +02:00
e0cebf30e5
Update terraform resource names to be 0.12 compatible.
...
According to the upgrade guide [0] resource names cannot start with digits.
Currently both routes and VPC CIDR associations start with digits, so this adds prefixes to them so that they are valid resource identifiers in 0.12.
This is a significant change because on its own, terraform will destroy and recreate the route which impact the cluster networking.
To avoid this, existing clusters this will require moving the resources within the terraform state prior to the next `apply`.
```
kops update cluster --target terraform --out ./
terraform state mv aws_route.0-0-0-0--0 aws_route.route-0-0-0-0--0 # repeat for all aws_route resources
terraform plan
terraform apply
```
The exact terraform state command may vary depending on how Kops' terraform output is used.
See the command documentation [1] for more details.
Always run a terraform plan first to ensure the `aws_route` and `aws_vpc_ipv4_cidr_block_association` resources are not getting recreated.
Due to the potential impact, this notice should be very prominant in the Kops release notes
[0] https://www.terraform.io/upgrade-guides/0-12.html
[1] https://www.terraform.io/docs/commands/state/mv.html
2020-01-17 07:51:39 -06:00
eaa025effd
run hack/update-expected.sh: we now consistenly output an empty user-data for bastion node
2020-01-13 15:28:20 -05:00
21cb8ece06
Label AWS ASGs with kops.k8s.io/instancegroup
...
We will use this to map an AWS instance to the instance group.
2019-09-02 09:26:23 -07:00
4485b115f4
Default CrossZoneLoadBalancing to false if not set
2019-07-26 12:21:43 -04:00
d6c02d3d72
Fix tests
2019-03-29 13:29:11 -04:00
36d2282d6b
AWS: Enable ICMP Type 3 Code 4 for API server ELBs
2019-01-12 07:20:17 -05:00
1c3949bdfe
Don't assume that we only have one subnet per AZ
...
I made a mistaken assumption in
dde2100a19#5587 this was not the case.
What I was trying to achieve was not to include the cluster name, so
for the case of subnets this commit just uses the subnet name from the
cluster spec, which should be unique and stable. That is hopefully at
least as meaningful.
Thankfully we hadn't released a version with the erroneous naming.
Fix #5587
2018-08-13 13:15:03 -04:00
00cd85d73e
Add autoscaling group ids to terraform module output
2018-07-20 13:15:03 +02:00
978f66266c
Generate locals for terraform target
2018-07-13 22:28:27 +02:00
e24aa79aa9
Updated terraform expected test output
2018-06-04 10:52:08 -07:00
5cda02ca2b
Merge pull request #4695 from vendrov/instnace_monitroing_support
...
Add support for instance monitoring
2018-03-25 14:17:01 -07:00
a148c67cad
ElasticIP tags for cloudformation & terraform
...
We previously weren't populating the terraform configuration with these
tags.
2018-03-25 15:52:50 -04:00
63225eb674
Merge pull request #4784 from justinsb/always_tag_volumes
...
Make sure volumes are tagged
2018-03-24 23:32:00 -07:00
0ce7dbf4bd
Update tests for new volume tags
2018-03-25 00:08:24 -04:00
0e22bf4ab5
Update tests for new security group tags
2018-03-24 22:19:59 -04:00
d734f35126
Add support for instance monitoring
...
Add API backward comptability
Add api generated files
documenting detailed-monitoring
instance-group json typo
Update test expected result
to support enable_monitroing
Add instance-monitroing support to CF
Improve doc, test and rename InstanceMonitoring
Rename instnace-monitoring to fit the YAML kops form
typo detailedInstanceMonitoring
2018-03-21 23:06:38 +02:00
6ff56e2f05
Fix shared network objects
...
RouteTables should be created (and owned) only for non-shared subnets.
2018-03-18 17:09:30 -04:00
650bd98ea2
Update integration tests with new tags
2018-03-15 20:11:54 -04:00
cd0f5b5b3f
Update tests
2018-03-08 13:26:34 -05:00
6e32329fb0
updating integration tests
2018-02-23 14:02:50 -07:00
6e562e0742
Support updating autoscaling metrics
2018-02-20 00:53:24 -05:00
02855fc13f
Enable metrics for AutoScalingGroups
...
Those metrics simplify monitoring the created ASGs and are free [0].
Enable them by default.
[0] https://aws.amazon.com/about-aws/whats-new/2016/08/free-auto-scaling-group-metrics-with-graphs/
2018-01-25 20:06:10 +01:00
5850b434b4
Add SubnetType Tag to Subnets
2018-01-08 10:53:58 +00:00
358e2e222c
Create mock igw in integration tests
2017-12-07 16:38:06 -08:00
581e954062
Block etcd peer port from nodes
...
Ports 2380 & 2381 should not be exposed to nodes.
Fix #3746
2017-11-25 16:36:46 -05:00
Ciprian Hacman