♻️ traefik: configuration via environment variables ⚠️ #8572
Conversation
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
It makes traefik configuration adjustments easier. One can do that by changing ENV in portainer. Use case: enable access and debug logs on prod to investigate some issue Related issues * ITISFoundation/osparc-ops-environments#1253 Related PR/s * ... corresponding changes in OPS must be added
YuryHrytsuk
added
the
a:infra+ops
YuryHrytsuk
changed the title
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #8572 +/- ##
=======================================
Coverage 87.55% 87.56%
=======================================
Files 2012 2012
Lines 79025 79025
Branches 1368 1368
=======================================
+ Hits 69191 69196 +5
+ Misses 9428 9423 -5
Partials 406 406
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
YuryHrytsuk
added a commit
to YuryHrytsuk/osparc-ops-environments
that referenced
this pull request
Nov 11, 2025
Configure simcore traefik via env (instead of commands). This makes configuration adjustments easier (it can be done on-the-fly via portainer). Use case: enable access and debug logs on PROD to investigate issues Related PR/s * ITISFoundation/osparc-simcore#8572
1 task
Contributor
🧪 CI InsightsHere's what we observed from your CI run for aa36488. ✅ Passed Jobs With Interesting Signals
|
Converting commands to env variables have implication. Names that have underscore inside cannot be converted to env variables without a change (underscore has special meaning). See more traefik/traefik#5427 Fix the problem by removing underscore. Traefik error log ``` failed to decode configuration from environment variables: field not found, node: api ```
|
YuryHrytsuk
added a commit
to ITISFoundation/osparc-ops-environments
that referenced
this pull request
Nov 11, 2025
* simcore traefik: configuration via env Configure simcore traefik via env (instead of commands). This makes configuration adjustments easier (it can be done on-the-fly via portainer). Use case: enable access and debug logs on PROD to investigate issues Related PR/s * ITISFoundation/osparc-simcore#8572 * Update simcore api entrypoint name Accroding to ITISFoundation/osparc-simcore@ff12cac
15 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What do these changes do?
Configure traefik via environment variables. This lets developers updating traefik configuration by changing ENV in portainer. Previous approach required redeploying simcore stack (not convenient). Use case: enable access and debug logs on prod to investigate some issue.
FYI @sanderegg @matusdrobuliak66 @GitHK to trace ITISFoundation/osparc-ops-environments#1253 we need to enable logs and check for errors. This is the "solution" as of now
Related issue/s
wb-authserver is down / not reachable osparc-ops-environments#1253 --> we need to enable traefik debug logs to trace this issue. With changes from this PR it will be easyRelated PR/s
How to test
deploy locally and ensure all works normally
Dev-ops⚠️
Checks