Explore expanding log message regarding update in CR hash
The following discussion from !131 (merged) should be addressed:
-
@mnielsen started a discussion: (+2 comments) Something intriguing from the logs: when pushing a change to the CR, it says the template signature has changed, but when it renders the new template the hash comes out with the same value. Since we include the values in the hash, I would have expected that hash value to change
🤔 (Does not appear to be a blocker)│ manager 2021-04-12T19:15:04.410Z INFO controllers.GitLab Reconciling GitLab {"gitlab": "gitlab-system/gitlab"} │ │ manager 2021-04-12T19:15:04.411Z DEBUG template Template signature has changed. Evicting it now. {"namespace": "gitlab-system", "releaseName": "gitlab", "hash": "d8e1c1effff6ae5d"} │ │ manager 2021-04-12T19:15:04.411Z INFO template Rendering a new template. {"namespace": "gitlab-system", "releaseName": "gitlab", "hash": "d8e1c1effff6ae5d"} │ │ manager 2021-04-12T19:15:04.411Z DEBUG template Looking for the designated GitLab Chart in the specified directory. {"chartVersion": "4.9.1", "directory": "/charts"} │ │ kube-rbac-proxy I0412 19:08:25.007467 1 main.go:186] Valid token audiences: │ │ kube-rbac-proxy I0412 19:08:25.007596 1 main.go:232] Generating self signed cert as no cert is provided │ │ kube-rbac-proxy I0412 19:08:25.226777 1 main.go:281] Starting TCP socket on 0.0.0.0:8443 │ │ kube-rbac-proxy I0412 19:08:25.230993 1 main.go:288] Listening securely on 0.0.0.0:8443 │ │ manager 2021-04-12T19:15:28.893Z DEBUG template The template is rendered. Check the warnings (if any). {"namespace": "gitlab-system", "releaseName": "gitlab", "hash": "d8e1c1effff6ae5d", "warnings": 0} │ │ manager 2021-04-12T19:15:28.893Z DEBUG template Caching the template. {"namespace": "gitlab-system", "releaseName": "gitlab", "hash": "d8e1c1effff6ae5d"}