Skip to content

Commit 2df57df

Browse files
roin-orcaroin-orca
committed
init
0 parents  commit 2df57df

File tree

128 files changed

+7158
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

128 files changed

+7158
-0
lines changed

‎.github/DISCUSSION_TEMPLATE/adopters.yaml

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
title: "<org name>:"
2+
labels: ["adopters"]
3+
body:
4+
- type: textarea
5+
attributes:
6+
label: "How do you use KTE?"
7+
validations:
8+
required: true
9+
- type: textarea
10+
attributes:
11+
label: "What's your favorite part of KTE?"
12+
validations:
13+
required: false
14+
- type: markdown
15+
attributes:
16+
value: |
17+
## Get in touch
18+
We are always looking to chat, listen to more feedback and collaborate with other organizations / individuals. If any of this interests you or your marketing team, please reach out at: [email protected].

‎.github/DISCUSSION_TEMPLATE/bugs.yaml

+40
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
labels: ["bug"]
2+
body:
3+
- type: markdown
4+
attributes:
5+
value: |
6+
**NOTE**: Please ensure that you're not creating a duplicate report by searching the [issues](https://github.com/orcasecurity/kte/issues)/[discussions](https://github.com/orcasecurity/kte/discussions) before you continue.
7+
- type: textarea
8+
attributes:
9+
label: Description
10+
description: Briefly describe the problem you are having in a few paragraphs.
11+
validations:
12+
required: true
13+
- type: textarea
14+
attributes:
15+
label: Desired Behavior
16+
description: What did you expect to happen?
17+
validations:
18+
required: true
19+
- type: textarea
20+
attributes:
21+
label: Actual Behavior
22+
description: What happened instead?
23+
validations:
24+
required: true
25+
- type: textarea
26+
attributes:
27+
label: Reproduction Steps
28+
description: How do you trigger this bug? Please walk us through it step by step.
29+
value: |
30+
1.
31+
2.
32+
3.
33+
...
34+
render: bash
35+
validations:
36+
required: true
37+
- type: markdown
38+
attributes:
39+
value: |
40+
We would be happy if you could share how you are using KTE [here](https://github.com/orcasecurity/kte/discussions/new?category=adopters).

‎.gitignore

+53
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# Local .terraform directories
2+
**/.terraform/*
3+
4+
# .tfstate files
5+
*.tfstate
6+
*.tfstate.*
7+
8+
# terraform lock files
9+
.terraform.lock.*
10+
11+
# Crash log files
12+
crash.log
13+
crash.*.log
14+
15+
# Exclude all .tfvars files, which are likely to contain sensitive data, such as
16+
# password, private keys, and other secrets. These should not be part of version
17+
# control as they are data points which are potentially sensitive and subject
18+
# to change depending on the environment.
19+
*.tfvars
20+
*.tfvars.json
21+
22+
# Ignore override files as they are usually used to override resources locally and so
23+
# are not checked in
24+
override.tf
25+
override.tf.json
26+
*_override.tf
27+
*_override.tf.json
28+
29+
# Include override files you do wish to add to version control using negated pattern
30+
# !example_override.tf
31+
32+
# Include tfplan files to ignore the plan output of command: terraform plan -out=tfplan
33+
# example: *tfplan*
34+
35+
# Ignore CLI configuration files
36+
.terraformrc
37+
terraform.rc
38+
39+
# Ignore JetBrains IDEs hidden directory
40+
.idea
41+
42+
# Ignore kte tools binaries & html files
43+
kubesec.html
44+
kube-score.html
45+
kube-score_output.txt
46+
checkov.html
47+
checkov_output.txt
48+
tools/kubesec/kubesec
49+
tools/kube-score/kube-score
50+
51+
# Ignore ssh keys
52+
id_rsa
53+
id_rsa.pub

‎CHANGELOG.md

Whitespace-only changes.

‎CODE_OF_CONDUCT.md

+128
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
[email protected].
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.0, available at
119+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120+
121+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
122+
enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
[homepage]: https://www.contributor-covenant.org
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
https://www.contributor-covenant.org/faq. Translations are available at
128+
https://www.contributor-covenant.org/translations.

‎CONTRIBUTING.md

+34
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# How To Contribute
2+
## 1) What We Prioritize
3+
Your PR is more likely to get accepted if it includes agnostic support of new open-source tools. We would like to create a hub of seamless, agnostic and fast evaluation of different Kubernetes security software. This will tremendously help organizations and individuals asses and secure their k8s resources. Of-course, we would also welcome and prioritize support of different Cloud Service Providers. Your changes must integrate with [index.html]() and export web-based dashboards to maintain an easy and coherent access.
4+
5+
## 2) Discuss First, Implement Later
6+
We are looking to engage with contributors. Please share your suggestions before you start writing any code. This will foster a healthy and fun community, and raise your chances of meeting master. Let us and the other contributors know your plans, so we could share our feedback.
7+
8+
## 3) Basic Guidelines
9+
1. Please add the associated Discussions link in the PR description.
10+
2. Please include a comment with the results before and after your change. **IMPORTANT:** since this project (at this moment) doesn't implement testings or CI/CD validations, we ask for a demonstration of a successful end-2-end testing, which showcases code maturity and stability. This can be made through a video or footage.
11+
3. Please update the docs according to the your new changes in code or user experience.
12+
13+
## 4) Conventions
14+
Your pull request title should be indicative and succinct. Stick to one sentence, don't capitalize the first word and follow the below format. Currently allowed `<type>` values:
15+
* **feature**
16+
* **bugfix**
17+
* **performance**: for performance improvements.
18+
* **style**: for ux improvements.
19+
* **docs**: for changes to the docs.
20+
21+
We may allow other / more type values during a discussion.
22+
23+
```
24+
<type>: <subject>
25+
```
26+
27+
Example titles:
28+
```
29+
feature: adding support for OKE
30+
```
31+
```
32+
feature: adding support for kube-hunter
33+
```
34+

0 commit comments

Comments
 (0)