It's actually a clash with bash's command history and emacs.
I opened T245898.
> On Feb 21, 2020, at 7:14 PM, Brooke Storm wrote:
>
> I get what you mean now. This is a container launched by Kubernetes with the
> webservice wrapper on a daemon in the cluster, so I don't consider it likely
>
I get what you mean now. This is a container launched by Kubernetes
with the webservice wrapper on a daemon in the cluster, so I don't
consider it likely that passing that through to the docker daemon would
be possible. Configuring docker to work differently across the fleet is
more likely (which
Hmmm, yeah, I get the desire to keep production containers as minimal as
possible. I had asked a while ago if it was possible to get Python 3.7 on the
bastion hosts, but was told that's not feasible because of the way the distros
are packaged. So, I seem to be stuck with having to flip back an
Hello Roy,
The container environment for webservice shell is the same image as the
runtime containers for a service, so I'd rather not support ssh in the
containers because they need to be light-weight, limited and including
that would raise some interesting security issues in the cluster
otherwise
I had been planning to switch my tools over before it was forced, so I took
care of that last night - thanks, it seems to have gone smoothly. And I
love the new grafana dashboards!
One question - I seem to be getting some more timeout-related 500 server
errors. Was there a change in how that is ha
The bastion hosts don't have python3.7, and the k8s hosts don't have ssh, so
"git pull" and "git push" don't work. Which means I need to keep flipping back
and forth between the two during development. Is there some way to get ssh
working on the k8s hosts, so I can do everything in one place?
