Automated chart bump jaeger-operator-2.18.4

[d2iq-dispatch]

What type of PR is this?
Chore

What this PR does/ why we need it:
Bump jaeger.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

bump jaeger-operator-2.18.4

Checklist

• If a chart is changed, the chart version is correctly incremented.
• The commit message explains the changes and why are needed.
• The code builds and passes lint/style checks locally.
• The relevant subset of integration tests pass locally.
• The core changes are covered by tests.
• The documentation is updated where needed.

[joejulian]

@GoelDeepak I assume you just want to close this?

[vespian]

I assume you just want to close this?

We just need to manually fix this. It was in my queue, but during the release time it was of low priority.

Fixing it now.

[vespian]

@mesosphere/sig-ksphere-catalog Can I have a review?

[vespian]

@joejulian @orsenthil Do you know what is the Mergable check? It does not allow me to merge PR, and does not clarify which label is missing either :(

[joejulian]

@vespian If you go in to Details and look at Mergeable, there's this.

We started a really short discussion about making Mergeable add comments to state the same that can be found there. Would that be a desired behavior to you?

[joejulian]

If you were an administrator for a production cluster and you wanted to know whether or not to upgrade your addons to this version, is this a valuable release note for you?

Personally, I would prefer to see what features or bug fixes that bump brings so I know whether it's something that helps me. That's what I look for in release notes, fwiw.

[joejulian]

As an example:
https://github.com/mesosphere/kubernetes-base-addons/blob/master/RELEASE_NOTES.md#stable-118-300

I think cert-manager is a little bit too verbose, listing items that are trivial and don't apply to users. Those things that do, like "v1 API" don't have enough detail, like "This is a complete replacement of the v1alpha1 CRDs. This upgrade will change all necessary resources to use the new API. This upgrade cannot be reverted."

Dex is good. If I wasn't even noticing a lack of metrics from dex, this would alert me to it and make me want to upgrade.

Istio is way too verbose. It's effectively a copy-paste of upstream's auto-generated release notes that include a lot of trivial notes that have no user-facing impact.

[vespian]

We started a really short discussion about making Mergeable add comments to state the same that can be found there. Would that be a desired behavior to you?

No, the way it is now is way clearer. I am just not used to the Details link having useful data in PR status checks.

[vespian]

If you were an administrator for a production cluster and you wanted to know whether or not to upgrade your addons to this version, is this a valuable release note for you?

Depends on how much resources we have at our disposal.

Ideally yes - as an admin, I would appreciate my vendor to summarise the changes for me in just one place. In our current situation though I am struggling to find time to keep the bumps going and do not let #sig-networking slip into abandonment. Networking stuff it is not a priority ATM.

Thanks for understanding.

[joejulian]

@mesosphere-mergebot backport release/3.3

[d2iq-mergebot]

Backport PR for release/3.3: #918