When no terminal configuration is provided an error is shown. #390
Description
What happened?
When no configuration section
devSpace:
terminal:
service: example
namespace: default`
Is provided,
It waits for pods to become available and then times out with the message:
[FATAL] Cannot find running pod: Waiting for pod with selector release=devspace-default in namespace default timed out
Because when you don't specify a terminal configuration it uses a default which may not apply to your project.
What did you expect to happen instead?
No error to be displayed and no terminal to be started.
In our case because one of our devspace configurations contains a number of applications and supporting services there is no logical default terminal.
Ideally we should be able to say e.g.
devSpace:
terminal:
enabled: false`
So that no terminal is started.
How can we reproduce the bug? (as minimally and precisely as possible)
Omit the terminal configuration from config.yaml in a configuration that does NOT contain a container/service with selector 'release=devspace-default'
Local Environment:
- Operating System: linux
- Deployment method: kubectl apply
Kubernetes Cluster:
- Cloud Provider: Local single node Microk8s cluster
- Kubernetes Version: 1.12.2
Anything else we need to know?
/kind bug