-
Notifications
You must be signed in to change notification settings - Fork 55
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
Misc aks followup #507
Misc aks followup #507
Conversation
jsaun
commented
Oct 10, 2022
•
edited
Loading
edited
- Remove blob storage mounts for Tes.
- Fixes to arguments validation, don't validate helm install if manualhelminstall flag is used and default provisionpostgresql to true if AKS is used.
- Remove settings-system & settings-user, use aksValues.yaml to store all settings.
|
||
public async Task UpgradeValuesYaml(IStorageAccount storageAccount, Dictionary<string, string> settings) | ||
{ | ||
var values = KubernetesYaml.Deserialize<HelmValues>(await Deployer.DownloadTextFromStorageAccountAsync(storageAccount, Deployer.ConfigurationContainerName, "aksValues.yaml", cts)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is called "aksValues.yml" but below is "values.yaml" - is there a reason for them to differ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the actual helm deployment, it must be named exactly values.yaml. I added the AKS prefix while in the storage account since you mentioned in the meeting last week, and it does add some specificity to the filename in that context.