You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey guys, so I'm using the nest-typed-config library and one trouble I'm experiencing is loading .env.yaml files to a K8s pods. I've looked around and seen no way to load a .env.yaml file to a K8s pod, except defining the environment variables in the spec.
What would be some strategies for loading environment variables in a K8s pod and ensure that the TypedConfigModule is able to detect this environment variables and process the type definitions? Would ConfigMaps or Secrets be viable solution?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey guys, so I'm using the nest-typed-config library and one trouble I'm experiencing is loading .env.yaml files to a K8s pods. I've looked around and seen no way to load a .env.yaml file to a K8s pod, except defining the environment variables in the spec.
What would be some strategies for loading environment variables in a K8s pod and ensure that the TypedConfigModule is able to detect this environment variables and process the type definitions? Would ConfigMaps or Secrets be viable solution?
Beta Was this translation helpful? Give feedback.
All reactions