Add AnalysisTemplate & update logic for canary rollout strategy

[j-jasmin]

Changes made:

• make stable(Service|Metadata) and canary(Service|Metadata) depending on whether useTrafficRouting is true for a canary rollout
• make preview service creation depending on whether useTrafficRouting is true or rollout.strategy is BlueGreen
• add steps to control progress of canary rollouts
• add option to create AnalysisTemplate
• add option to subscribe on rollout events and sent slack notifications
• add progressDeadlineSeconds with default kubernetes value
• add minReadySeconds with default kubernetes value
• add progressDeadlineAbort for argo rollouts

[bastianeicher]

I'd prefer to keep this more generalized, since not everybody uses Slack for notifications. Perhaps we could just use the existing annotations for this?

[j-jasmin]

Yeah that's what I initially wanted to do but it would add the annotation to all resources while it would be only needed for Rollout?

[bastianeicher]

generic-service applies labels to all resources but annotations only to the resource created in controller.yaml, Rollout in this case.

[j-jasmin]

removed it 👍

[bastianeicher]

with doesn't seem necessary here.

Indent seems to be too deep. Would put analysis under trafficRouting.

Suggested change

	{{- with .Values.rollout.analysis -}}
	analysis: {{- . | toYaml | nindent 8 }}
	{{- end }}
	analysis: {{- .Values.rollout.analysis | toYaml | nindent 8 }}

[j-jasmin]

analysis is an optional field (with or without traffic routing). see rollout specs

[bastianeicher]

Then perhaps like this?

Suggested change

	{{- with .Values.rollout.analysis -}}
	analysis: {{- . | toYaml | nindent 8 }}
	{{- end }}
	{{- if .Values.rollout.analysis }}
	analysis: {{- . | toYaml | nindent 8 }}
	{{- end }}