docs: blog about 5.3.0 release#3205
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
There was a problem hiding this comment.
Pull request overview
Adds the release blog post for Java Operator SDK v5.3.0, summarizing the main new features, migration notes, and getting-started guidance for users.
Changes:
- Introduces a new
v5-3-release.mdrelease announcement covering key features (read-cache-after-write consistency, Micrometer metrics v2, config loaders, MDC changes, etc.). - Adds migration notes and pointers to docs/resources (migration guide, observability docs, comparison view).
You can also share your feedback on Copilot code review. Take the survey.
|
|
||
| ### Informer Health Checks | ||
|
|
||
| Informers health status no longer checks `isWacthing`. For ready and startup probes mainly `hasSynced` |
There was a problem hiding this comment.
Typo in method name: isWacthing should be isWatching (matches InformerHealthIndicator.isWatching() in the codebase).
| Informers health status no longer checks `isWacthing`. For ready and startup probes mainly `hasSynced` | |
| Informers health status no longer checks `isWatching`. For ready and startup probes mainly `hasSynced` |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.
You can also share your feedback on Copilot code review. Take the survey.
| | Meter | Type | Description | | ||
| |---|---|---| | ||
| | `reconciliations.active` | gauge | Reconciler executions currently running | | ||
| | `reconciliations.queue` | gauge | Resources queued for reconciliation | | ||
| | `custom_resources` | gauge | Resources tracked by the controller | | ||
| | `reconciliations.execution.duration` | timer | Execution duration with explicit histogram buckets | | ||
| | `reconciliations.started.total` | counter | Reconciliations started | | ||
| | `reconciliations.success.total` | counter | Successful reconciliations | | ||
| | `reconciliations.failure.total` | counter | Failed reconciliations | | ||
| | `reconciliations.retries.total` | counter | Retry attempts | | ||
| | `events.received` | counter | Kubernetes events received | |
There was a problem hiding this comment.
These Markdown table rows start with a double pipe (||), which typically renders as an extra empty column (or a malformed table) in many renderers. Consider changing them to single-pipe table rows (e.g., | Meter | Type | Description |, | --- | --- | --- |, etc.) so the table renders consistently.
| | v5.2 | v5.3 | | ||
| |---|---| | ||
| | `reconcileCustomResource` | `reconciliationSubmitted` | | ||
| | `reconciliationExecutionStarted` | `reconciliationStarted` | | ||
| | `reconciliationExecutionFinished` | `reconciliationSucceeded` | | ||
| | `failedReconciliation` | `reconciliationFailed` | | ||
| | `finishedReconciliation` | `reconciliationFinished` | | ||
| | `cleanupDoneFor` | `cleanupDone` | | ||
| | `receivedEvent` | `eventReceived` | |
There was a problem hiding this comment.
Same as the meters table above: the migration table uses || at the start of each row, which can introduce an unintended empty column. Use single-pipe rows to ensure correct Markdown rendering across site generators.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Adds blog post for 5.3 release.
Signed-off-by: Attila Mészáros a_meszaros@apple.com