add machine ssh key to staging mgmt

[anish-mudaraddi]

for easier debugging in the future

[gmatthews20]

Is this something we want o do if we don't encourage users to do he same? Where is the private key stored?

[anish-mudaraddi]

private key/passphrase is in keeper

@DavidFair - I think we should encourage users to add SSH keys as a "last resort" - especially for the kubeconfig credentials expiring issue

[DavidFair]

Yeah I guess unless we're actively trying to solve a problem now I'd rather not add it, then point people to either LOKI or add the key as/when we need it?

For dev I don't care if it runs with a key 24/7, but staging should be close to prod to basically pre-test something before it goes to prod. If someone can SSH in we can't reliably say prod and staging are the same from that point onwards as easily.

Also (more controversially) if something is failing then we should diagnose it in dev and either drop it from staging (it's not ready to be staged for a promotion) or accept it as a known issue to revisit