Initial commit

.github/FUNDING.yml

@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: [prometherion]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug report
+about: Create a report to help us improve Capsule
+title: ''
+labels: blocked-needs-validation, bug
+assignees: ''
+
+---
+
+<!--
+Thanks for taking time reporting a Capsule bug!
+
+We do our best to keep it reliable and working, so don't hesitate adding
+as many information as you can and keep in mind you can reach us on our
+Clastix Slack workspace: https://clastix.slack.com, #capsule channel.   
+-->
+
+# Bug description
+
+A clear and concise description of what the bug is.
+
+# How to reproduce
+
+Steps to reproduce the behaviour:
+
+1. Provide the Capsule Tenant YAML definitions
+2. Provide all managed Kubernetes resources
+
+# Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+# Logs
+
+If applicable, please provide logs of `capsule`.
+
+In a standard stand-alone installation of Capsule,
+you'd get this by running `kubectl -n capsule-system logs deploy/capsule`.
+
+# Additional context
+
+- Capsule version: (`capsule --version`)
+- Kubernetes version: (`kubectl version`)

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,37 @@
+---
+name: Feature request
+about: Suggest a new feature for Capsule
+title: ''
+labels: blocked-needs-validation, feature
+assignees: ''
+
+---
+
+<!--
+Yay, it look you're enjoying Capsule and, first, thanks for that!
+
+We're trying to build a community drive Open Source project, so don't
+hesitate proposing your enhancement ideas: keep in mind, since we would like
+to keep it as agnostic as possible, to motivate all your assumptions.
+
+If you need to reach the maintainers, please join the Clastix Slack workspace:
+https://clastix.slack.com, #capsule channel.   
+-->
+
+# Describe the feature
+
+A clear and concise description of the feature.
+
+# What would the new user story look like?
+
+How would the new interaction with Capsule look like? E.g.
+
+1. What are the prerequisites for this?
+2. Tenant owner creates a new _Namespace_
+3. This is going to be attached to the _Tenant_
+4. All the magic happens in the background
+
+Feel free to add a diagram if that helps explain things.
+
+# Expected behavior
+A clear and concise description of what you expect to happen.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+<!--
+# General contribution criteria
+
+Thanks for spending some time for improving and fixing Capsule!
+
+We're still working on the outline of the contribution guidelines but we're
+following ourselves these points:
+
+- reference a previously opened issue: https://docs.github.com/en/github/writing-on-github/autolinked-references-and-urls#issues-and-pull-requests 
+- including a sentence or two in the commit description for the
+  changelog/release notes
+- splitting changes into several and documented small commits
+- limit the git subject to 50 characters and write as the continuation of the
+  sentence "If applied, this commit will ..."
+- explain what and why in the body, if more than a trivial change, wrapping at
+  72 characters
+
+If you have any issue or question, reach out us!
+https://clastix.slack.com >>> #capsule channel 
+-->

.github/workflows/main.yaml

@@ -0,0 +1,13 @@
+name: golangci-lint
+on:
+  pull_request:
+jobs:
+  golangci:
+    name: lint
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: golangci-lint
+        uses: golangci/golangci-lint-action@v1
+        with:
+          version: v1.29