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
Hm, I'll have to check the keyfile arg handling in jupyter-client, I don't think I've seen it used before. Are you not using a normal connection file with the key as a field?
we deployed a cluster in GKE. All field excepts key we just put in config Map. For key, we have to put it in secret to keep it safe. ipcontroll and ipengine can start with --keyfile arg. Only Client does not honor it.
Is there a reason to split the connection file into config and secret, rather than putting the whole connection file in a secret because it contains auth info? The connection file isn't useful without the key, so it doesn't seem useful to separate them since they must always be recombined to be used.
Yes, all connection files can be put into secret. However, we split it with some reasons:
We use dedicated manual process to deploy secret, so we do not need put passwords into circleCI. Keep secret simple then we can reduce times of redeployment.
The host information in connection file can not get in secret deployment because it derives dynamically.
Activity
minrk commentedon Jun 9, 2017
Hm, I'll have to check the keyfile arg handling in jupyter-client, I don't think I've seen it used before. Are you not using a normal connection file with the key as a field?
ktong commentedon Jun 9, 2017
we deployed a cluster in GKE. All field excepts key we just put in config Map. For key, we have to put it in secret to keep it safe. ipcontroll and ipengine can start with --keyfile arg. Only Client does not honor it.
minrk commentedon Jun 16, 2017
Is there a reason to split the connection file into config and secret, rather than putting the whole connection file in a secret because it contains auth info? The connection file isn't useful without the key, so it doesn't seem useful to separate them since they must always be recombined to be used.
ktong commentedon Jun 16, 2017
Yes, all connection files can be put into secret. However, we split it with some reasons:
We use dedicated manual process to deploy secret, so we do not need put passwords into circleCI. Keep secret simple then we can reduce times of redeployment.
The host information in connection file can not get in secret deployment because it derives dynamically.