Repository navigation
docs: document automatic plugin reload on pod rollout - #10935
Merged
Merged
Conversation
cnpg-bot
added
backport-requested ◀️
Contributor
|
❗ By default, the pull request is configured to backport to all release branches.
|
dosubot
Bot
added
size:XS
mnencia
force-pushed
the
dev/plugin-reload-docs
branch
from
June 17, 2026 16:29
97dfe06 to
ad18109
Compare
Member
Author
|
/ok-to-merge doc only |
gbartolini
approved these changes
Jun 18, 2026
Signed-off-by: Marco Nenciarini <[email protected]>
Signed-off-by: Marco Nenciarini <[email protected]>
mnencia
force-pushed
the
dev/plugin-reload-docs
branch
from
June 18, 2026 07:36
ad18109 to
5d35199
Compare
leonardoce
approved these changes
Jun 18, 2026
cnpg-bot
pushed a commit
that referenced
this pull request
Jun 18, 2026
Follow-up to #10836. That PR made the operator reconcile clusters when a CNPG-i plugin's pods are rolled, but the CNPG-i documentation still only described how new plugins are discovered, not what happens when an existing plugin is upgraded. This adds a short note to the standalone deployment section explaining that the operator detects plugin pod rollouts through the backing EndpointSlices and promptly reconciles the affected clusters, so they reconnect to the new pods without waiting for the periodic resync. Signed-off-by: Marco Nenciarini <[email protected]> (cherry picked from commit 49fb8fa)
cnpg-bot
pushed a commit
that referenced
this pull request
Jun 18, 2026
Follow-up to #10836. That PR made the operator reconcile clusters when a CNPG-i plugin's pods are rolled, but the CNPG-i documentation still only described how new plugins are discovered, not what happens when an existing plugin is upgraded. This adds a short note to the standalone deployment section explaining that the operator detects plugin pod rollouts through the backing EndpointSlices and promptly reconciles the affected clusters, so they reconnect to the new pods without waiting for the periodic resync. Signed-off-by: Marco Nenciarini <[email protected]> (cherry picked from commit 49fb8fa)
cnpg-bot
pushed a commit
that referenced
this pull request
Jun 18, 2026
Follow-up to #10836. That PR made the operator reconcile clusters when a CNPG-i plugin's pods are rolled, but the CNPG-i documentation still only described how new plugins are discovered, not what happens when an existing plugin is upgraded. This adds a short note to the standalone deployment section explaining that the operator detects plugin pod rollouts through the backing EndpointSlices and promptly reconciles the affected clusters, so they reconnect to the new pods without waiting for the periodic resync. Signed-off-by: Marco Nenciarini <[email protected]> (cherry picked from commit 49fb8fa)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #10836. That PR made the operator reconcile clusters when a CNPG-i plugin's pods are rolled, but the CNPG-i documentation still only described how new plugins are discovered, not what happens when an existing plugin is upgraded.
This adds a short note to the standalone deployment section explaining that the operator detects plugin pod rollouts through the backing EndpointSlices and promptly reconciles the affected clusters, so they reconnect to the new pods without waiting for the periodic resync.