Set up an Azure Kubernetes Service connector

Capabilities

Gather Azure Kubernetes Service credentials

Configuring the connector requires you to pass in credentials generated in Azure Kubernetes Service. Gather these credentials before you move on.

To create a Service Principal in Azure Kubernetes Service the user must have the following permissions:

• Application.ReadWrite.All
• Directory.ReadWrite.All

Roles that grant these permissions include:

• Azure AD Administrator
• Application Administrator
• Cloud Application Administrator

To assign a role to the Service Principal, the user must have Azure resource-level permissions, typically at the subscription, resource group, or AKS resource level:

• Microsoft.Authorization/roleAssignments/write permission

Look up your Azure subscription ID and cluster resource group name

1. In Azure, search for and navigate to your cluster’s home page.

2. On the Overview tab, locate the Essentials section.

3. Make a note of the cluster’s resource group name and subscription ID.

Look up your tenant ID

1. In the main search bar, click Tenant properties.

2. Make a note of the tenant ID.

Create a Service Principal

If desired, you can use an existing Service Principal. Follow these steps if you want to create a new one.

1. In Entra admin center, navigate to App registrations.

2. Click + New registration.

3. Give the application a name, such as “ConductorOne”.

4. Select the supported account type appropriate for your organization. For most internal automation, “Accounts in this organizational directory only (Single tenant)” is sufficient.

5. You do not need to set a redirect URI.

6. Click Register.

7. The new app is created. Carefully copy and save the Application (client) ID and the Directory (tenant) ID shown on the application summary page.

8. Next, we’ll generate a client secret for this app. Click Certificates & secrets.

9. Click + New client secret.

10. Give the client secret a description and set its expiration.

11. Click Add.

12. The client secret is generated. Carefully copy and save the Secret Value.

Assign Azure RBAC permissions to the Service Principal

Next, grant this Service Principal the Reader role at the subscription level so it can discover and read all your AKS cluster information.

1. In the Azure portal’s search bar, type “Subscriptions” and select the relevant Azure subscription.

2. In the left-hand menu of your Subscription, select Access control (IAM).

3. Click + Add > Add role assignment.

4. On the Role tab, search for and select the Reader role.

5. Click Next.

6. On the Members tab, ensure User, group, or service principal is selected for Assign access to.

7. Click + Select members.

8. In the Select members pane, search for and select the name of your App Registration.

9. Click Select at the bottom of the pane.

10. Click Review + assign at the bottom.

Allow time for the new role to propagate. Azure role assignments can take several minutes (typically five to 15, sometimes up to 30) to fully propagate.

Make sure your Service Principal has cluster access

The Service Principal must have access to the cluster in Azure and the proper permissions defined in the cluster.

1. In Azure, navigate to the cluster’s admin page and click Access control (IAM).

2. Locate Role assignments add a new assignment for your Service Principal. Commonly used roles are “Azure Kubernetes Service Cluster User Role” and “Azure Kubernetes Service Cluster Admin Role”.

Be aware that propagation of this assignment may take some time (up to multiple hours) depending on the size and complexity of your cluster.

That’s it! Next, move on to the connector configuration instructions.

Configure the Azure Kubernetes Service connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Azure Kubernetes Service credentials generated by following the instructions above

# baton-aks-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-aks-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Azure Kubernetes Service credentials
  BATON_SUBSCRIPTION_ID: <Azure subscription ID>
  BATON_RESOURCE_GROUP: <Resource group name of the cluster>
  BATON_CLUSTER_NAME: <Name of the cluster to sync>
  BATON_TENANT_ID: <The directory (tenant) ID where your service principal is registered>
  BATON_SP_CLIENT_ID: <The Application (client) ID of your service principal>
  BATON_SP_CLIENT_SECRET: <The client (Service Principal) secret>

# baton-aks.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-aks
  labels:
    app: baton-aks
spec:
  selector:
    matchLabels:
      app: baton-aks
  template:
    metadata:
      labels:
        app: baton-aks
        baton: true
        baton-app: aks
    spec:
      containers:
      - name: baton-aks
        image: ghcr.io/conductorone/baton-aks:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-aks-secrets