terraform-aws-kops-ecr

Terraform module to provision an ECR repository and grant users and kubernetes nodes access to it.

Overview

The module uses terraform-aws-kops-metadata to lookup resources within a Kops cluster for easier integration with Terraform.

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

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

Usage

module "cicd_user" {
  source    = "git::https://github.com/cloudposse/terraform-aws-iam-system-user.git?ref=tags/0.3.0"
  namespace = "${var.namespace}"
  stage     = "${var.stage}"
  name      = "codefresh"

  tags = {
    Cluster = "${var.kops_cluster_name}"
  }
}

module "kops_ecr_app" {
  source       = "git::https://github.com/cloudposse/terraform-aws-kops-ecr.git?ref=tags/0.1.0"
  namespace    = "${var.namespace}"
  stage        = "${var.stage}"
  name         = "app"
  cluster_name = "${var.kops_cluster_name}"

  users = [
    "${module.cicd_user.user_name}"
  ]

  tags = {
    Cluster = "${var.kops_cluster_name}"
  }
}

Makefile Targets

Available targets:

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

Inputs

Name	Description	Type	Default	Required
attributes	Additional attributes (e.g. `1`)	list	`<list>`	no
cluster_name	Kops cluster name (e.g. `us-west-2.cloudposse.co` or `cluster-1.cloudposse.co`)	string	-	yes
delimiter	Delimiter to be used between `namespace`, `stage`, `name` and `attributes`	string	`-`	no
masters_name	Kops masters subdomain name in the cluster DNS zone	string	`masters`	no
name	Name (e.g. `external-dns`)	string	-	yes
namespace	Namespace (e.g. `cp` or `cloudposse`)	string	-	yes
nodes_name	Kops nodes subdomain name in the cluster DNS zone	string	`nodes`	no
stage	Stage (e.g. `prod`, `dev`, `staging`)	string	-	yes
tags	Additional tags (e.g. map(`Cluster`,`us-west-2.cloudposse.co`)	map	`<map>`	no
use_fullname	Set 'true' to use `namespace-stage-name` for ecr repository name, else `name`	string	`true`	no
users	User names to grant permissions	list	`<list>`	no

Outputs

Name	Description
registry_id	Registry ID
registry_url	Registry URL
repository_name	Repository name
role_arn	Role ARN to get access to the registry
role_name	Role name to get access to the registry

Related Projects

Check out these related projects.

terraform-aws-ecr - Terraform Module to manage Docker Container Registries on AWS ECR
terraform-aws-jenkins - Terraform module to build Docker image with Jenkins, save it to an ECR repo, and deploy to Elastic Beanstalk running Docker stack

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

Igor Rodionov