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.
Is this an ISSUE or FEATURE REQUEST? (choose one): Feature
What version of acs-engine?: all
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm): Kubernetes
What happened:
When you generate a template - there are some big big long strings for customData added to each VM. It's difficult to read these, and it's almost impossible to see how they'll be modified as you make changes to acs-engine.
I propose adding a new verbose flag that will output anything to a file for review before it's encoded into customData strings. That will make it easier to review changes to kubelet flags, apiserver settings and so on before running az group deploy
How to reproduce it (as minimally and precisely as possible): acs-engine generate <anything.json>
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is this a request for help?: No
Is this an ISSUE or FEATURE REQUEST? (choose one): Feature
What version of acs-engine?: all
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm): Kubernetes
What happened:
When you generate a template - there are some big big long strings for customData added to each VM. It's difficult to read these, and it's almost impossible to see how they'll be modified as you make changes to acs-engine.
I propose adding a new verbose flag that will output anything to a file for review before it's encoded into customData strings. That will make it easier to review changes to kubelet flags, apiserver settings and so on before running
az group deploy
How to reproduce it (as minimally and precisely as possible):
acs-engine generate <anything.json>
The text was updated successfully, but these errors were encountered: