home/kt-connect
2
0
Fork 0
mirror of https://github.com/wahyd4/kt-connect.git synced 2026-08-09 05:16:02 +10:00
Code Issues Packages Projects Releases Wiki Activity

exchange and mesh command need sudo to avoid "Load key ~/.kt_id_rsa: Permission denied"

Browse Source
This commit is contained in:
金戟
2020-01-05 11:43:51 +08:00
parent bb763cb248
commit a0e0e12ec6
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -2
View File
@@ -82,7 +82,7 @@ docker run -itd -p 8080:8080 tomcat:8
```
```
$ ktctl exchange tomcat --expose 8080
$ sudo ktctl exchange tomcat --expose 8080
2019/06/19 11:19:10 * tomcat (0 replicas)
2019/06/19 11:19:10 Scale deployment tomcat to zero
2019/06/19 11:19:10 Deploying proxy deployment tomcat-kt-oxpjf in namespace default
@@ -114,7 +114,7 @@ $ curl http://tomcat:8080 | grep '<h1>'
The most different from mesh and exchange is exchange will scale the origin workload replicas to zero. And messh will keep it and create a pod instance with random version, after this user can modifi the Istio route rule let the specific request redirect to local, and the environment is working as normal:
```
$ ktctl mesh tomcat --expose 8080
$ sudo ktctl mesh tomcat --expose 8080
2019/06/19 22:10:23 'KT Connect' not runing, you can only access local app from cluster
2019/06/19 22:10:24 Deploying proxy deployment tomcat-kt-ybocr in namespace default
2019/06/19 22:10:24 Pod status is Pending