Application Dependencies
Use the dependency block to have the platform inject database credentials, cloud IAM roles and secrets into your application at deploy time.
Your application needs a database password, a cloud IAM permission, or an API
key, and you do not want any of those values sitting in your repository or in
your deployment configuration. The dependency block in your application
Component tells the platform to fetch them at deploy time and hand them to the
pod as environment variables or mounted secrets.
The block is available on the generic and language-specific application
Component types. Four engines are available. Each has its own page with the
full field reference.
| Engine | What it does |
|---|---|
db | Injects database connection details (user, password, host) as environment variables |
iam | Binds cloud IAM roles to your application's Kubernetes service account |
ssm | Pulls secrets from your cloud provider's Parameter Store or Secrets Manager |
onepassword | Maps 1Password items into Kubernetes secrets |
There is also a kafka dependency for injecting Kafka credentials — see
Kafka Access, ACLs and Topics.
For copy-and-paste starting points, see
Dependency Configuration Examples.
Related articles
Updated about 1 month ago