macstadium · celanthe · May 22, 2026 · May 22, 2026
diff --git a/macstadium/macstadium-overview/ip-plan.mdx b/macstadium/macstadium-overview/ip-plan.mdx
@@ -1,16 +1,16 @@
 ---
 title: "Viewing your environment in My Cloud"
 description: "My Cloud in the MacStadium Portal shows your environment by data center: public servers, firewalls, VPN credentials, network allocations, and host assignments."
 zendesk_id: 28230867289883
 ---
 
 The **My Cloud** page in the MacStadium Portal is where you see the networking and access details for your environment — VPN credentials, network ranges, firewall public IPs, and the IP assignments for your servers.
 
-> My Cloud replaces the IP Plan spreadsheet that was previously distributed. Other MacStadium docs may still refer to this information as "your IP Plan"; this is now under My Cloud.
+<Note>My Cloud replaces the IP Plan spreadsheet that was previously distributed. Other MacStadium docs may still refer to this information as "your IP Plan"; this is now under My Cloud.</Note>
 
 ## Open My Cloud
 
 1. Sign in to the [MacStadium Portal](/macstadium/macstadium-overview/macstadium-portal) at [portal.macstadium.com](https://portal.macstadium.com/login).
 2. Open **My Cloud**.
 3. Select the data center tab for the environment you want to view (Atlanta, Las Vegas, or Dublin).

@@ -18,11 +18,11 @@

 My Cloud groups your environment by data center. For each data center you'll see:

 - **Public Servers** — servers reachable on the public internet, with their public IPs and hostnames.
 - **Firewalls** — each dedicated firewall has its own section, containing:
  - **IP Allocation** — the networks behind the firewall, with subnet (CIDR), range, mask, and gateway.
  - **Credentials** — username and password for [connecting to the environment via VPN](/orka/networking-with-orka-at-macstadium/vpn-connection), and (where provisioned) for **Harbor OCI Storage** and **Private Cloud**. Select **Show** to reveal, then copy.
  - **Host Assignments** — servers assigned to each network, with their private IPs and (where applicable) public NAT IPs.

 The firewall's public IP is the address you use as the VPN server address and as the on-prem peer when configuring a site-to-site VPN tunnel — see the setup guides for [AWS](/orka/networking-with-orka-at-macstadium/aws-orka-connections), [GCP](/orka/networking-with-orka-at-macstadium/gcp-orka-connections), or [Azure](/iaas/azure/site-to-site-vpn-configuration-with-azure).

@@ -41,12 +41,12 @@

 ## Field reference

 Other MacStadium docs refer to legacy field names from the old IP Plan spreadsheet. Use this mapping when you're looking them up in My Cloud:

 | Looking for... | Find it in My Cloud |
 |---|---|
 | VPN server address, `FW1-Outside`, or the `Outside` network | The firewall's public IP, shown at the top of the firewall's section |
 | VPN username and password | **Credentials** for that firewall |
 | The `Private-1` network (or any internal network) | A row in the firewall's **IP Allocation** table. The **Subnet ID** column is the CIDR you'll need for VPN tunnels. |
 
-> Network names vary by environment. If your environment was provisioned with custom network names, use the **IP Allocation** table to identify the equivalent networks.
+<Note>Network names vary by environment. If your environment was provisioned with custom network names, use the **IP Allocation** table to identify the equivalent networks.</Note>
diff --git a/orka/orka-overview/tools-integrations.mdx b/orka/orka-overview/tools-integrations.mdx
@@ -1,29 +1,29 @@
 ---
 title: "Orka tools, CLI downloads, and CI/CD plugins"
 description: "Download Orka3 CLI binaries for macOS, Linux, and Windows, plus Orka VM Tools and CI/CD integrations for Jenkins, GitHub Actions, GitLab, and Buildkite."
 zendesk_id: 28347376278299
 ---

 Tools for accessing the Orka service. CI/CD integrations for Orka.

 ## Orka3 CLI

 Visit the links below to download a version of the Orka CLI binary that matches your environment.

 | Release | Notes | macOS ARM | macOS AMD | Linux | Windows |
 |---------|-------|-----------|-----------|-------|---------|
 | Orka3 CLI v3.6.1 *(Latest)* | [What's new](#orka3-cli-v361) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.6.1/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.6.1/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.6.1/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.6.1/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.6.0 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-36-release-notes) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.6.0/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.6.0/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.6.0/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.6.0/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.5.2 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-35-release-notes) | [Download](https://cli-builds-public.s3.amazonaws.com/official/3.5.2/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.amazonaws.com/official/3.5.2/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.5.2/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.5.2/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.5.1 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-35-release-notes) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.5.1/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.5.1/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.5.1/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.5.1/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.5.0 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-35-release-notes) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.5.0/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.5.0/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.5.0/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.5.0/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.4.0 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-34-release-notes) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.4.0/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.4.0/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.4.0/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.4.0/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.3.0 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-33-release-notes) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.3.0/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.3.0/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.3.0/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.3.0/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.2.0 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-32-release-notes) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.2.0/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.2.0/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.2.0/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.2.0/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.1.0 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-31-release-notes) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.1.0/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.1.0/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.1.0/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.1.0/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.0.2 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-30-release-notes#orka-v302) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.2/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.2/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.2/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.2/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.0.1 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-30-release-notes#orka-v301) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.1/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.1/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.1/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.1/orka3/windows/amd64/orka3.exe) |
 | Orka3 CLI v3.0.0 | [Release notes](/orka/orka-upgrades-and-release-notes/orka-30-release-notes) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.0/orka3/macos/arm64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.0/orka3/macos/amd64/orka3.pkg) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.0/orka3/linux/amd64/orka3.tar.gz) | [Download](https://cli-builds-public.s3.eu-west-1.amazonaws.com/official/3.0.0/orka3/windows/amd64/orka3.exe) |

 Complete the installation

@@ -35,13 +35,13 @@

 <Tip>Using Homebrew? Try `brew install --cask orka3`.</Tip>

 ### Orka3 CLI v3.6.1

 **Bug fix:** Fixed an issue where the Orka CLI did not support private NAT IP addresses. Customers whose environments use a private address space for NAT IPs can now connect to their Orka clusters without issue. No configuration changes are required.

 ## Orka3 API

 In addition to the [Orka CLI](/orka/quick-start-guides/orka3-cli-quick-start), MacStadium offers full-featured API integration as well.

 Check the [API Documentation](https://macstadium.github.io/orka-api-docs/) for more details.

@@ -53,7 +53,7 @@

 ## CI/CD integrations

 MacStadium is constantly working on expanding the list of Orka integrations with leading CI/CD solutions.

  * [**Jenkins**](/orka/orka-devops-integrations/jenkins)
  * [**GitLab**](/orka/orka-devops-integrations/gitlab)
@@ -67,11 +67,9 @@
 
 <Warning>Always run matching versions across your Orka cluster, Orka CLI, Orka VM Tools, and any CI/CD integrations. A version mismatch can cause deployment failures, broken image caching, and unexpected behavior. For example, if your cluster runs 3.5.x, your CLI and VM Tools should also run 3.5.x.</Warning>
 
-> **TIP: Using Homebrew?**
-> 
-> Try `brew install orka-vm-tools` for a fresh install on a newly deployed VM.
-> 
-> Try `brew upgrade orka-vm-tools` to update any existing installation. Make sure to `commit` or `save` the changes to the base image and redeploy any existing VMs.
+<Tip>
+**Using Homebrew?** Run `brew install orka-vm-tools` for a fresh install. To update an existing installation, run `brew upgrade orka-vm-tools`. Make sure to `commit` or `save` the changes to the base image and redeploy any existing VMs.
+</Tip>
 
 Orka VM Tools are guest tools installed on your ARM-based VMs. They enable features like Disk Image Resize and VM Metadata.
 

diff --git a/orka/orka-upgrades-and-release-notes/orka-33-release-notes.mdx b/orka/orka-upgrades-and-release-notes/orka-33-release-notes.mdx
@@ -41,7 +41,7 @@

 ### Next steps:

 We recommend that all customers using Orka 3.3.0 and above apply this hotfix immediately, especially those that are operating medium or large-load ARM-based infrastructure, or high-volume VM deployments.

 If you have any questions or require assistance, please [contact our support team](https://docs.macstadium.com/docs/support)

@@ -53,9 +53,9 @@

  * Consistent Hardware UUID generation is good for use cases that require the same Hardware UUID and serial number for each deployment. This is often the case for code signing or other workflows that expect a specific machine identifier.

  * Dynamic Hardware UUID generation is good for use cases that require unique identifiers, such as VDI or remote desktop use cases where each desktop is assigned to an individual user. MDM integration may also depend on having unique Hardware UUIDs.

 The default system behavior is consistent Hardware UUIDs. [Contact our support team](/macstadium/support/support) to switch to dynamic Hardware UUID generation.

 OCI integration now supports Harbor as a repository.

@@ -63,13 +63,13 @@

 ## Improvements and Fixes

 Orka 3.3.1 is a patch release that addresses compatibility issues with JAMF MDM.

 # Orka 3.3.0

 ## New Features

  * [Orka Burst](/orka/orka-resources/burst) is now available to customers, providing dedicated, on-demand access to elastic cluster capacity as needed. If you are interested in adding burst nodes to your account, please get in touch with MacStadium through your Account Portal.
  * Component versions are now shown with the `orka3 version` and `orka3 node list -o wide` commands.
  * Orka worker nodes are upgraded to macOS 15.5.

@@ -89,7 +89,9 @@
 
 **Known Issues**
 
-> If you implement code signing workflows in Orka this message pertains to you. Please consider your workflows before deciding to upgrade to 3.3.0
+<Warning>
+If you implement code signing workflows in Orka, review your workflows before deciding to upgrade to 3.3.0.
+</Warning>
 
 The 3.3.0 release implements behaviors to align with Apple’s guidelines for Virtualization regarding identifiers, as discussed in [VZMacMachineIdentifier | Apple Developer Documentation](https://developer.apple.com/documentation/virtualization/vzmacmachineidentifier), such that VMs are always created with a unique machine identifier.
 

diff --git a/orka/orka-upgrades-and-release-notes/orka-35-release-notes.mdx b/orka/orka-upgrades-and-release-notes/orka-35-release-notes.mdx
@@ -45,7 +45,7 @@
 ```
 diskutil list internal physical
 ```
 Look for the disk identifier in the output. The disk will initially be unformatted and will not contain a filesystem.

  2. Format and mount the disk:

@@ -106,7 +106,7 @@



 ### Default Namespace Detection in Orka CLI

 The Orka CLI now reads the default namespace directly from your `orka` kubeconfig context, implementing hierarchical namespace resolution with environment-level overrides also available.

@@ -177,7 +177,7 @@

 ### Release summary

 The Orka v3.5.1 hotfix addresses five issues affecting ARM nodes, Orka operator, and the Orka CLI. All fixes can be deployed with zero downtime.

 ### Fixed issues

@@ -187,17 +187,17 @@

 Fix: Added automatic detection and self-healing for NAT networking issues. If self-healing fails, the VM deployment will fail and the VM will be deleted. Note that most common integrations (e.g., Jenkins) will then simply re-deploy the VM.

 #### Node Resource Display in Custom Namespaces

 Issue: `orka3 node list -o wide` incorrectly showed resource usage for nodes in non-default namespaces. This issue was cosmetic only, and had no impact on scheduling VMs.

 Fix: Corrected resource reporting logic to accurately display usage across all namespaces.

 #### Image Caching in Custom Namespaces

 Issue: `orka3 ic add` silently failed when caching images to nodes in custom namespaces.

 Fix: Image caching now works correctly across all namespaces. You will need to re-cache any previously failed images after applying this hotfix.

 #### Service Account Permissions Loss

@@ -213,7 +213,7 @@

 ### Deployment

 The Orka v3.5.1 hotfix patch is a zero-downtime deployment. Note that Orka clusters must be at least on Orka v3.4+ / k8s v1.33 to be upgraded to v3.5.1.

 ### Support

@@ -227,7 +227,7 @@
 
 ### Bridged networking support:
 
-> Note: Customers must configure their own DHCP server on the network infrastructure. Static IP configuration through Orka is not currently supported.
+<Note>Customers must configure their own DHCP server on the network infrastructure. Static IP configuration through Orka is not currently supported.</Note>
 
 The release of Orka 3.5.0 brings with it new support for bridged networking for customers running [Orka On-Prem](/orka/orka-on-aws-and-on-prem/orka-on-prem-getting-started), enabling seamless connectivity from a virtual environment to a physical network environment.
 
@@ -239,28 +239,28 @@

 For more information on getting started using bridge networking with Orka, please visit: [Bridge networking with Orka](/orka/orka-on-aws-and-on-prem/using-bridge-networking-with-orka-350).

 ### MacOS 26 Tahoe guest support:

 #### Key capabilities:

 Orka 3.5.0 now allows users to create guest VM images using MacOS 26 (Tahoe).

 #### Getting started:

 You can get started with Tahoe by downloading the latest image from [OrkaHub](https://orkahub.com/), or our Tahoe package in the [orka-images repository](https://github.com/orgs/macstadium/packages/container/package/orka-images%2Ftahoe). Tahoe guest VMs can be run using the Orka CLI, or by using Orka Desktop.

 #### Technical requirements:

  * A Sequoia 15.5 host is required in order to run a MacOS Tahoe 26 guest image

  * Orka does not currently officially support running Tahoe on a host machine. We aim to officially support MacOS 26 hosts in the upcoming Orka 3.6.0 release.




 ### OCI storage:

 Orka 3.5.0 introduces Harbor OCI storage as an alternative to NFS storage in Orka. OCI is now our default managed storage solution for new Orka customers (existing customers will keep their current storage). Your OCI instance comes preconfigured with everything needed to push and pull macOS VM images using the Orka CLI. When you purchase hosted storage through MacStadium, OCI is included as a managed service with automatic resource scaling based on your available Orka nodes. While external repositories will still remain supported for use with Orka, our managed Harbor instance provides better performance and reliability.

 #### Key capabilities:

@@ -287,7 +287,7 @@

  * Performance and stability improvements have been made to the Orka Nodes.

  * New [Packer template examples](https://github.com/macstadium/packer-plugin-macstadium-orka/tree/main/examples) are now available, adding popular developer tools such as Homebrew, Cocoapods, Swift, xcodes, Git, and Fastlane on top of our latest existing MacOS Tahoe and MacOS Sequoia 15.5 base images.

  * NFS connection is now self-healing


diff --git a/orka/quick-start-guides/web-ui-quick-start.mdx b/orka/quick-start-guides/web-ui-quick-start.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Orka Web UI quick start guide"
 description: "Get started with the Orka Web UI: browse nodes and images, create VM configs, deploy VMs, connect via Screen Sharing, and save changes as a new base image."
 zendesk_id: 28393197020059
 ---

@@ -12,8 +12,8 @@
  2. Launch the Orka UI in your browser at `<ORKA_API_URL>`.
  3. Go to **Nodes**.
  4. Go to **Images**.
  5. Go to **VM Configs** and click **Create config** (select an available macOS image, 3 for CPU and vCPU, leave VNC enabled).
  6. Click **Deploy Config** and wait for the confirmation.
  7. Go to **VMs** and check the connection information for the instance.
  8. Use Apple Screen Sharing to connect to the VM instance. Example: `vnc://<VM-IP>:<Screenshare-port>` with the IP and port from Step 7. Use the `admin/admin` credentials.
  9. Once you login be sure to change the login credentials, apply the latest OS updates, and install (or upgrade) the Orka VM Tools for added security and functionality.
@@ -21,7 +21,7 @@
  11. Return to the UI. Go to the **Images** page and make sure that your new image appears in the list.
  12. On the **VMs** page, select your VM instance and click **More** > **Delete** at the top.
  13. Make sure that the list of VMs is empty.
  14. Go to **VM configs** and verify that your template is preserved.



@@ -36,7 +36,7 @@

 ## 1. Before You Begin

  1. Ensure you can access your cluster account in the MacStadium Customer Portal. See [Cluster Access Management: Overview](/orka/orka-cluster-access/cluster-access-management-overview).
  2. Get your VPN connection information from your IP Plan. You can [download](/macstadium/macstadium-overview/ip-plan) it from the [MacStadium portal](https://portal.macstadium.com/).
  3. Connect to your Orka cluster via VPN.
     1. [Download and install a VPN client](/orka/networking-with-orka-at-macstadium/vpn-connection). Note that you might need to make additional configuration changes if you're using a custom Orka domain.
@@ -46,7 +46,7 @@

 ## 2. Authenticate with the Cluster

 Orka lets you log in with your MacStadium Customer Portal credentials. Your access privileges are based on the role configured by your account admin in the Customer Portal. By default, you will have access to the `orka-default` namespace. You can access additional namespaces if you have been added to additional role bindings.


 ```bash
@@ -68,15 +68,17 @@
 
 
 
-> #### **What's your Orka API URL?**
-> 
-> You can get your Orka API URL from your [IP Plan](/macstadium/macstadium-overview/ip-plan):
-> 
->   * For clusters deployed before Orka 2.1, it's the `.100` address for your `Private-1` network (usually, `10.221.188.100`), prefixed with `http`. For example: `http://10.221.188.100`.
->   * For clusters deployed with Orka 2.1 or later, it's the `.20` address for your `Private-1` network (usually `10.221.188.20`), prefixed with `http`. For example: `http://10.221.188.20`.
->   * You can also use `https://<orka-domain>` and `https://<custom-domain>` (if configured). To get the [Orka domain](/orka/networking-with-orka-at-macstadium/built-in-orka-domains) for your Orka cluster, [contact MacStadium support](https://portal.macstadium.com/login). To use an external custom domain, see [here](/orka/networking-with-orka-at-macstadium/external-custom-domains).
-> 
-> Note that you can use `http://<orka-IP>`, `https://<orka-domain>`, and `https://<custom-domain>` interchangeably in your workflows.
+<Tip>
+**What's your Orka API URL?**
+
+You can get your Orka API URL from your [IP Plan](/macstadium/macstadium-overview/ip-plan):
+
+  * For clusters deployed before Orka 2.1, it's the `.100` address for your `Private-1` network (usually, `10.221.188.100`), prefixed with `http`. For example: `http://10.221.188.100`.
+  * For clusters deployed with Orka 2.1 or later, it's the `.20` address for your `Private-1` network (usually `10.221.188.20`), prefixed with `http`. For example: `http://10.221.188.20`.
+  * You can also use `https://<orka-domain>` and `https://<custom-domain>` (if configured). To get the [Orka domain](/orka/networking-with-orka-at-macstadium/built-in-orka-domains) for your Orka cluster, [contact MacStadium support](https://portal.macstadium.com/login). To use an external custom domain, see [here](/orka/networking-with-orka-at-macstadium/external-custom-domains).
+
+Note that you can use `http://<orka-IP>`, `https://<orka-domain>`, and `https://<custom-domain>` interchangeably in your workflows.
+</Tip>
 
 ![Orka UI login page in browser](/images/attachments/28393224419867.png)
 
@@ -98,29 +100,29 @@

  2. In the sidebar, click **Images**.

 You will likely see one or more macOS images listed. MacStadium pre-built images come with an admin user configured and SSH and Apple Screen Sharing access enabled.

  3. In the sidebar, click **VM Configs**.

 If this is your first time using Orka, you will get a blank screen.

  4. On the **VM Configs** page, click **Create config** and fill in the form:

  * **Name:** Set any user-friendly name that will help you recognize the VM.
  * **Base image:** Select an available macOS image from the list. (Note that the settings in the dialog change based on the selected image type.)
  * **CPU:** Set to 3. This is the number of CPUs for the VM.
  * **vCPU:** Set to 3. Unless the CPU is 3, it must be half of or the exact number of CPUs. This denotes if hyperthreading is enabled. For example, if the vCPU equals CPU, hyperthreading is enabled.
  * **Memory (G):** Leave blank. Orka automatically assigns memory when this field is empty. If you provide a value, it overrides the default and allocates the specified amount.

 <Note>
 **VM name requirements:** The name must not exceed 38 characters, must contain only lowercase alphanumeric characters (0-9, a-z) and dashes (-), and must begin and end with an alphanumeric character.
 </Note>

 ![Create VM config form with name, image, CPU, and vCPU fields](/images/attachments/28393224435355.png)

 This creates a VM config.

  5. On the **VM Configs** page, select your newly created template and click **Deploy config**. Make sure that your template is selected and click **Deploy**.

 Wait for the loading UI at the bottom of the dialog to complete. A success message should pop up at the top of the screen.

@@ -150,7 +152,7 @@

 One more thing to remember is that Screen Sharing must already be enabled within your macOS VM. This is usually not the case (especially on clean OS installs or after an ISO install (Intel only)), and you must enable the setting yourself. This also applies to SSH connectivity.

 The good news is that MacStadium pre-built images are already preconfigured for you, and you can enjoy out-of-the-box Screen Sharing and SSH connectivity.

 <Note>
 If you're using a custom image or installing from ISO (Intel only), SSH and Screen Sharing are not enabled by default. Connect via VNC first, then enable them in the OS.
@@ -209,13 +211,13 @@

 _This section is optional._

 When your VM configs and instances have served their purpose, you can remove them. Deleting a VM instance always preserves the original VM config, and you can deploy new instances from it at any time.

  * On the **VMs** page, select your VM. Select **More** > **Delete**. When prompted, confirm that you want to delete the VM.

 ![VM More menu with Delete option highlighted](/images/attachments/28393197015195.jpg)

 When the page refreshes, you should not see any more VM instances. Your VM config is still available on the **VM Configs** page, and you can deploy new instances from it.

 Note that the changes you made to your deleted VM instance will not be present on newly deployed instances.