Squashed commit of the following:

8.6.5 release

Author: adriankjohnson

articles/cyclecloud/how-to/ccws/connect-to-portal-with-bastion.md

@@ -0,0 +1,35 @@
+---
+title: How to connect to the CycleCloud Portal through Bastion
+description: How to securily connect to the CycleCloud Portal using Bastion
+author: xpillons
+ms.date: 11/22/2024
+ms.author: padmalathas
+---
+
+# How to connect to the CycleCloud Portal through Bastion
+You can deploy an Azure Bastion to establish an SSH tunnel to your Azure CycleCloud virtual machine when the HTTPS route is unavailable in your local environment. For detailed instructions, see [Connect to a VM - tunnel command](/azure/bastion/connect-vm-native-client-linux#tunnel).
+
+## Step 1 – Retrieve the Resource ID of the CycleCloud VM
+To retrieve the resource ID of the `ccw-cyclecloud-vm` virtual machine, navigate to the Azure Portal. From the virtual machine view, select **Settings**, then **Properties**, and you will find the **ResourceID**.
+
+## Step 2 – Create a connect script
+Create a bash script using the template below. Paste the CycleCloud `resourceID` retrieved above.
+
+```bash
+#!/bin/bash
+
+resourceId=<vm_resource_id>
+resourceGroup=$(echo $resourceId | cut -d'/' -f5)
+
+az network bastion tunnel --name bastion --resource-group $resourceGroup --target-resource-id $resourceId --resource-port 443 --port 8443
+```
+
+> Note: The github repository https://github.com/Azure/cyclecloud-slurm-workspace.git contains the utility script _./util/tunnel_thru_bastion.sh_ to help connecting.
+
+
+## Step 3 - Create the tunnel
+Run the script created/updated above to start the SSH tunnel.
+
+## Step 4 - Connect to CycleCloud
+
+Browse to `https://localhost:8443` and connect to CycleCloud.

articles/cyclecloud/release-notes.md

@@ -29,6 +29,8 @@ CycleCloud 8.6 is the sixth GA release of the CycleCloud 8.x platform and contin
 ## Release Notes
 
 Comprehensive release notes for the individual 8.x releases are listed below:
+
+* [**8.6.5 Release Notes**](release-notes/8-6-5.md) - released on 10/24/24
 * [**8.6.4 Release Notes**](release-notes/8-6-4.md) - released on 08/30/24
 * [**8.6.3 Release Notes**](release-notes/8-6-3.md) - released on 07/18/24
 * [**8.6.2 Release Notes**](release-notes/8-6-2.md) - released on 05/31/24

articles/cyclecloud/release-notes/8-6-4.md

@@ -25,3 +25,8 @@ ms.author: bewatrou
 * Centos 7 is no longer supported for azslurm and slurm packages. 
 * Jetpack installation failed to retry the initial CycleCloud connection leading to occasional extension failures under load 
 * Resolved [CVE-2017-1000487](https://nvd.nist.gov/vuln/detail/CVE-2017-1000487), [CVE-2024-30105](https://nvd.nist.gov/vuln/detail/CVE-2024-30105), [CVE-2024-38095](https://nvd.nist.gov/vuln/detail/CVE-2024-38095), [CVE-2024-39338](https://nvd.nist.gov/vuln/detail/CVE-2024-39338), [CVE-2024-34750](https://nvd.nist.gov/vuln/detail/CVE-2024-34750), [CVE-2024-23672](https://nvd.nist.gov/vuln/detail/CVE-2024-23672), and [CVE-2024-24549](https://nvd.nist.gov/vuln/detail/CVE-2024-24549) 
+
+## Known Issues:
+
+* Configuring "CycleCloud" under the `Settings` page displays an error stating "Invalid form arguments". The workaround is to go to the Advanced tab and configure the `cyclecloud.default_authenticator`, `cyclecloud.eventgrid_topic`, `cyclecloud.single_cluster`, `cyclecloud.force_delete.vm`, and `cyclecloud.force_delete.vmss` settings directly, for example:
+![alt text](settings_workaround_image.png)

articles/cyclecloud/release-notes/8-6-5.md

@@ -0,0 +1,23 @@
+---
+title: Release Notes v8.6.5
+description: Product release notes for Azure CycleCloud v8.6.5
+author: doclayto
+ms.date: 10/23/2024
+ms.author: doclayto
+---
+
+# CycleCloud version 8.6.5 
+
+## New Features
+
+* CycleServer tracks and logs internal performance metrics like CPU and memory usage
+* The CycleCloud almalinux8 image now uses the AlmaLinux 8.10 HPC image by default rather than the deprecated AlmaLinux 8.7 HPC image.
+
+## Resolved Issues
+
+* Clusters with no owner failed to converge with UserData.processNode errors
+* The health monitor URL could trigger excessive garbage collection under load
+* CycleCloud could incorrectly use a loopback address (127.0.0.*) as its cluster address after its VM rebooted.
+* The Event Log page used far more resources than necessary to query data.
+* Clusters using AlmaLinux 8.10 failed to converge due to missing lvm2 package (resulting in vgscan errors).
+* Resolved CVE-2024-47554, CVE-2024-43485, CVE-2024-45801

articles/cyclecloud/release-notes/settings_workaround_image.png

@@ -88,6 +88,8 @@
       href: ./how-to/ccws/cleanup-roles.md
     - name: How to connect to a Login Node through Bastion
       href: ./how-to/ccws/connect-to-login-node-with-bastion.md
+    - name: How to connect to the CycleCloud Portal through Bastion
+      href: ./how-to/ccws/connect-to-portal-with-bastion.md
   - name: Cluster Operations
     items:
     - name: Create a Cluster