-
Notifications
You must be signed in to change notification settings - Fork 344
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
Added note about the apiVersion used up to 1.10.0 #283
Added note about the apiVersion used up to 1.10.0 #283
Conversation
Codecov Report
@@ Coverage Diff @@
## master #283 +/- ##
======================================
Coverage 89.8% 89.8%
======================================
Files 64 64
Lines 3011 3011
======================================
Hits 2704 2704
Misses 207 207
Partials 100 100 Continue to review full report at Codecov.
|
@objectiser, is this OK to be merged? |
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/service_account.yaml | ||
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/role.yaml | ||
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/role_binding.yaml | ||
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/operator.yaml | ||
---- | ||
<1> This creates the namespace used by default in the deployment files. | ||
<2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` | ||
|
||
IMPORTANT: when using a Jaeger Operator up to v1.10.0, install the CRD file `io_v1alpha1_jaeger_crd.yaml` in addition to `jaegertracing_v1_jaeger_crd.yaml`. This is because up to that version, the `apiVersion` in use was `io.jaegertracing/v1alpha1`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this notice be included below aswell?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added. Our ultimate goal is to remove the OpenShift-specific instructions, but until that, we should indeed duplicate the instructions.
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
dc0ccf8
to
cf6d9f1
Compare
Signed-off-by: Juraci Paixão Kröhling [email protected]