This PR primarily addresses the following warning that's started appearing when intercepting:
Warning: You are executing the "telepresence intercept [flags] <intercept_base_name> [-- <command with arguments...>]" command without a preceding "telepresence connect", causing an implicit connect to take place. The implicit connect behavior is deprecated and will be removed in a future release.
The warning can also appear for telepresence leave when closing an intercept that's been open for a long time (e.g. accidentally left open overnight).
I've also added a bunch of optional flags that seem to improve the experience when switching namespaces and re-intercepting. Previously, if you forget to telepresence quit -s after switching namespaces, the intercept would appear to work, but would have applied to the previous namespace. Now, when intercepting after a namespace switch, you'll get an error instead:
A deprecation warning will be printed if a command other than telepresence connect causes an implicit connect to happen. Implicit connects will be removed in a future release.
The behavior changed so that a connected Telepresence client is bound to a namespace. The namespace can then not be changed unless the client disconnects and reconnects. A connection is also given a name. The default name is composed from <kube context name>-<namespace> but can be given explicitly when connecting using --name. The connection can optionally be identified using the option --use <name match> (only needed when docker is used and more than one connection is active).
This PR primarily addresses the following warning that's started appearing when intercepting:
The warning can also appear for
telepresence leavewhen closing an intercept that's been open for a long time (e.g. accidentally left open overnight).I've also added a bunch of optional flags that seem to improve the experience when switching namespaces and re-intercepting. Previously, if you forget to
telepresence quit -safter switching namespaces, the intercept would appear to work, but would have applied to the previous namespace. Now, when intercepting after a namespace switch, you'll get an error instead:Which still sucks, but at least it's a decent reminder of what you need to do.
Relevant release notes:
2.16.0telepresence connectcauses an implicit connect to happen. Implicit connects will be removed in a future release.<kube context name>-<namespace>but can be given explicitly when connecting using--name. The connection can optionally be identified using the option--use <name match>(only needed when docker is used and more than one connection is active).