Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
K
k3s
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Jacklull
  • k3s
  • Repository

Switch branch/tag
  • k3s
  • pkg
  • kubelet
  • kuberuntime
  • kuberuntime_container_windows.go
Find file
BlameHistoryPermalink
  • Jean Rouge's avatar
    Kubelet changes for Windows GMSA support · 3f567588
    Jean Rouge authored Feb 04, 2019
    This patch comprises the kubelet changes outlined in the GMSA KEP
    (https://github.com/kubernetes/enhancements/blob/master/keps/sig-windows/20181221-windows-group-managed-service-accounts-for-container-identity.md)
    to add GMSA support to Windows workloads.
    
    More precisely, it includes the logic proposed in the KEP to resolve
    which GMSA spec should be applied to which containers, and changes
    `dockershim` to copy the relevant GMSA credential specs to Windows
    registry values prior to creating the container, passing them down
    to docker itself, and finally removing the values from the registry
    afterwards; both these changes need to be activated with the `WindowsGMSA`
    feature gate.
    
    Includes unit tests.
    Signed-off-by: 's avatarJean Rouge <rougej+github@gmail.com>
    3f567588
kuberuntime_container_windows.go 5.79 KB
EditWeb IDE

Replace kuberuntime_container_windows.go

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.