terraform-aws-kops-vpc-peering

Terraform module to create a peering connection between a backing services VPC and a VPC created by Kops.

The module depends on the following Cloud Posse Terraform modules

terraform-aws-kops-metadata - to lookup resources within a Kops cluster
terraform-aws-vpc-peering - to create a peering connection between two VPCs

This project is part of our comprehensive "SweetOps" approach towards DevOps.

It's 100% Open Source and licensed under the APACHE2.

Usage

module "kops_vpc_peering" {
  source                                           = "git::https://github.com/cloudposse/terraform-aws-kops-vpc-peering.git?ref=master"
  namespace                                        = "cp"
  stage                                            = "dev"
  name                                             = "cluster"
  backing_services_vpc_id                          = "vpc-XXXXXXXX"
  dns_zone                                         = "us-west-2.domain.com"
  bastion_name                                     = "bastion"
  masters_name                                     = "masters"
  nodes_name                                       = "nodes"
  backing_services_allow_remote_vpc_dns_resolution = "true"
}

Makefile Targets

Available targets:

  help                                This help screen
  help/all                            Display help for all targets
  lint                                Lint terraform code

Inputs

Name	Description	Type	Default	Required
attributes	Additional attributes (e.g. `policy` or `role`)	list	`<list>`	no
auto_accept	Automatically accept the peering (both VPCs need to be in the same AWS account)	string	`true`	no
backing_services_allow_remote_vpc_dns_resolution	Allow the backing services VPC to resolve public DNS hostnames to private IP addresses when queried from instances in the Kops VPC	string	`true`	no
backing_services_vpc_id	Backing services VPC ID	string	-	yes
bastion_name	Bastion server subdomain name in the Kops DNS zone	string	`bastion`	no
delimiter	Delimiter to be used between `namespace`, `stage`, `name`, and `attributes`	string	`-`	no
dns_zone	Name of the Kops DNS zone	string	-	yes
enabled	Set to false to prevent the module from creating or accessing any resources	string	`true`	no
masters_name	K8s masters subdomain name in the Kops DNS zone	string	`masters`	no
name	Name (e.g. `app` or `cluster`)	string	-	yes
namespace	Namespace (e.g. `cp` or `cloudposse`)	string	-	yes
nodes_name	K8s nodes subdomain name in the Kops DNS zone	string	`nodes`	no
stage	Stage (e.g. `prod`, `dev`, `staging`)	string	-	yes
tags	Additional tags (e.g. map('BusinessUnit`,`XYZ`)	map	`<map>`	no

Outputs

Name	Description
accept_status	The status of the VPC peering connection request
connection_id	VPC peering connection ID
kops_vpc_id	Kops VPC ID

Related Projects

Check out these related projects.

terraform-aws-kops-metadata - Terraform module to lookup resources within a Kops cluster for easier integration with Terraform
terraform-aws-kops-ecr - Terraform module to provision an ECR repository and grant users and kubernetes nodes access to it.
terraform-aws-kops-state-backend - Easily bootstrap kops clusters (DNS & S3 Bucket)
terraform-aws-kops-external-dns - Terraform module to provision an IAM role for external-dns running in a Kops cluster, and attach an IAM policy to the role with permissions to modify Route53 record sets
terraform-aws-kops-route53 - Terraform module to lookup the IAM role associated with kops masters, and attach an IAM policy to the role with permissions to modify Route53 record sets
terraform-aws-kops-vault-backend - Terraform module to provision an S3 bucket for HashiCorp Vault secrets storage, and an IAM role and policy with permissions for Kops nodes to access the bucket
terraform-aws-kops-chart-repo - Terraform module to provision an S3 bucket for Helm chart repository, and an IAM role and policy with permissions for Kops nodes to access the bucket

Help

Got a question?

File a GitHub issue, send us an email or join our Slack Community.

Commercial Support

Work directly with our team of DevOps experts via email, slack, and video conferencing.

We provide commercial support for all of our Open Source projects. As a Dedicated Support customer, you have access to our team of subject matter experts at a fraction of the cost of a full-time engineer.

Questions. We'll use a Shared Slack channel between your team and ours.
Troubleshooting. We'll help you triage why things aren't working.
Code Reviews. We'll review your Pull Requests and provide constructive feedback.
Bug Fixes. We'll rapidly work to fix any bugs in our projects.
Build New Terraform Modules. We'll develop original modules to provision infrastructure.
Cloud Architecture. We'll assist with your cloud strategy and design.
Implementation. We'll provide hands-on support to implement our reference architectures.

Community Forum

Get access to our Open Source Community Forum on Slack. It's FREE to join for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build sweet infrastructure.

Contributing

Bug Reports & Feature Requests

Please use the issue tracker to report any bugs or file feature requests.

Developing

If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

Fork the repo on GitHub
Clone the project to your own machine
Commit changes to your own branch
Push your work back up to your fork
Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

Copyright

License

See LICENSE for full details.

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.

About

This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know at hello@cloudposse.com

We're a DevOps Professional Services company based in Los Angeles, CA. We love Open Source Software!

We offer paid support on all of our projects.

Check out our other projects, apply for a job, or hire us to help with your cloud strategy and implementation.

Contributors

Andriy Knysh

amoskyler/terraform-aws-kops-vpc-peering