Remove Entanglement code from Quarks Job

[rohitsakala]

#172404604

I think we should not put entanglement logic inside QuarksJob since it is not the feature of QuarksJob

Part of cloudfoundry-incubator/quarks-operator#909

[manno]

Is it really possible to do this? I was under the impression, that the annotation has a generated value, which in case of 'FanOut' the cf-operator can not predict.

https://github.com/cloudfoundry-incubator/quarks-job/blob/master/pkg/kube/controllers/quarksjob/output_persistor.go#L150

This value depends on the keys in the secrets data. Does this really work for all use-cases, when it's the same value for all?

https://www.pivotaltracker.com/n/projects/2192232/stories/171433464 made that label necessary (I thought at the time;).

[rohitsakala]

Is it really possible to do this? I was under the impression, that the annotation has a generated value, which in case of 'FanOut' the cf-operator can not predict.

https://github.com/cloudfoundry-incubator/quarks-job/blob/master/pkg/kube/controllers/quarksjob/output_persistor.go#L150

This value depends on the keys in the secrets data. Does this really work for all use-cases, when it's the same value for all?

https://www.pivotaltracker.com/n/projects/2192232/stories/171433464 made that label necessary (I thought at the time;).

@manno I realiased there is nothing to update here after our conversation. Please re-review.