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
{{ message }}
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
The script assumes that the script parts/k8s/cloud-init/artifacts/setup-custom-search-domains.sh contains a #EOF. But this is not the case here, so the script is not included in /opt/azure/cloud-init-files.paved on the server and the corresponding abort occurs. If i run setup-custom-search-domains.sh manually, the server are joining the realm.
Expected behavior
The script should be functional so that the nodes register themselves in the AD.
AKS Engine version
aks-engine-v0.51.1 Kubernetes version
1.17.5
Additional context
Another thing is, thet the Names of the Nodes are much to long, for the Active-Directory Computer section. There is a limit, so the nodes are shorten to k8s-master-3500 and get all the same name, is there an way to get shorter names?
The text was updated successfully, but these errors were encountered:
Describe the bug
I have the problem that I would like to use a custom DNS, so I enter the variables as desired
I get the fallowing error from the log:
This is caused by the ./provision_source.sh:wait_for_file()
The script assumes that the script parts/k8s/cloud-init/artifacts/setup-custom-search-domains.sh contains a #EOF. But this is not the case here, so the script is not included in /opt/azure/cloud-init-files.paved on the server and the corresponding abort occurs. If i run setup-custom-search-domains.sh manually, the server are joining the realm.
Steps To Reproduce
aks-engine-v0.51.1 deploy -f --azure-env AzureStackCloud --api-model kubernetes-azurestack.json --location REDACTED --resource-group RG-k8s-Test --client-id REDACTED --client-secret REDACTED --subscription-id REDACTED --output-directory RG-k8s-Test
Expected behavior
The script should be functional so that the nodes register themselves in the AD.
AKS Engine version
aks-engine-v0.51.1
Kubernetes version
1.17.5
Additional context
Another thing is, thet the Names of the Nodes are much to long, for the Active-Directory Computer section. There is a limit, so the nodes are shorten to k8s-master-3500 and get all the same name, is there an way to get shorter names?
The text was updated successfully, but these errors were encountered: