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

[release-2.8] [2.9 Manual Backport] Support messages that are greater than 1024 characters #409

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #408

/assign mprahl

The v1 Event API supports large messages, but if new fields are
specified, the Kubernetes API converts it to a events.k8s.io/v1 Event
which has a limit of 1024 characters.

The solution was to stop setting the eventTime field so that it stays a
v1 Event.

Relates:
https://issues.redhat.com/browse/ACM-13720

Signed-off-by: mprahl <[email protected]>
Coverage merging is failing in Go versions older than 1.22 because a gocovmerge
dependency requires Go 1.22. gocovmerge isn't a module, so there is no versions
pinned, so go install uses the latest version of the dependency which
causes the failure.

Signed-off-by: mprahl <[email protected]>
Copy link

sonarcloud bot commented Oct 2, 2024

Copy link

openshift-ci bot commented Oct 2, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhaiducek, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Oct 2, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit da4beaa into stolostron:release-2.8 Oct 2, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants