Skip to content

feat(azure): Allow specifying the resource group#218

Draft
jaitaiwan wants to merge 1 commit into
masterfrom
jaitaiwan/azure-resource-group
Draft

feat(azure): Allow specifying the resource group#218
jaitaiwan wants to merge 1 commit into
masterfrom
jaitaiwan/azure-resource-group

Conversation

@jaitaiwan
Copy link
Copy Markdown

Typically, when deploying resources in Azure, the user is expected to provide a name of a resource group that is either in existence or will be created by the command.

E.g. for AKS:

az aks create \
  --resource-group $MY_RESOURCE_GROUP_NAME \
  --name $MY_AKS_CLUSTER_NAME \
  --node-count 1 \
  --generate-ssh-keys \

Or for Azure RedHat Openshift:

az aro create \
  --resource-group $RESOURCEGROUP \
  --name $CLUSTER \
  --vnet $VIRTUALNETWORK \
  --master-subnet master-subnet \
  --worker-subnet worker-subnet \
  --version <x.y.z>

When using our terraform templates, creating a resource group and attaching the service principal to it (reducing the scope of the role binds as a result) I cannot specify for the azure environment to use it. This changes that by allowing for the resource group to be specified.

Signed-off-by: Daniel J. Holmes (jaitaiwan) <dholmes@altinity.com>
@jaitaiwan jaitaiwan force-pushed the jaitaiwan/azure-resource-group branch from 1488264 to 10d0789 Compare March 24, 2026 06:28
@ianaya89 ianaya89 force-pushed the master branch 5 times, most recently from 2977209 to 45e4e9a Compare April 10, 2026 04:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant