-
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
Preparing release v1.59.0 #2608
Conversation
Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
CHANGELOG.md
Outdated
@@ -1,5 +1,9 @@ | |||
Changes by Version | |||
================== | |||
## v1.58.0 (2024-05-06) | |||
* Final deprecation of jaeger agent. Agents injected by the operator are no longer updated. newly created or updated Jaeger CRs with an agent configuration will be rejected. ([#2497](https://github.com/jaegertracing/jaeger-operator/pull/2497), [@frzifus](https://github.com/frzifus)) |
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.
Could we document recommendation to use OTEL collector?
@frzifus I think it would make sense reject the request to the webhook when the |
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.
We can probably remove the daemonset code as well https://github.com/jaegertracing/jaeger-operator/blob/d6204bc2296648ee130c039ecfc4e8e71ca6a19a/pkg/inventory/daemonset.go
Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
Some deployments fail:
|
a0575d6
to
eb87342
Compare
If otlp is enabled and no explicit port for grpc or http is configured, we change the default address from |
Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
@@ -15,7 +15,7 @@ metadata: | |||
capabilities: Deep Insights | |||
categories: Logging & Tracing | |||
certified: "false" | |||
containerImage: quay.io/jaegertracing/jaeger-operator:1.56.0 | |||
containerImage: quay.io/jaegertracing/jaeger-operator:1.59.0 |
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.
Seems the 1.57
release did ship an old image. :b
@@ -15,7 +15,7 @@ metadata: | |||
capabilities: Deep Insights | |||
categories: Logging & Tracing | |||
certified: "false" | |||
containerImage: quay.io/jaegertracing/jaeger-operator:1.56.0 | |||
containerImage: quay.io/jaegertracing/jaeger-operator:1.59.0 | |||
createdAt: "2023-05-16T04:47:12Z" |
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.
Curious why you capture the date.
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.
Which date are you referring to? createdAt
is displayed on the openshift operator hub and the community version (example).
AFAIK it has no additional meaning. While looking at it, its a but weird, that there is no updatedAt
filed.
208ed5f
to
2e9ab66
Compare
Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
config/manifests/bases/jaeger-operator.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: Ben B. <bongartz@klimlive.de>
|
||
# DO NOT EDIT the next value, it is updated automatically during the release. | ||
# Represents the current (latest) release of the Jaeger Operator. | ||
operator=1.57.0 | ||
operator=1.59.0 |
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.
https://github.com/jaegertracing/jaeger-operator/blob/main/RELEASE.md#releasing
Change the versions.txt so that it lists the target version of the Jaeger (if it is required). Don't touch the operator version: it will be changed automatically in the next step.
Maybe you want to skip 1.59 and go to 1.60 (just released)? |
Signed-off-by: Ben B. <bongartz@klimlive.de>
Which problem is this PR solving?
Description of the changes
How was this change tested?
Checklist
jaeger
:make lint test
jaeger-ui
:yarn lint
andyarn test