diff --git a/src/pages/release-announce/1.5.2.md b/src/pages/release-announce/1.5.2.md
new file mode 100644
index 00000000000..a887dcbc661
--- /dev/null
+++ b/src/pages/release-announce/1.5.2.md
@@ -0,0 +1,45 @@
+---
+id: rn-1.5.2
+title: Release Announcement v1.5.2
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# Release Announcement v1.5.2
+We are pleased to announce that the Apache YuniKorn community has voted to release 1.5.2. 
+Apache YuniKorn is a standalone resource scheduler, designed for managing and scheduling Batch and Data workloads on container
+orchestration frameworks like Kubernetes for on-prem and on-cloud use cases.
+
+## Overview
+The Apache YuniKorn community has resolved 17 [JIRAs](https://issues.apache.org/jira/issues/?filter=12353487) in this release.
+
+Release manager: Peter Bacsko
+
+Release date: 2024-07-26
+
+## Highlights
+### Locking fix to avoid deadlock on node addition
+Yunikorn could enter a deadlock when a node is added during scheduling. This is now fixed, see [YUNIKORN-2629](https://issues.apache.org/jira/browse/YUNIKORN-2629) for details.
+
+### CSINodes informer
+Node volume limits and other that scheduling actions that relied on the CSINode objects failed as the CSINode informer was not started. This was fixed in [YUNIKORN-2621](https://issues.apache.org/jira/browse/YUNIKORN-2621) and the CSINode informer now gets started by default.
+
+### Skip setting the default queue name
+The default queue name no longer gets set on the pod to allow placement rules to be executed correctly in specific configurations. Placement behaviour has not changed except for the specific configurations. Details are in [YUNIKORN-2703](https://issues.apache.org/jira/browse/YUNIKORN-2703) and [YUNIKORN-2711](https://issues.apache.org/jira/browse/YUNIKORN-2711).