vpc-kops-peering

cloudposse/vpc-kops-peering/aws

Terraform Module HCL AWS

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

Install

module "vpc-kops-peering" {

source = "cloudposse/vpc-kops-peering/aws"

version = "0.1.5"

}

plain text: /constructs/tfmod-cloudposse-vpc-kops-peering-aws/install.txt

⭐ Source on GitHub 📦 Registry page

README

[![README Header][readme_header_img]][readme_header_link] [![Cloud Posse][logo]](https://cpco.io/homepage) terraform-aws-kops-vpc-peering ![Build Status](https://travis-ci.org/cloudposse/terraform-aws-kops-vpc-peering) ![Latest Release](https://github.com/cloudposse/terraform-aws-kops-vpc-peering/releases/latest) ![Slack Community](https://slack.cloudposse.com) 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][website] 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. [ ][share_email] [

Inputs (14)

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