Issue 338: CRD template refactor to accommodate different api versions

[lspecian-olx]

Change log description

In order to accommodate the both api versions schemas apiextensions.k8s.io/v1 and apiextensions.k8s.io/v1beta1

• moved openAPIV3Schema as a named template in _helpers.tpl since the schema change moved the object
• the schema change also moved the object additionalPrinterColumns which needed two versions as named templates since the attribute JSONPath was changed to jsonPath

Purpose of the change

Closes #338

What the code does

The code is checking .Capabilities.APIVersions.Has "apiextensions.k8s.io/v1" and adapting the template output accordingly to the support for the apiVersion

How to verify it

Chart is able to install in eks clusters that support both apiVersions apiextensions.k8s.io/v1 and apiextensions.k8s.io/v1beta1

[codecov-commenter]

Codecov Report

Merging #339 (a8a585b) into master (23888a5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #339   +/-   ##
=======================================
  Coverage   84.90%   84.90%           
=======================================
  Files          11       11           
  Lines        1358     1358           
=======================================
  Hits         1153     1153           
  Misses        135      135           
  Partials       70       70           

---

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 23888a5...a8a585b. Read the comment docs.

[anishakj]

@lspecian-olx , how you have generated crd file? Is there any tools used

[lspecian-olx]

@lspecian-olx , how you have generated crd file? Is there any tools used

hello @anishakj, I used only helm templates, not sure if I understood the question

[anishakj]

@lspecian-olx , how you have generated crd file? Is there any tools used

hello @anishakj, I used only helm templates, not sure if I understood the question

Have you used any commands like operator-sdk generate crds ,but have seen that operator-sdk generate crd with v1beta1 version

[anishakj]

@lspecian-olx, could you please resolve the conflict?

[anishakj]

@lspecian-olx Looks like there is parse error after conflicts are resolved. Getting below error while try to install

Error: YAML parse error on zookeeper-operator/templates/zookeeper.pravega.io_zookeeperclusters_crd.yaml: error converting YAML to JSON: yaml: line 70: could not find expected ':'

[hansh0801]

thanks!

[SrishT]

Just a very minor comment needs to be addressed, otherwise LGTM

[anishakj]

LGTM

[SrishT]

LGTM