cncf
[Sandbox] Reloader
Application contact emails
Project Summary
A Kubernetes controller to watch changes in ConfigMap and Secrets and do rolling upgrades on Pods with their associated Deployment, StatefulSet, DaemonSet and DeploymentConfig
Project Description
The problem Reloader addresses is that you would like to watch if some change happens in a ConfigMap or Secret, and then perform a rolling upgrade on the relevant DeploymentConfig, Deployment, Daemonset, Statefulset, and Rollout. Reloader can watch changes in ConfigMap and Secret objects and do rolling upgrades on Pods with their associated DeploymentConfigs, Deployments, Daemonsets, Statefulsets, and Rollouts.
Org repo URL (provide if all repos under the org are in scope of the application)
N/A
Project repo URL in scope of application
https://github.com/stakater/reloader/
Additional repos in scope of the application
No response
Website URL
https://docs.stakater.com/reloader/
Roadmap
https://github.com/orgs/stakater/projects/4
Roadmap context
The roadmap is continuously updated through the GitHub project
Contributing Guide
https://github.com/stakater/Reloader#contributing
Code of Conduct (CoC)
https://github.com/stakater/Reloader/blob/master/CODE_OF_CONDUCT.md
Adopters
No response
Contributing or Sponsoring Org
Stakater
Maintainers file
https://github.com/stakater/Reloader/blob/master/MAINTAINERS
IP Policy
- [X] If the project is accepted, I agree the project will follow the CNCF IP Policy
Trademark and accounts
- [X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF
Why CNCF?
The CNCF can provide the project with wider adoption and community collaboration, further simplifying and enhancing updates of Kubernetes resources when secrets or configurations change in Kubernetes environments.
Benefit to the Landscape
Reloader uniquely addresses the problem of doing rolling updates of Kubernetes resources when configurations or secrets change.
Cloud Native 'Fit'
No response
Cloud Native 'Integration'
No response
Cloud Native Overlap
No response
Similar projects
N/A
Landscape
No
Business Product or Service to Project separation
N/A
Project presentations
No response
Project champions
No response
Additional information
No response
Please open a presentation issue with TAG security so that we can provide the TAG review. It may be useful to perform a self assessment before the presentation.
Some questions:
- The repo appears to be some less active, not many changes occurring. Is this project near feature complete/stable?
- what is stakater-user in relation to this repo?
- When is SHA1 going to be replaced with SHA2? SHA1 was deprecated in 2011.
- The project roadmap doesnt detail much future direction for the project, are there plans to extend the project beyond its current capabilities?
Actions:
- please complete the remaining fields on the application, in particular:
- the business product and service separation as the project's repo indicates enterprise level support available by the same name.
- Cloud native fit
Don't Kubernetes' default controller already do what is described here? What additional functionality is being added/proposed? Other triggers other than k8s image field? How are reverts happening etc.
TAG Contributor strategy has reviewed this project and found the following:
- The contributor guide is basic.
- The project has no written governance, yet.
- The roadmap is a Github project board and appears to be very new.
- There are 5 maintainers, whose employer affiliation is not clear. Two of these maintainers appear to be currently active.
- The project is at least 6 years old.
This review is for the TOC’s information only. Sandbox projects are not required to have full governance or contributor documentation.
