You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to add new blueprint configurations to Authentik after initial deployment, but running into limitations with the Helm chart approach. Current situation:
Using official Authentik Helm chart
Blueprints work when pre-configured in values.yaml under blueprints.configMaps
New ConfigMaps created after deployment aren't automatically mounted/discovered
What I've tried:
ak apply_blueprint command fails with "Invalid blueprint path" for files outside /blueprints directories
Direct file placement in /blueprints/ fails due to read-only filesystem
Only /blueprints/mounted/ contains ConfigMap volumes, but these must be pre-configured in Helm
Question: What's the recommended way to add new blueprint configurations dynamically without updating Helm values and redeploying?
Goal: Fully automated blueprint deployment via CI/CD without requiring Helm chart updates.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to add new blueprint configurations to Authentik after initial deployment, but running into limitations with the Helm chart approach.
Current situation:
What I've tried:
Question: What's the recommended way to add new blueprint configurations dynamically without updating Helm values and redeploying?
Goal: Fully automated blueprint deployment via CI/CD without requiring Helm chart updates.
Beta Was this translation helpful? Give feedback.
All reactions