Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[jaeger-operator] Sync the CRD for 1.17 #28

Closed
jpkrohling opened this issue Jan 10, 2020 · 2 comments
Closed

[jaeger-operator] Sync the CRD for 1.17 #28

jpkrohling opened this issue Jan 10, 2020 · 2 comments

Comments

@jpkrohling
Copy link
Contributor

Based on #20, this issue is a heads-up that the CRD file has been changed in the Operator's master and will be released as part of 1.17.

jaegertracing/jaeger-operator#819

@jpkrohling jpkrohling changed the title Update the CRD for 1.17 Sync the CRD for 1.17 Jan 10, 2020
@naseemkullah naseemkullah changed the title Sync the CRD for 1.17 [jaeger-operator] Sync the CRD for 1.17 Jan 18, 2020
@bsundsrud
Copy link

I would like to bump this for 1.18 as well, just ran into a bunch of errors after deploying the operator and an instance like the following:

time="2020-07-08T10:16:25Z" level=error msg="failed to store the running status into the current CustomResource" error="jaegers.jaegertracing.io \"jaeger-instance\" not found" execution="2020-07-08 10:16:25.341972774 +0000 UTC" instance=jaeger-instance namespace=observability

And found out I needed to apply the CRD that matched the version, and I assumed that the operator chart had taken care of that.

@naseemkullah
Copy link
Member

cc @cpanato @batazor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants