[Feature] API Awareness of `sshAccess` setting During Node Rotation for OS Image Updates
- Dominant language
- TypeScript
- Stars
- 2.1k
- Forks
- 395
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 13
Description
**Is your feature request related to a problem? Please describe.**
We're seeing an issue where we originally configured an AKS cluster without ssh access, and are now finding it enabled. We're being told that we need to file a feature request to have the Node OS Image update processes account for the new feature that allows you to retroactively disable ssh access on AKS nodes (ssh was configured disabled by not providing a local user name nor ssh key when building clusters, and now it's enabled without us making changes to have caused it to be enabled.
We can disable the ssh access on the nodes, but it should not have been enabled in the first place, and it keeps getting re-enabled when node os image updates take place and the nodes are rotated out.
**Describe the solution you'd like**
The node pool provisioning and/or os image update process(es)/APIs/clients needs to be made aware of the new ssh access setting on node pools and properly set it when rotating nodes for the image update.
**Describe alternatives you've considered**
There are none. We have to manually disable it every time node image updates are applied. This causes additional unnecessary downtime for the nodes because the ssh disablement process proceeds to rotate the nodes again to disable ssh access.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Assessment
This issue has not been assessed yet.