-
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
Add container orchestrator environment variable #43
Conversation
ea97f10
to
7c8691b
Compare
@@ -9,6 +9,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), | |||
### Added | |||
|
|||
- Automatic model management on AWS now supports model removal. See the `engine.modelManager.models.remove` section in the `values.yaml` file for details. | |||
- Container orchestrator environment variable added to improve support. |
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.
Worth calling out the 3 supported values, since it's a small finite set and we could potentially add/change it in the future?
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.
It's not necessarily intended to be change or configured - I don't think it needs to be called out.
Also, the cardinality will increase, as the Helm value will change for each version (but the prefix will stay the same).
@@ -14,6 +14,7 @@ services: | |||
# Make sure you `export` your self-hosted API key secret in your local environment | |||
environment: | |||
DEEPGRAM_API_KEY: "${DEEPGRAM_API_KEY}" | |||
DEEPGRAM_DEPLOYMENT_ORCHESTRATOR: "docker-compose" |
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.
Any way to make this a static variable or enum of some type, or is hard-coding the same string multiple times the best option on these?
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.
I wasn't previously aware, which is why there is duplication in other places, but your question prompted me to go looking, and I found Docker Compose extension fields. Let me see if they're also compatible with Podman.
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.
The Compose protocol is fairly limited. I was able to reduce the duplication of the API key and the common orchestrator variable. I tried to do the same for the release tag on each image, but I can edit only a subsection of a field.
It's also not supported by podman-compose
right now, so can only use this for the Docker Compose templates.
Proposed changes
Add an environment variable to container launch templates to enable more detailed support for self-hosted deployments.
Types of changes
Checklist