Conversation
joshgav
left a comment
There was a problem hiding this comment.
Nice work, thank you! A few comments inline.
Could you rename the file to 2026-01-30.md to match the convention for other reviews?
Signed-off-by: Kashif Khan <kashif.khan@est.tech>
bb2ac9d to
8334d55
Compare
joshgav
left a comment
There was a problem hiding this comment.
Thanks for your work @kashifest! LGTM.
|
|
||
| ## Overall Assessment | ||
|
|
||
| This technical review finds k8gb to be overall satisfactory for progression from Sandbox to Incubation status. The project demonstrates strong technical maturity with a well-architected, Kubernetes-native solution that's proven in production by multiple adopters. Security practices are adequate. The documentation is thorough with clear tutorials and integration guides. The multi-cluster distributed architecture eliminates single points of failure and follows cloud-native principles effectively. |
There was a problem hiding this comment.
| This technical review finds k8gb to be overall satisfactory for progression from Sandbox to Incubation status. The project demonstrates strong technical maturity with a well-architected, Kubernetes-native solution that's proven in production by multiple adopters. Security practices are adequate. The documentation is thorough with clear tutorials and integration guides. The multi-cluster distributed architecture eliminates single points of failure and follows cloud-native principles effectively. | |
| This technical review finds k8gb to be overall satisfactory for progression from Sandbox to Incubation status. The project demonstrates strong technical maturity with a well-architected, Kubernetes-native solution that's proven in production by multiple adopters. Security practices are adequate. The documentation is thorough with clear tutorials and integration guides. The multi-cluster distributed architecture eliminates single points of failure and follows cloud native principles effectively. |
Cloud native, by definition, is not hyphenated
| * How do you recommend users alter security defaults in order to "loosen" the security of the project? Please link to any documentation the project has written concerning these use cases. | ||
| * I don't recommend loosening security, but if you really need to, you can modify the security context through [Helm values](https://github.com/k8gb-io/k8gb/blob/master/chart/k8gb/values.yaml). |
There was a problem hiding this comment.
To clarify what this question is asking: the expectation is that projects are hardened by default. If an adopter has specific needs that are incompatible with the locked down and fully hardened out-of-the-box configuration of the project, the "loosening" guide is intended to inform users what configuration changes they may make and the corresponding impact on the security of the project's use in their environment.
Closes #2021
cc @joshgav @TheFoxAtWork @rochaporto