Patch release notes for 4.8.1

[kcarmichael08]

Version(s): 4.8

Issue

Link to docs preview

QE review: ACS has no QE, approved by SMEs

• QE has approved this change.

Additional information:

[ocpdocs-previewbot]

🤖 Mon Jul 28 15:19:28 - Prow CI generated the docs preview:
https://96433--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

[gaurav-nelson]

Thank you @kcarmichael08

I left a few suggestions. Feel free to not accept any that you believe aren't applicable.

[gaurav-nelson]

Suggested change

	* In {product-title-short} 4.8, Central fails to create a backup due to using `pg_dump` from PostgreSQL version 13 with the PostgreSQL 15 database. With this release, we updated the `pg_dump` version in Central to resolve the backup failures.
	* In {product-title-short} 4.8, Central fails to create a backup because it uses `pg_dump` from PostgreSQL 13 with the PostgreSQL 15 database. This release updates the `pg_dump` version in Central to resolve the backup failures.

nitpick and suggestion: Replace due to using with because it uses or as it uses.
issue: we updated Our style prefers avoiding "we".

[gaurav-nelson]

Suggested change

	* Before this update, the migration of the network flow table during the 4.8 upgrade would take a lot of time, ultimately failing with timeout after 2 hours. With this release, batch network flow updates have been implemented to reduce the migration time.
	* Before this update, the network flow table migration during the {product-title-short} 4.8 upgrade took an extended period, often timing out after 2 hours. This release implements batch network flow updates to reduce the migration time.

[gaurav-nelson]

Suggested change

	* Before this update, the failure of Sensor to call `stream.Recv()` caused gRPC flow control to block image reprocessing every 4 hours. With this update, the reprocessing loop includes a timeout for sending messages to Sensors, which resolves the issue and resumes the image reprocessing as expected.
	* Before this update, Sensor's failure to call `stream.Recv()` caused gRPC flow control to block image reprocessing every 4 hours. This update resolves the issue by including a timeout for sending messages to Sensors in the reprocessing loop, allowing image reprocessing to resume as expected.

[gaurav-nelson]

Suggested change

* Before this update, removing a network entity from the network tree did not properly remove its parent node when it had no children or value, leading to a memory leak. As a consequence, users experienced increased memory usage and potential application crashes, particularly noticeable with external IPs enabled. With this release, the memory leak has been fixed by removing parent nodes when nodes are removed from the network tree. As a result, network tree memory usage is optimized, reducing potential crashes and improving system performance, especially with external IPs enabled.

* Before this update, removing a network entity from the network tree failed to properly remove its parent node when it had no children or value. This led to a memory leak, causing increased memory usage and potential application crashes, especially noticeable when external IPs were enabled. This release resolves the memory leak by ensuring that {product-title-short} removes parent nodes along with their child nodes, optimizing network tree memory usage, reducing potential crashes, and improving system performance, particularly with external IPs enabled.

[gaurav-nelson]

Suggested change

	* Before this update, you could observe excessive logging of telemetry collection status, resulting in log spam. With this update, the telemetry collection has been configured to not emit repeated logs continuously, which resolves the issue and significantly reduces the log volume.
	* Before this update, excessive logging of telemetry collection status resulted in an abundance of log entries. This update configures telemetry collection to not emit repeated logs continuously, resolving the issue and significantly reducing log volume.

[gaurav-nelson]

Suggested change

	* Before this update, there was a time window during which external IPs could be stored in the database while the corresponding deployment had been deleted. This resulted in inaccessible and stale data, and a loss of storage and memory, possibly leading to memory exhaustion. With this release, Central no longer stores external IP information about deleted deployments.
	* Before this update, Central sometimes stored external IPs in the database even after users deleted their corresponding deployments. This resulted in inaccessible and stale data, leading to a loss of storage and memory, and potential memory exhaustion. With this release, Central no longer stores external IP information for deleted deployments, resolving these issues.

[kcarmichael08]

/retest

[openshift-ci]

@kcarmichael08: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[kcarmichael08]

/cherrypick rhacs-docs-4.8

[openshift-cherrypick-robot]

@kcarmichael08: new pull request created: #96765

In response to this:

/cherrypick rhacs-docs-4.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.