Skip to content

Commit 2b6d394

Browse files
thc1006thc1006
committed
Add comprehensive security tests for TLS/mTLS configuration and validation
- Implemented a security test suite in `suite_test.go` to validate the overall security setup. - Created detailed tests in `tls_test.go` to check TLS certificate validity, expiration monitoring, CA validation, and service TLS enforcement. - Added utility functions in `security_helpers.go` for setting up the test environment, validating security contexts, and checking resource limits. - Included checks for mutual TLS (mTLS) authentication and certificate revocation mechanisms. - Established benchmarks for TLS operations to assess performance. - Enhanced the security testing framework with structured test cases and suites for better organization and execution.
1 parent 778f154 commit 2b6d394

91 files changed

Lines changed: 54674 additions & 197 deletions

File tree

Some content is hidden

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

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
---
2+
name: Bug Report
3+
about: Report a bug to help us improve the Nephoran Intent Operator
4+
title: "[BUG] "
5+
labels: ["bug", "needs-triage"]
6+
assignees: []
7+
---
8+
9+
## Bug Description
10+
11+
A clear and concise description of what the bug is.
12+
13+
## Steps to Reproduce
14+
15+
Please provide detailed steps to reproduce the behavior:
16+
17+
1. Go to '...'
18+
2. Click on '...'
19+
3. Execute command '...'
20+
4. See error
21+
22+
## Expected Behavior
23+
24+
A clear and concise description of what you expected to happen.
25+
26+
## Actual Behavior
27+
28+
A clear and concise description of what actually happened.
29+
30+
## Environment Information
31+
32+
**System Information:**
33+
- OS: [e.g., macOS 12.0, Ubuntu 22.04, Windows 11]
34+
- Architecture: [e.g., amd64, arm64]
35+
36+
**Software Versions:**
37+
- Go version: [e.g., 1.23.0]
38+
- Kubernetes version: [e.g., 1.28.0]
39+
- Docker version: [e.g., 24.0.0]
40+
- Nephoran version: [e.g., v0.1.0]
41+
42+
**Cluster Information:**
43+
- Kubernetes distribution: [e.g., kind, minikube, EKS, GKE, AKS]
44+
- Node count: [e.g., 3]
45+
- Resource constraints: [e.g., CPU/Memory limits]
46+
47+
## Error Logs
48+
49+
Please include relevant log output. Use code blocks for formatting:
50+
51+
```
52+
Insert error logs here
53+
```
54+
55+
**Controller Logs:**
56+
```bash
57+
kubectl logs -n nephoran-system deployment/nephio-bridge --tail=100
58+
```
59+
60+
**LLM Processor Logs:**
61+
```bash
62+
kubectl logs -n nephoran-system deployment/llm-processor --tail=100
63+
```
64+
65+
**System Events:**
66+
```bash
67+
kubectl get events -n nephoran-system --sort-by='.lastTimestamp'
68+
```
69+
70+
## Configuration Files
71+
72+
Please include relevant configuration files:
73+
74+
**NetworkIntent Resource:**
75+
```yaml
76+
# Include the NetworkIntent that caused the issue
77+
```
78+
79+
**Values/Config:**
80+
```yaml
81+
# Include relevant Helm values or configuration
82+
```
83+
84+
## Screenshots/Recordings
85+
86+
If applicable, add screenshots or screen recordings to help explain the problem.
87+
88+
## Impact Assessment
89+
90+
**Severity:** [Critical/High/Medium/Low]
91+
92+
**Impact Description:**
93+
- How does this affect your usage?
94+
- Is there a workaround available?
95+
- How many users/systems are affected?
96+
97+
## Additional Context
98+
99+
Add any other context about the problem here:
100+
- Does this happen consistently or intermittently?
101+
- When did this first occur?
102+
- Has this ever worked correctly?
103+
- Any recent changes that might be related?
104+
105+
## Possible Solution
106+
107+
If you have ideas on how to fix this, please share them here.
108+
109+
## Checklist
110+
111+
Please confirm the following:
112+
113+
- [ ] I have searched the existing issues to make sure this hasn't been reported before
114+
- [ ] I have provided sufficient information to reproduce the issue
115+
- [ ] I have included relevant logs and error messages
116+
- [ ] I have tested with the latest version of the software
117+
- [ ] I have provided environment details
118+
119+
---
120+
121+
**Thank you for taking the time to report this bug! We'll investigate and respond as soon as possible.**

‎.github/ISSUE_TEMPLATE/documentation.md‎

Lines changed: 144 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,144 @@
1+
---
2+
name: Documentation Issue
3+
about: Report missing, incorrect, or unclear documentation
4+
title: "[DOCS] "
5+
labels: ["documentation", "needs-triage"]
6+
assignees: []
7+
---
8+
9+
## Documentation Issue Type
10+
11+
- [ ] Missing documentation
12+
- [ ] Incorrect/outdated information
13+
- [ ] Unclear or confusing content
14+
- [ ] Typo or grammatical error
15+
- [ ] Broken links or references
16+
- [ ] Missing examples
17+
- [ ] Translation issue
18+
- [ ] Accessibility issue
19+
20+
## Location
21+
22+
**Document/Page:** [e.g., Getting Started Guide, API Reference, etc.]
23+
**URL/Path:** [e.g., docs/getting-started.md, https://docs.nephoran-project.org/api]
24+
**Section:** [e.g., Installation, Configuration, Examples]
25+
26+
## Issue Description
27+
28+
**What is missing, incorrect, or unclear?**
29+
A clear and concise description of the documentation issue.
30+
31+
**Current Content** (if applicable):
32+
```
33+
Copy the current text that has issues
34+
```
35+
36+
**Expected/Corrected Content:**
37+
```
38+
What the content should say instead
39+
```
40+
41+
## Impact
42+
43+
**Who does this affect?**
44+
- [ ] New users trying to get started
45+
- [ ] Developers integrating with the system
46+
- [ ] System administrators deploying in production
47+
- [ ] Contributors to the project
48+
- [ ] All users
49+
- [ ] Other: _____________
50+
51+
**Severity:**
52+
- [ ] Critical (blocks user progress completely)
53+
- [ ] High (causes significant confusion or delays)
54+
- [ ] Medium (minor confusion or inefficiency)
55+
- [ ] Low (cosmetic or nice-to-have improvement)
56+
57+
## Context
58+
59+
**What were you trying to accomplish?**
60+
Describe the task or goal you were working on when you encountered this issue.
61+
62+
**User Journey:**
63+
1. Started at [location/page]
64+
2. Followed instructions to [action]
65+
3. Expected to [expected outcome]
66+
4. Actually encountered [actual outcome]
67+
68+
**Environment/Setup:**
69+
If relevant, describe your environment:
70+
- Operating System: [e.g., macOS, Ubuntu, Windows]
71+
- Experience Level: [e.g., Beginner, Intermediate, Expert]
72+
- Use Case: [e.g., Development, Testing, Production]
73+
74+
## Suggestions
75+
76+
**Proposed Solution:**
77+
How do you think this should be fixed or improved?
78+
79+
**Additional Content Needed:**
80+
- [ ] More detailed explanation
81+
- [ ] Code examples
82+
- [ ] Screenshots or diagrams
83+
- [ ] Step-by-step instructions
84+
- [ ] Troubleshooting section
85+
- [ ] FAQ entries
86+
- [ ] Cross-references to related topics
87+
- [ ] Video tutorials
88+
- [ ] Other: _____________
89+
90+
## Examples and References
91+
92+
**Good Examples:**
93+
Point to other documentation (internal or external) that handles this topic well.
94+
95+
**Related Issues:**
96+
Link to related documentation issues or feature requests.
97+
98+
**External Resources:**
99+
Relevant external documentation, standards, or best practices that should be referenced.
100+
101+
## Contribution Offer
102+
103+
**Can you help fix this?**
104+
- [ ] Yes, I can submit a pull request with the fix
105+
- [ ] Yes, I can provide the corrected content
106+
- [ ] Yes, I can review proposed changes
107+
- [ ] Yes, I can help with testing the updated documentation
108+
- [ ] No, but I can provide feedback on proposed solutions
109+
- [ ] No, I cannot contribute directly
110+
111+
**Expertise:**
112+
- [ ] Technical writing
113+
- [ ] Subject matter expertise
114+
- [ ] User experience design
115+
- [ ] Accessibility
116+
- [ ] Translation/localization
117+
- [ ] Visual design (diagrams, screenshots)
118+
119+
## Additional Context
120+
121+
**Screenshots:**
122+
If applicable, add screenshots to help explain the problem.
123+
124+
**Browser/Device Info** (for web documentation):
125+
- Browser: [e.g., Chrome 118, Firefox 119, Safari 17]
126+
- Device: [e.g., Desktop, Mobile, Tablet]
127+
- Screen Reader: [if applicable]
128+
129+
**Related Documentation:**
130+
- Other pages that might need similar updates
131+
- Dependencies or prerequisites that should be mentioned
132+
- Follow-up tasks that might be needed
133+
134+
## Checklist
135+
136+
- [ ] I have searched existing issues to avoid duplicates
137+
- [ ] I have provided specific location information
138+
- [ ] I have described the impact clearly
139+
- [ ] I have included suggestions for improvement
140+
- [ ] I have checked related documentation for consistency
141+
142+
---
143+
144+
**Thank you for helping us improve our documentation! Clear documentation is essential for project success.**

0 commit comments

Comments
 (0)