This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 522
Using special characters in client_secret will break windows node pool creation #926
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. |
PatrickLang
pushed a commit
to PatrickLang/aks-engine
that referenced
this issue
Apr 1, 2019
…tom script block
PatrickLang
pushed a commit
to PatrickLang/aks-engine
that referenced
this issue
Apr 1, 2019
4 tasks
acs-bot
pushed a commit
that referenced
this issue
Apr 3, 2019
mboersma
pushed a commit
that referenced
this issue
Apr 4, 2019
PatrickLang
pushed a commit
to PatrickLang/aks-engine
that referenced
this issue
Apr 30, 2019
4 tasks
jackfrancis
pushed a commit
that referenced
this issue
Apr 30, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a request for help?: No.
Is this an ISSUE or FEATURE REQUEST? (choose one): ISSUE
What version of aks-engine?: 1.12.6
Kubernetes version: 1.12.6
What happened: When the client secret includes special chars such as "(" and ")", the node provision will fail.
What you expected to happen: Node provision to succeed.
How to reproduce it (as minimally and precisely as possible): Provision a windows agent pool with specials chars ")" in the service principal client secret.
Anything else we need to know:
The text was updated successfully, but these errors were encountered: