I'm using kubernetes secret as my environment variable (http://kubernetes.io/docs/user-guide/secrets/#using-secrets-as-environment-variables).

I've check whether env vars set correctly by

kubectl exec -it my_pod bash

1.

echo $RAILS_ENV #=> staging

2.

bin/rails c;
puts ENV['RAILS_ENV'] #=> staging

It works fine for my rails application and bash command, but doesn't work when executing cron process.

I've read some post to understand cron process (e.g. https://unix.stackexchange.com/questions/27289/how-can-i-run-a-cron-command-with-existing-environmental-variables) and know that I should source .profile or .bashrc before executing cron command like.

$ crontab -l

* * * * * . $HOME/.profile; /bin/bash -l -c 'echo rails_env=$RAILS_ENV >> /tmp/cron_test.log'

* * * * * . $HOME/.bashrc; /bin/bash -l -c 'echo rails_env=$RAILS_ENV >> /tmp/cron_test.log'

but both doesn't work for me ˊˋ

result

rails_env=

Any help will be appreciated!

\===

[update: add kubernetes yaml config]

Both environment variables assign by kubernetes config and kubernetes secret can read in bash and rails application, but doesn't work in cron process.

deployment.yaml

spec:
  containers:
  - name: my_rails
  ...
    command:
    - bash
    args:
    - /tmp/run_cron.sh
  ...
    env:
      - name: RAILS_ENV
        value: staging
      - name: MYSQL_PASSWORD
        valueFrom:
          secretKeyRef:
            name: rails-secret
            key: MYSQL_PASSWORD

secret.yaml

apiVersion: v1
kind: Secret
metadata:
  name: rails-secret
type: Opaque
data:
  MYSQL_PASSWORD: ENCODED_PASSWORD