[08:13:31] <akosiaris>	 looks like the earth day meeting has been cancelled already in the gcal. 
[09:12:03] <elukey>	 I am not sure what is the best venue to talk about the Docker Registry state, but it would be nice to discuss future steps together
[09:12:13] <elukey>	 like short/medium/long plans etc..
[09:12:27] <elukey>	 we can also form a separate group of people for it
[09:20:04] <akosiaris>	 So, an update that I have is that the docker-registry work has been approved as EW for next FY. So yes, we will have to create that group of people, document the problems, propose and decide/settle on solutions and implement them. 
[09:20:43] <akosiaris>	 but that doesn't cover this Q, so this doesn't apply to "short term" plans
[09:22:20] <elukey>	 also medium, for example if we want to have a hybrid solution of docker-distribution supported by S3/apus for some use cases
[09:22:27] <elukey>	 etc..
[09:22:31] <elukey>	 anyway, +1 for the group :)
[14:21:21] <federico3>	 akosiaris: hello, can I merge https://gerrit.wikimedia.org/r/c/operations/deployment-charts/+/1135414  as it is? 
[14:41:14] <elukey>	 federico3: if you need reviews for deployment-charts in the future feel free to drop a note here
[14:43:42] <akosiaris>	 federico3: reviewing
[14:49:07] <claime>	 we've moved on to testing the deployment
[14:49:08] <federico3>	 akosiaris: we are deploying it with claime, I'll send a small change in a bit
[14:49:18] <claime>	 which is failing because of the livenessProbe definition
[14:49:35] <claime>	 There'll be more things to change, namely adding the mysql egress
[14:49:41] <claime>	 + secrets
[14:51:50] <akosiaris>	 I 've left a couple of comments anyway
[14:52:07] <akosiaris>	 next thing you 'll meet is indeed the egress 
[14:52:59] <federico3>	 thanks
[14:54:56] <federico3>	 (in the initial iteration there is/was no need for secrets and egress)
[15:09:10] <federico3>	 is there a required or preferred version naming scheme? Many charts use <timestamp>-production
[15:11:16] <akosiaris>	 the pipeline should be giving you already a couple of options. the <timestamp>-production is standard
[15:11:29] <akosiaris>	 there is another one which is the sha of the git commit
[15:11:37] <federico3>	 also, how is the version being updated on new commits/tags in the "upstream" repo?
[15:11:51] <akosiaris>	 and you can ofc also git tag and the git tag is used as a docker tag
[15:18:57] <akosiaris>	 every commit merged/pushed should trigger the pipeline btw. 
[15:48:27] <claime>	 you can probably have the pipeline create the deployment-charts CR to point to the new tag
[15:48:40] <claime>	 but you won't escape having to +2/merge/helmfile apply it
[15:50:21] <claime>	 akosiaris: that's possible right ^ ?
[15:50:55] <akosiaris>	 yes, the pipeline can create the CR
[15:51:07] <akosiaris>	 but there is no CD (and for good reasons)
[15:51:34] <akosiaris>	 mathoid is the example to copy if interested
[15:52:32] <federico3>	 even for staging.... (once it be available)... ?