Merge pull request #1 from RedbackThomson/initial-commit

Add support for Addon, Cluster, FargateProfile and Nodegroup

Author: jaypipes

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,6 @@
+Issue #, if available:
+
+Description of changes:
+
+By submitting this pull request, I confirm that my contribution is made under
+the terms of the Apache 2.0 license.

.gitignore

@@ -0,0 +1,7 @@
+.DS_Store
+*.swp
+*~
+.idea
+/docs/site
+bin
+build

ATTRIBUTION.md

@@ -1,4 +1,6 @@
 ## Code of Conduct
+
 This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
 For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
 [email protected] with any additional questions or comments.
+

CODE_OF_CONDUCT.md

@@ -1,25 +1,20 @@
 # Contributing Guidelines
 
-Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
-documentation, we greatly value feedback and contributions from our community.
-
-Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
-information to effectively respond to your bug report or contribution.
+Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.
 
+Please read through this document before submitting any issues or pull requests to ensure we have all the necessary information to effectively respond to your bug report or contribution.
 
 ## Reporting Bugs/Feature Requests
 
 We welcome you to use the GitHub issue tracker to report bugs or suggest features.
 
-When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
-reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
+When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
 
 * A reproducible test case or series of steps
 * The version of our code being used
 * Any modifications you've made relevant to the bug
 * Anything unusual about your environment or deployment
 
-
 ## Contributing via Pull Requests
 Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
 
@@ -36,24 +31,21 @@ To send us a pull request, please:
 5. Send us a pull request, answering any default questions in the pull request interface.
 6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
 
-GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
-[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
-
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
 ## Finding contributions to work on
 Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
 
+## Developer documentation
+[See the documentation](https://aws-controllers-k8s.github.io/community/dev-docs/overview/) for detailed development information.
 
 ## Code of Conduct
 This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
-For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
-[email protected] with any additional questions or comments.
 
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact [email protected] with any additional questions or comments.
 
 ## Security issue notifications
 If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
 
-
 ## Licensing
-
 See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.

CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Project governance
+
+This document lays out the guidelines under which the AWS Controllers for Kubernetes (ACK) project will be governed. 
+The goal is to make sure that the roles and responsibilities are well defined and clarify on how decisions are made.
+
+## Roles
+
+In the context of ACK, we consider the following roles:
+
+* __Users__ ... everyone using ACK, typically willing to provide feedback on ACK by proposing features and/or filing issues.
+* __Contributors__ ... everyone contributing code, documentation, examples, testing infra, and participating in feature proposals as well as design discussions. Code contributions will require a Developer Certificate of Origin (DCO).
+* __Maintainers__ ... are responsible for engaging with and assisting contributors to iterate on the contributions until it reaches acceptable quality. Maintainers can decide whether the contributions can be accepted into the project or rejected. Any active contributor meeting the project quality can be made a Maintainer by the Advisory Board.
+* __Advisory Board__ ... is responsible for defining the guidelines and processes that the project operates under. 
+
+The initial members of the Advisory Board are `@jaypipes` and `@mhausenblas`.
+
+
+## Communication
+
+The primary mechanism for communication will be via the `#provider-aws` channel on the Kubernetes Slack community. 
+All features and bug fixes will be tracked as issues in GitHub. All decisions will be documented in GitHub issues.
+
+In the future, we may consider using a public mailing list, which can be better archived. 
+
+## Roadmap Planning
+
+Maintainers will share roadmap and release versions as milestones in GitHub. 
+
+## Release Management
+
+The Advisory Board will propose a release management proposal via a GitHub issue and resolve it there.
+
+## Other relevant governance resources
+
+* The ACK [Contributing Guidelines](CONTRIBUTING.md)
+* Our [Code of Conduct](CODE_OF_CONDUCT.md)
+

GOVERNANCE.md

@@ -0,0 +1,32 @@
+SHELL := /bin/bash # Use bash syntax
+
+# Set up variables
+GO111MODULE=on
+
+# Build ldflags
+VERSION ?= "v0.0.0"
+GITCOMMIT=$(shell git rev-parse HEAD)
+BUILDDATE=$(shell date -u +'%Y-%m-%dT%H:%M:%SZ')
+GO_LDFLAGS=-ldflags "-X main.version=$(VERSION) \
+			-X main.buildHash=$(GITCOMMIT) \
+			-X main.buildDate=$(BUILDDATE)"
+
+AUTHENTICATED_ACCOUNT_ID=$(shell aws sts get-caller-identity --output text --query "Account")
+
+.PHONY: all test
+
+all: test
+
+local-run-controller: ## Run a controller image locally for SERVICE
+	@go run ./cmd/controller/main.go \
+		--aws-account-id=$(AUTHENTICATED_ACCOUNT_ID) \
+		--aws-region=us-west-2 \
+		--enable-development-logging \
+		--log-level=debug
+
+test: 				## Run code tests
+	go test -v ./...
+
+help:           	## Show this help.
+	@grep -F -h "##" $(MAKEFILE_LIST) | grep -F -v grep | sed -e 's/\\$$//' \
+		| awk -F'[:#]' '{print $$1 = sprintf("%-30s", $$1), $$4}'

Makefile

@@ -1 +1,2 @@
-Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+Copyright 2020 Amazon.com, Inc. or its affiliates. All Rights Reserved.
+

NOTICE

@@ -0,0 +1,5 @@
+# See the OWNERS docs at https://go.k8s.io/owners
+
+approvers:
+  - core-ack-team
+  - service-team

OWNERS

@@ -0,0 +1,12 @@
+# See the OWNERS docs at https://go.k8s.io/owners#owners_aliases
+
+aliases:
+  # Always allow the core ACK maintainers to have access to your repository
+  core-ack-team:
+    - jaypipes
+    - mhausenblas
+    - a-hilaly
+    - RedbackThomson
+    - vijtrip2
+  # TODO: Add your team members to your team controller alias
+  service-team: []