Commit ed7aef1
committed
fix: Always mount ConfigMap and add --config flag
When alphaConfig.enabled=true and forceLegacyConfig=false, the
deployment was not mounting the ConfigMap or adding the --config flag
because the condition checked for existingConfig OR configFile.
Since configFile defaults to empty string, the condition was false
and oauth2-proxy failed with 'missing setting for email validation'.
Fixed by removing the conditions entirely:
- ConfigMap volume is always created (using existingConfig if specified)
- ConfigMap is always mounted
- --config flag is always added
This ensures email_domains is always provided to oauth2-proxy,
whether using the generated ConfigMap or an existingConfig.
This is NOT a breaking change - it fixes a bug where the app didn't
work with default values when using alphaConfig.
Signed-off-by: pierluigilenoci <pierluigi.lenoci@gmail.com>
Signed-off-by: Pierluigi Lenoci <pierluigi.lenoci@gmail.com>1 parent 79831db commit ed7aef1
1 file changed
+0
-6
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
145 | 145 | | |
146 | 146 | | |
147 | 147 | | |
148 | | - | |
149 | 148 | | |
150 | | - | |
151 | 149 | | |
152 | 150 | | |
153 | 151 | | |
| |||
298 | 296 | | |
299 | 297 | | |
300 | 298 | | |
301 | | - | |
302 | 299 | | |
303 | 300 | | |
304 | 301 | | |
305 | | - | |
306 | 302 | | |
307 | 303 | | |
308 | 304 | | |
| |||
366 | 362 | | |
367 | 363 | | |
368 | 364 | | |
369 | | - | |
370 | 365 | | |
371 | 366 | | |
372 | 367 | | |
373 | 368 | | |
374 | | - | |
375 | 369 | | |
376 | 370 | | |
377 | 371 | | |
| |||
0 commit comments