Skip to content

Rename section to ConfigMaps in Windows Containers #372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 6, 2025
Merged

Rename section to ConfigMaps in Windows Containers #372

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/container-instances/container-instances-config-map.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -514,7 +514,7 @@ Once the update has been applied to an existing container and you will see the v

/mnt/configmap/<containername>/key2 with value as “value2”
```
### ConfigMaps in Linux Windows
### ConfigMaps in Windows Containers
Once the update has been applied to an existing container and you can fetch the configmap keyvalue pairs in the windows container by making the following call, without requiring a restart. These values are not mounted anywhere for windows containers, as is the case for linux.
```
Invoke-Expression "$Env:ConfigMapURI"
Expand Down