Explorar el Código

Fix command line arg usage

Gennady Lipenkov hace 5 años
padre
commit
73bfdfd7f5

+ 1 - 1
dashboard/src/main/home/modals/ClusterInstructionsModal.tsx

@@ -84,7 +84,7 @@ export default class ClusterInstructionsModal extends Component<
             there are two contexts named minikube and staging, you could connect
             there are two contexts named minikube and staging, you could connect
             both of them via:
             both of them via:
             <Code>
             <Code>
-              porter connect kubeconfig --contexts minikube --contexts staging
+              porter connect kubeconfig --context minikube --context staging
             </Code>
             </Code>
           </Placeholder>
           </Placeholder>
         );
         );

+ 1 - 1
docs/GETTING_STARTED.md

@@ -99,5 +99,5 @@ porter connect kubeconfig --kubeconfig path/to/kubeconfig
 You can initialize Porter with a set of contexts by passing a context list to start. The contexts that Porter will be able to access are the same as `kubectl config get-contexts`. For example, if there are two contexts named `minikube` and `staging`, you could connect both of them via:
 You can initialize Porter with a set of contexts by passing a context list to start. The contexts that Porter will be able to access are the same as `kubectl config get-contexts`. For example, if there are two contexts named `minikube` and `staging`, you could connect both of them via:
 
 
 ```sh
 ```sh
-porter connect kubeconfig --contexts minikube --contexts staging
+porter connect kubeconfig --context minikube --context staging
 ```
 ```