Commit 3e24482
authored
fix: create separate config client to resolve APIServer TLS update conflicts (#3753)
Problem:
The olm-operator fails to receive subsequent APIServer TLS configuration
updates after the initial sync. This is because two SharedInformerFactory
instances were being created from the same client, causing watch conflicts:
1. APIServer TLS factory (created in SetupAPIServerTLSConfig)
2. Proxy factory (created inside the OLM operator)
Both factories watch config.openshift.io resources but don't share watch
state, leading to one factory not receiving all update events.
Solution:
Create a separate configclientset.Interface instance for the operator's
proxy syncer. This ensures each SharedInformerFactory has its own client,
preventing watch conflicts.1 parent 73a2205 commit 3e24482
1 file changed
Lines changed: 8 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
133 | 133 | | |
134 | 134 | | |
135 | 135 | | |
136 | | - | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
137 | 142 | | |
138 | | - | |
| 143 | + | |
139 | 144 | | |
140 | 145 | | |
141 | 146 | | |
| |||
189 | 194 | | |
190 | 195 | | |
191 | 196 | | |
192 | | - | |
| 197 | + | |
193 | 198 | | |
194 | 199 | | |
195 | 200 | | |
| |||
0 commit comments