Skip to content

Commit 49fb8fa

Browse files
authored
docs: document automatic plugin reload on pod rollout (#10935)
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]>
1 parent afdce89 commit 49fb8fa

2 files changed

Lines changed: 8 additions & 0 deletions

File tree

‎.wordlist-en-custom.txt‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -168,6 +168,8 @@ EmbeddedObjectMetadata
168168
EnablePDB
169169
Endevir
170170
EndpointCA
171+
EndpointSlice
172+
EndpointSlices
171173
EnsureOption
172174
EnterpriseDB
173175
Enum

‎docs/src/cnpg_i.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,12 @@ TCP gRPC endpoint behind a Service, with **mTLS** for secure communication.
9494
Standalone plugins are discovered dynamically by watching for Services with the
9595
required labels and annotations — no operator restart is needed.
9696
97+
When a standalone plugin's pods are rolled (for example, after upgrading its
98+
image), the operator detects the change through the EndpointSlices backing the
99+
plugin Service and reconciles every cluster using that plugin, so they start
100+
interacting with the new pods promptly instead of waiting for the periodic
101+
resync.
102+
97103
Example Deployment:
98104
99105
```yaml

0 commit comments

Comments
 (0)