mirror of
https://github.com/stakater/Reloader.git
synced 2026-08-20 12:36:26 +00:00
Faizan AhmadandRasheed Amir
003eaee887
* Add reloader vs k8s-trigger-controller doc * Fix kubectl command in readme
28 lines
992 B
Markdown
28 lines
992 B
Markdown
# Reloader vs k8s-trigger-controller
|
|
|
|
Reloader and k8s-trigger-controller are both built for same purpose. So there are quite a few similarities and differences between these.
|
|
|
|
## Similarities
|
|
|
|
- Both controllers support change detection in configmap and secrets
|
|
- Both controllers support deployment rollout
|
|
- Both controllers use SHA1 for hashing
|
|
- Both controllers have end to end as well as unit test cases.
|
|
|
|
## Differences
|
|
|
|
### Support for Daemonsets and Statefulsets.
|
|
|
|
#### k8s-trigger-controller:
|
|
k8s-trigger-controller only support for deployment rollout. It does not support daemonsets and statefulsets rollout.
|
|
|
|
#### Reloader:
|
|
Reloader supports deployment rollout as well as daemonsets and statefulsets rollout.
|
|
|
|
### Hashing usage
|
|
|
|
#### k8s-trigger-controller:
|
|
k8s-trigger-controller stores the hash value in an annotation `trigger.k8s.io/[secret|configMap]-NAME-last-hash`
|
|
|
|
#### Reloader:
|
|
Reloader stores the hash value in an environment variable `STAKATER_NAME_[SECRET|CONFIGMAP]` |