Marked specific fields as nullable to keep backwards compatibility

[jpkrohling]

When a CR like the following is applied, the current CRD validation will complain that it's invalid:

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: simplest
spec:
  resources:

The Jaeger "simplest" is invalid: spec.resources: Invalid value: "null": spec.resources in body must be of type object: "null"

To keep backwards compatibility, we want to mark a few fields as nullable. With this PR, the YAML specified above is accepted.

Signed-off-by: Juraci Paixão Kröhling [email protected]

[codecov]

Codecov Report

Merging #985 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #985   +/-   ##
=======================================
  Coverage   64.44%   64.44%           
=======================================
  Files          82       82           
  Lines        6526     6526           
=======================================
  Hits         4206     4206           
  Misses       2178     2178           
  Partials      142      142           

Impacted Files	Coverage Δ
pkg/apis/jaegertracing/v1/jaeger_types.go	100.00% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cc2cff4...d1eeea9. Read the comment docs.

[objectiser]

LGTM, subject to CI passing and testing with maistra.

[kevinearls]

LGTM. I was able to reproduce the initial problem, and then applying this PR fixed it.

[jpkrohling]

Merging, but the verification that this is sufficient to address Maistra's problems is still pending.

[objectiser]

@pavolloffay Could you update the CRD from this PR to the upstream operatorhub PRs for 1.17.1?