mirror of
https://github.com/projectcapsule/capsule.git
synced 2026-02-14 18:09:58 +00:00
Initial commit
This commit is contained in:
43
.github/ISSUE_TEMPLATE/bug_report.md
vendored
Normal file
43
.github/ISSUE_TEMPLATE/bug_report.md
vendored
Normal file
@@ -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`)
|
||||
37
.github/ISSUE_TEMPLATE/feature_request.md
vendored
Normal file
37
.github/ISSUE_TEMPLATE/feature_request.md
vendored
Normal file
@@ -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.
|
||||
Reference in New Issue
Block a user