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.

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

ACS-engine private cluster jumpbox fails to install #2474

stefanstranger opened this Issue Mar 15, 2018 · 2 comments


None yet
2 participants

stefanstranger commented Mar 15, 2018

Request for help


What version of acs-engine?:
Version: v0.14.0

I'm trying to deploy an ACS with Kubernetes private Cluster but when I configure to also deploy a jumpbox the ARM Template Test Deployment fails with errors around missing variables:

  • vnetID
  • vmSizesMap

I've the following Cluster Definition regarding internal ip addresses and jumpbox configuration:

"kubernetesConfig": {
"privateCluster": {
"enabled": true,
"jumpboxProfile": {
"name": "my-jb",
"vmSize": "Standard_D4s_v3",
"osDiskSizeGB": 30,
"storageProfile": "ManagedDisks",
"username": "azureuser",
"publicKey": "ssh-rsa xxx"
"clusterSubnet": "",
"dnsServiceIP": "",
"serviceCidr": ""

After the creation of the ARM Templates the Azure Test deployment fails because of missing variables in the ARM Templates. See above.

I'm able to deploy the internal only ACS with Kubernetes cluster when I remove the jumpbox settings.

My Azure Environment consists of two Resource Groups:

  1. Resource Group with:
    • Domain Controller and DNS
      -Virtual Network
  2. Resource Group with:
    • Kubernetes Cluster nodes etc.

The Kubernetes Cluster nodes are using the VNet from Resource Group 1.

I'm able to deploy and connect to the Kubernetes Cluster when I deploy the cluster without the jumpbox configuration.

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes 1.9.0

What happened:
Deployed failed when trying to include jumpbox vm for ACS with Kubernetes internal deployment.

What you expected to happen:

  • Deployment of ACS with private Kubernetes cluster including the jumpbox VM.

How to reproduce it (as minimally and precisely as possible):

  • Create 2 Resource Groups in Azure
  • Create a VNet in one Resource Group
  • Create a Cluster Definition file for private clusterin including jumpbox configuration
  • Run ACS Engine
  • Verify ARM Templates for missing variables.

This comment has been minimized.


CecileRobertMichon commented Mar 15, 2018

@stefanstranger thank you for reporting! That is indeed a bug in the implementation which makes the jumpbox incompatible with a custom vnet. I will have a PR to fix it soon, I'll report back here when it's out.


This comment has been minimized.


CecileRobertMichon commented Mar 16, 2018

The fix was just released in v0.14.1, please let me know if you run into any other issues!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment