Re:Beyond CI/CD: GitLab's DevOps Vision (2017)
by akvadrako on Monday March 19, 2018 @08:15AM
(#16617781)
That doesn't explain it. You always need some global variable saying what the current state is. In your case, maybe it's the branch pointer in your git tree. In the k8s deployment, it's a tag value.
[ Parent
| on HN ]
Re:Beyond CI/CD: GitLab's DevOps Vision (2017)
by tazjin on Monday March 19, 2018 @08:23AM
(#16617813)
No, those don't contain the same information.
Our Kontemplate repository contains the state of an entire cluster, including all versions and all configuration.
A tag value is a single piece of mutable data that is in no relation to the other relevant data.
Re:Beyond CI/CD: GitLab's DevOps Vision (2017)
by akvadrako on Monday March 19, 2018 @09:02AM
(#16618007)
The tag points to the current version of your docker image, which contains the current configuration, except secrets which you don't want in a repo. Older deployments point to the older docker images which contain the older versions.
Still don't see any advantage to justify the additional complexity in your system.
Re:Beyond CI/CD: GitLab's DevOps Vision (2017)
by tazjin on Monday March 19, 2018 @09:26AM
(#16618155)
We have more than one service, more than one environment, and auditability requirements (due to being a financial institution).
I find it more complex to try and keep track of remote state modifications than to have a single source of truth, but whatever floats your boat ;-)