Skip to content
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.

feat: EncryptionAtHost support(cherry-pick to branch aks-release-v0.47.0-1) #3064

Merged

Conversation

andyzhangx
Copy link
Contributor

Reason for Change:

Ported from PR: #3041

This PR is actually a place holder, it's mainly for AKS to support EncryptionAtHost(Enable Encryption at Host support for VM/VMSS) (JEDI requirement) which is going to be in private preview late this month.

EncryptionAtHost functionality actually does not work by this PR since it depends on

  • go sdk ready and upgrade to supported go sdk version
  • EncryptionAtHost feature on public regions ready
  • subs whitelist

Will make it work when the above 3 requirements are fullfilled.

Issue Fixed:

Requirements:

Notes:

/assign @xuto2
cc @jluk

@andyzhangx andyzhangx changed the title feat: EncryptionAtHost support(only for branch aks-release-v0.47.0-1) feat: EncryptionAtHost support(cherry-pick to branch aks-release-v0.47.0-1) Apr 13, 2020
pkg/api/types.go Show resolved Hide resolved
@mboersma mboersma added the aks label Apr 13, 2020
@andyzhangx

This comment has been minimized.

@andyzhangx andyzhangx closed this Apr 14, 2020
@andyzhangx
Copy link
Contributor Author

andyzhangx commented Apr 14, 2020

I was wrong, we still need this field in aks-engine agent pool


Below are the work flow:

  1. az aks create --aks-custom-headers EncryptionAtHost=true
  2. aks rp do the validation and check whether current vm size in agent pool supports EncryptionAtHost, if yes, set agentPool.EncryptionAtHost=true
  3. set EncryptionAtHost flag in ARM template according to agentPool.EncryptionAtHost value

@andyzhangx andyzhangx reopened this Apr 14, 2020
@xuto2 xuto2 merged commit 2740df9 into Azure:aks-release-v0.47.0-1 Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants