-
Notifications
You must be signed in to change notification settings - Fork 134
feat: add init container to web deployment for database migrations #274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
chaholl
wants to merge
4
commits into
langfuse:main
Choose a base branch
from
chaholl:feature/web-init-container
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
ee806f0
feat: add init container to web deployment for database migrations
chaholl 7c73e43
fix: use args instead of command for init container
chaholl 23fd646
fix: increase liveness probe initial delay to 60s
chaholl 552cdf1
docs: update chart documentation for liveness probe changes
chaholl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,83 @@ | ||
| suite: test init container functionality | ||
| templates: | ||
| - web/deployment.yaml | ||
| tests: | ||
| - it: should have init container with correct configuration | ||
| values: | ||
| - ../values.lint.yaml | ||
| asserts: | ||
| # Test that web deployment has init containers | ||
| - hasDocuments: | ||
| count: 1 | ||
| template: web/deployment.yaml | ||
| - isKind: | ||
| of: Deployment | ||
| template: web/deployment.yaml | ||
|
|
||
| # Test that init container exists | ||
| - exists: | ||
| path: spec.template.spec.initContainers | ||
| template: web/deployment.yaml | ||
|
|
||
| # Test init container count (should have at least 1) | ||
| - isNotEmpty: | ||
| path: spec.template.spec.initContainers | ||
| template: web/deployment.yaml | ||
|
|
||
| # Test init container name | ||
| - equal: | ||
| path: spec.template.spec.initContainers[0].name | ||
| value: langfuse-web-init | ||
| template: web/deployment.yaml | ||
|
|
||
| # Test init container uses same image as main container | ||
| - equal: | ||
| path: spec.template.spec.initContainers[0].image | ||
| value: "langfuse/langfuse:3.129.0" | ||
| template: web/deployment.yaml | ||
|
|
||
| # Test init container has args that runs initialization and exits | ||
| - equal: | ||
| path: spec.template.spec.initContainers[0].args | ||
| value: ["echo", "Init completed successfully"] | ||
| template: web/deployment.yaml | ||
|
|
||
| # Test init container has environment variables | ||
| - exists: | ||
| path: spec.template.spec.initContainers[0].env | ||
| template: web/deployment.yaml | ||
|
|
||
| # Test that NODE_ENV is set in init container | ||
| - contains: | ||
| path: spec.template.spec.initContainers[0].env | ||
| content: | ||
| name: NODE_ENV | ||
| value: "production" | ||
| template: web/deployment.yaml | ||
|
|
||
| - it: should preserve existing extraInitContainers functionality | ||
| values: | ||
| - ../values.lint.yaml | ||
| set: | ||
| langfuse.extraInitContainers: | ||
| - name: custom-init | ||
| image: busybox | ||
| command: ["echo", "custom init"] | ||
| asserts: | ||
| # Should have 2 init containers (our default + custom) | ||
| - lengthEqual: | ||
| path: spec.template.spec.initContainers | ||
| count: 2 | ||
| template: web/deployment.yaml | ||
|
|
||
| # First should be our web-init container | ||
| - equal: | ||
| path: spec.template.spec.initContainers[0].name | ||
| value: langfuse-web-init | ||
| template: web/deployment.yaml | ||
|
|
||
| # Second should be the custom init container | ||
| - equal: | ||
| path: spec.template.spec.initContainers[1].name | ||
| value: custom-init | ||
| template: web/deployment.yaml |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this necessary if an init container is in place? My understanding is that the health check would only start once the main container in the pod becomes active.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's what I thought as well! :)
But unfortunately the main container is still talking longer than 20s to spin up and become ready to serve the health api. Maybe because it's still running the entrypoint script