Initial commit

.dockerignore

@@ -0,0 +1,8 @@
+# Ignore Docker build configuration.
+.dockerignore
+Dockerfile
+
+# Ignore git project releated files.
+.git
+.gitignore
+.github

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,28 @@
+---
+name: Bug report
+about: Report a bug to help us improve the New Relic Istio Adapter
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. ...
+2. ...
+3. ...
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Version information (please complete the following information):**
+ - newrelic-istio-adapter: [e.g. 0.0.1]
+ - Kubernetes: [e.g. v1.15]
+ - Istio: [e.g. 1.2]
+
+**Additional context**
+Add any other context about the problem here.

.gitignore

@@ -0,0 +1,2 @@
+kube/00-secret.yaml
+vendor*

CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
+
+## Unreleased
+
+## 1.0.0
+
+### Added
+
+*   Initial `newrelic-istio-adapter` application code.
+*   Documentation, user guides, and project metadata.
+*   Build configuration files.

CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# CONTRIBUTOR COVENANT CODE OF CONDUCT
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+*   Using welcoming and inclusive language
+*   Being respectful of differing viewpoints and experiences
+*   Gracefully accepting constructive criticism
+*   Focusing on what is best for the community
+*   Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+*   The use of sexualized language or imagery and unwelcome sexual attention or advances
+*   Trolling, insulting/derogatory comments, and personal or political attacks
+*   Public or private harassment
+*   Publishing others’ private information, such as a physical or electronic address, without explicit permission
+*   Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at open-source@newrelic.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,69 @@
+# Contributing to newrelic-istio-adapter
+
+Welcome!
+We gladly accept contributions from the community.
+
+If you wish to contribute code and you have not signed our [Individual Contributor License Agreement](INDIVIDUAL_CLA.md) or our [Corporate Contributor License Agreement](CORPORATE_CLA.md), please do so in order to contribute.
+
+## How to contribute
+
+We use GitHub Pull Requests to incorporate code changes from external
+contributors. 
+Typical contribution flow steps are:
+
+*   Sign the [Individual Contributor License Agreement](INDIVIDUAL_CLA.md) or our [Corporate Contributor License Agreement](CORPORATE_CLA.md).
+*   Fork the `newrelic-istio-adapter` repository.
+*   Clone the forked repository locally and configure the upstream repository.
+*   Open an Issue describing what you propose to do (unless the change is so
+    trivial that an issue is not needed).
+    Issues should be submitted with a clear description, steps to reproduce the issue, Istio version used, and Kubernetes version.
+*   Once you know which steps to take in your intended contribution, make changes
+    in a topic branch and commit.
+    (Don't forget to add or modify tests!).
+*   Consult the [style guide](STYLE.md) and ensure your changes adhere to the project style.
+*   Fetch changes from upstream, rebase with master and resolve any merge
+    conflicts so that your topic branch is up-to-date.
+*   Build and test the project locally.
+    (See [DEVELOPMENT.md](DEVELOPMENT.md) for more details.)
+*   Push all commits to the topic branch in your forked repository.
+*   Submit a Pull Request to merge topic branch commits to upstream master.
+    Be sure to reference your Issue when creating the PR unless it is a trivial change.
+
+If this process sounds unfamiliar, have a look at the excellent overview of [collaboration via Pull Requests on GitHub](https://help.github.com/categories/collaborating-with-issues-and-pull-requests/)
+for more information.
+
+## Adding dependencies
+
+Please avoid adding new dependencies to the project. If a change requires a new dependency, we encourage you to choose dependencies licensed under BSD, MIT, or Apache licenses.
+
+## Do you have questions or are you experiencing unexpected behaviors after modifying this Open Source Software? 
+
+Please engage with the “Build on New Relic” space in the [Explorers Hub](https://discuss.newrelic.com/c/build-on-new-relic/Integrations), New Relic’s Forum.
+Posts are publicly viewable by anyone, please do not include PII or sensitive information in your forum post. 
+
+## Contributor License Agreement ("CLA")
+
+We'd love to get your contributions to improve `newrelic-istio-adapter`!
+Keep in mind when you submit your pull request, you'll need to sign the [CLA](INDIVIDUAL_CLA.md) via the click-through using CLA-Assistant.
+You only have to sign the CLA one time per project.
+
+To execute our corporate CLA, which is required if your contribution is on behalf of a company, or if you have any questions, please drop us an email at open-source@newrelic.com. 
+
+## Filing Issues & Bug Reports
+
+We use GitHub issues to track public issues and bugs.
+Issues should be submitted with a clear description, steps to reproduce the issue, Istio version used, and Kubernetes version.
+If possible, please provide a link to an example app or gist that reproduces the issue.
+Be aware that GitHub issues are publicly viewable by anyone, so please do not include personal information in your GitHub issue or in any of your contributions, except as minimally necessary for the purpose of supporting your issue.
+New Relic will process any personal data you submit through GitHub issues in compliance with the [New Relic Privacy Notice](https://newrelic.com/termsandconditions/privacy).   
+
+## A note about vulnerabilities  
+
+New Relic is committed to the privacy and security of our customers and their data.
+We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.
+If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through [HackerOne](https://hackerone.com/newrelic).
+
+## License
+
+By contributing to `newrelic-istio-adapter`, you agree that your contributions will be licensed under the LICENSE file in the root directory of this source tree.
+

CORPORATE_CLA.md

@@ -0,0 +1,43 @@
+# NEW RELIC, INC.
+
+## CORPORATE CONTRIBUTOR LICENSE AGREEMENT
+
+Thank you for your interest in contributing to the open source projects of New Relic, Inc. (“New Relic”).
+In order to clarify the intellectual property license granted with Contributions from any person or entity, New Relic must have a Contributor License Agreement ("Agreement") on file that has been signed by each Contributor, indicating agreement to the license terms below.
+This Agreement is for your protection as a Contributor as well as the protection of New Relic; it does not change your rights to use your own Contributions for any other purpose.
+
+This version of the Agreement allows an entity (the "Corporation") to submit Contributions to New Relic, to authorize Contributions submitted by its designated employees to New Relic, and to grant copyright and patent licenses thereto.
+
+You accept and agree to the following terms and conditions for Your present and future Contributions submitted to New Relic.
+Except for the licenses granted herein to New Relic and recipients of software distributed by New Relic, You reserve all right, title, and interest in and to Your Contributions.
+
+1) Definitions
+
+    "You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is entering into this Agreement with New Relic.
+    For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor.
+    For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+    "Contribution" shall mean the code, documentation or other original works of authorship initially identified by You, as well as any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to New Relic for inclusion in, or documentation of, any of the products managed or maintained by New Relic (the "Work").
+    For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to New Relic or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, New Relic for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
+
+2) Grant of Copyright License.
+Subject to the terms and conditions of this Agreement, You hereby grant to New Relic and to recipients of software distributed by New Relic a perpetual, worldwide, non-exclusive, no-charge, royalty-free, transferable, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.
+
+3) Grant of Patent License.
+Subject to the terms and conditions of this Agreement, You hereby grant to New Relic and to recipients of software distributed by New Relic a perpetual, worldwide, non-exclusive, no-charge, royalty-free, transferable, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contributions alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted.
+If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that Your Contribution, or the Work to which You have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.
+
+4) You represent that You are legally entitled to grant the above licenses.
+You represent further that each employee of the Corporation designated by You (now or in the future) is authorized to submit Contributions on behalf of the Corporation.
+
+5) You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others).
+You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which You are aware and which are associated with any part of Your Contributions.
+
+6) You are not expected to provide support for Your Contributions, except to the extent You desire to provide support.
+You may provide support for free, for a fee, or not at all.
+Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
+
+7) Should You wish to submit work that is not Your original creation, You may submit it to New Relic separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which You are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [named here]".
+
+8) It is Your responsibility to notify New Relic when any change is required to the list of designated employees authorized to submit Contributions on behalf of the Corporation, or to the Corporation's point of contact with New Relic.
+You agree to notify New Relic of any facts or circumstances of which You become aware that would make these representations inaccurate in any respect.