[jaeger-operator] Helm skipping crd-install hook

[csp197]

Hello!

I've been trying to install the Jaeger Operator into a namespace of an EKS cluster using the prescribed helm charts, but my build pipeline starts to fail upon setting the following configuration in the values.yaml file:

jaeger:
  # Specifies whether Jaeger instance should be created
  create: true

Below are the appropriate logs re: this issue:

Release "jaeger-operator" does not exist. Installing it now.
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Jaeger" in version "jaegertracing.io/v1"
ERROR: Job failed: command terminated with exit code 1

[vincenthcui]

@CSP197 Hi, I create a pull request trying to solve this problem, plz pull the source code and test in your local cluster.

[csp197]

Hi @vincenthcui I resolved this issue by installing the Jaeger Operator using the helm chart first, and then later creating the Jaeger Operator after installation.

I see that you have an open PR regarding this issue, so I'll leave the issue open until it gets merged. 👍

[m1o1]

I ran into this when I added the jaeger-operator chart as a dependency to my chart. It skipped installing crds, I assume because I was running "helm upgrade --install" and my chart was already installed, so it did an upgrade. When I uninstalled my chart and reran the command, it installed the CRDs properly.

I know this might just be a helm thing though (since helm doesn't let you add CRDs during upgrades for some reason, which is effectively what I did when I added this as a dependency). Just pointing it out in case someone runs into the same issue.