diff --git a/macstadium/macstadium-overview/ip-plan.mdx b/macstadium/macstadium-overview/ip-plan.mdx index 2f7e8db..df3967c 100644 --- a/macstadium/macstadium-overview/ip-plan.mdx +++ b/macstadium/macstadium-overview/ip-plan.mdx @@ -6,7 +6,7 @@ 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. +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. ## Open My Cloud @@ -49,4 +49,4 @@ Other MacStadium docs refer to legacy field names from the old IP Plan spreadshe | 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. +Network names vary by environment. If your environment was provisioned with custom network names, use the **IP Allocation** table to identify the equivalent networks. diff --git a/orka/orka-overview/tools-integrations.mdx b/orka/orka-overview/tools-integrations.mdx index 06d65d9..23e3771 100644 --- a/orka/orka-overview/tools-integrations.mdx +++ b/orka/orka-overview/tools-integrations.mdx @@ -67,11 +67,9 @@ MacStadium is constantly working on expanding the list of Orka integrations with 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. -> **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. + +**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. + 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 index b62b759..2d9a9f8 100644 --- a/orka/orka-upgrades-and-release-notes/orka-33-release-notes.mdx +++ b/orka/orka-upgrades-and-release-notes/orka-33-release-notes.mdx @@ -89,7 +89,9 @@ Orka 3.3.1 is a patch release that addresses compatibility issues with JAMF MDM. **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 + +If you implement code signing workflows in Orka, review your workflows before deciding to upgrade to 3.3.0. + 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 index cd24624..71b096b 100644 --- a/orka/orka-upgrades-and-release-notes/orka-35-release-notes.mdx +++ b/orka/orka-upgrades-and-release-notes/orka-35-release-notes.mdx @@ -227,7 +227,7 @@ We are excited to announce the latest Orka release, which brings with it signifi ### Bridged networking support: -> Note: Customers must configure their own DHCP server on the network infrastructure. Static IP configuration through Orka is not currently supported. +Customers must configure their own DHCP server on the network infrastructure. Static IP configuration through Orka is not currently supported. 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. diff --git a/orka/quick-start-guides/web-ui-quick-start.mdx b/orka/quick-start-guides/web-ui-quick-start.mdx index 08c9986..7ffa309 100644 --- a/orka/quick-start-guides/web-ui-quick-start.mdx +++ b/orka/quick-start-guides/web-ui-quick-start.mdx @@ -68,15 +68,17 @@ orka3 user get-token -> #### **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://` and `https://` (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://`, `https://`, and `https://` interchangeably in your workflows. + +**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://` and `https://` (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://`, `https://`, and `https://` interchangeably in your workflows. + ![Orka UI login page in browser](/images/attachments/28393224419867.png)