You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/containers/overview-local-process-kubernetes.md
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,9 @@ After you establish a connection to your cluster, you can run and debug code nat
43
43
44
44
In addition, Local Process with Kubernetes provides a way to replicate environment variables and mounted files available to pods in your cluster on your development computer through the `KubernetesLocalProcessConfig.yaml` file. You can also use this file to create new environment variables and volume mounts.
45
45
46
+
> [!NOTE]
47
+
> For the duration of the connection to the cluster (plus an additional 15 minutes), Local Process with Kubernetes runs a process called *EndpointManager* with admin permissions on your local computer.
48
+
46
49
## Additional configuration with KubernetesLocalProcessConfig.yaml
47
50
48
51
The `KubernetesLocalProcessConfig.yaml` file allows you to replicate environment variables and mounted files available to your pods in your cluster. For more information on the additional configuration options, see [Configure Local Process with Kubernetes][using-config-yaml].
@@ -88,7 +91,7 @@ When you disconnect from your cluster, by default, Local Process with Kubernetes
88
91
89
92
## Diagnostics and logging
90
93
91
-
When using Local Process with Kubernetes to connect to your cluster, diagnostic logs from your cluster are logged to your development computer's [temporary directory][azds-tmp-dir].
94
+
When using Local Process with Kubernetes to connect to your cluster, diagnostic logs from your cluster are logged to your development computer's *TEMP* directory in the *Local Process with Kubernetes* folder.
Copy file name to clipboardExpand all lines: docs/containers/tutorial-kubernetes-tools.md
+11-1Lines changed: 11 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -119,7 +119,7 @@ The added files are:
119
119
120
120
-*azds.yaml*. This contains settings for Azure Dev Spaces, which provides a rapid, iterative debugging experience in Azure Kubernetes Service. For more information, see [the Azure Dev Spaces documentation](/azure/dev-spaces/azure-dev-spaces).
121
121
122
-
:::moniker range="vs-2017"
122
+
:::moniker range="vs-2017"
123
123
124
124
## Publish to Azure Kubernetes Service (AKS)
125
125
@@ -163,6 +163,16 @@ To do this, you first need to double-check that you've installed everything as d
163
163
164
164
Congratulations! You can now use the full power of Visual Studio for all your Kubernetes app development.
165
165
166
+
## Remove Kubernetes support
167
+
168
+
1. In **Solution Explorer**, under **Properties**, open *launchSettings.json*.
169
+
170
+
1. Delete the section **Container in Kubernetes**.
171
+
172
+
1. If you're switching back to Docker compose, select that project in **Solution Explorer**, right-click and choose **Set as Startup Project**.
173
+
174
+
1. (Optional) You can also delete other artifacts listed as mentioned earlier in the article, such as the **charts** folder and *azds.yaml*.
175
+
166
176
## Next steps
167
177
168
178
Learn more about Kubernetes development on Azure by reading the [AKS documentation](/azure/aks).
0 commit comments