From 003eaee887dae0b33a767ac30b49475a95ee31a9 Mon Sep 17 00:00:00 2001 From: Faizan Ahmad Date: Wed, 1 Aug 2018 14:41:45 +0500 Subject: [PATCH] [STK-322] Add reloader vs k8s-trigger-controller doc (#13) * Add reloader vs k8s-trigger-controller doc * Fix kubectl command in readme --- docs/Reloader-vs-k8s-trigger-controller.md | 28 ++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 docs/Reloader-vs-k8s-trigger-controller.md diff --git a/docs/Reloader-vs-k8s-trigger-controller.md b/docs/Reloader-vs-k8s-trigger-controller.md new file mode 100644 index 0000000..f6bb564 --- /dev/null +++ b/docs/Reloader-vs-k8s-trigger-controller.md @@ -0,0 +1,28 @@ +# 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]` \ No newline at end of file