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
Currently all clusters will be deployed in development mode, which is insecure as it will use public secret stored in each service's git repo.
There should be a global value to specify whether to deploy the new cluster in development or production mode.
When in production mode, new JWT secret and public keys should be generated and stored as k8s secrets and shared to each relevant pod (which I think are api/staff, maybe core? someone from Product team will be able to confirm which services needs which env vars when in PRODUCTION mode)
In production mode there should be 0 "default" passwords, e.g. initial backoffice password should be randomly generated.
The text was updated successfully, but these errors were encountered:
Currently all clusters will be deployed in development mode, which is insecure as it will use public secret stored in each service's git repo.
There should be a global
value
to specify whether to deploy the new cluster in development or production mode.When in production mode, new JWT secret and public keys should be generated and stored as k8s secrets and shared to each relevant pod (which I think are api/staff, maybe core? someone from Product team will be able to confirm which services needs which env vars when in PRODUCTION mode)
In production mode there should be 0 "default" passwords, e.g. initial backoffice password should be randomly generated.
The text was updated successfully, but these errors were encountered: