[AKS Blog] Slight edits to blog post #4304
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Bridget Kromhout <[email protected]>
bridgetkromhout
commented
May 22, 2024
|
|
||
| At that time, the service was still very basic compared to what it is today. It only supported public clusters with a availability sets, no nodepools or autoscaling, no Windows containers, and a maximum of 100 nodes per cluster. It also lacked many features that are now considered essential, such as role-based access control, advanced networking, node repair, and cluster upgrades. Despite these limitations, AKS was still recognized as a huge leap forward from ACS and customer adoption was really fast. Users saw the value of having a fully managed Kubernetes service that integrated seamlessly with Azure and Microsoft tools. Plus, we quickly got to work delivering many of the key capabilities that our customers depend on today. | ||
| At that time, the service was still very basic compared to what it is today. It only supported public clusters with no availability sets, no nodepools or autoscaling, no Windows containers, and a maximum of 100 nodes per cluster. It also lacked many features that are now considered essential, such as role-based access control, advanced networking, node repair, and cluster upgrades. Despite these limitations, AKS was still recognized as a huge leap forward from ACS and customer adoption was really fast. Users saw the value of having a fully managed Kubernetes service that integrated seamlessly with Azure and Microsoft tools. Plus, we quickly got to work delivering many of the key capabilities that our customers depend on today. |
There was a problem hiding this comment.
"public clusters with a availability sets" makes no sense; my best guess is that we meant "public clusters with no availability sets", but I am not positive that is what was intended - @palma21 please confirm?
There was a problem hiding this comment.
With availability sets (instead of vmss or nodepools)
There was a problem hiding this comment.
Perhaps with only one availability set is the better phrasing
Signed-off-by: Bridget Kromhout <[email protected]>
sabbour
approved these changes
May 22, 2024
palma21
approved these changes
May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A day late, I offer some small subtle edits for this excellent blog post.