-
Notifications
You must be signed in to change notification settings - Fork 6
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
Automatically init scratch area and remove startup script #520
Conversation
This will need testing on k8s |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #520 +/- ##
==========================================
+ Coverage 91.32% 91.51% +0.18%
==========================================
Files 41 42 +1
Lines 1880 1933 +53
==========================================
+ Hits 1717 1769 +52
- Misses 163 164 +1 ☔ View full report in Codecov by Sentry. |
{{- if .Values.scratch.hostPath }} | ||
- name: init-venv | ||
image: busybox:1.28 | ||
command: ['sh', '-c', "cp -r /venv /emptyDir/venv"] |
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.
My current concern with this is the added startup time
351c8bc
to
376561e
Compare
Still to do:
|
1f19820
to
18e5cda
Compare
Co-authored-by: Joe Shannon <[email protected]>
Co-authored-by: Joe Shannon <[email protected]>
b2b2f94
to
3783354
Compare
Fixes #510 and #399
Write python code to do the job of
container-startup.sh
and add code to clone the required repos. Replacecontainer-startup.sh
with this code. Stop blueapi from initializing scratch automatically on container startup, replace this job with an initContainer. Copy the blueapi venv to an emptyDir so the initContainers can manipulate it.