support bringing own AKS cluster to deploy#24
Open
vivishno wants to merge 35 commits intoAzure:masterfrom
Open
support bringing own AKS cluster to deploy#24vivishno wants to merge 35 commits intoAzure:masterfrom
vivishno wants to merge 35 commits intoAzure:masterfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
issue linked to https://github.com/github/ms-ecosystem/issues/85
Added optional parameter resource group to action.(Only required when compute type is 'akscluster')
If the cluster provided is not found inside ML workspace it will look for it inside resource group.
If found will attach the given cluster to ML workspace else will create a new compute cluster as the action already does currently.