Update ssh-infrastructure-access.mdx (#16999)

* Update ssh-infrastructure-access.mdx

* Update src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx

---------

Co-authored-by: ranbel <101146722+ranbel@users.noreply.github.com>

src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx

@@ -14,6 +14,10 @@ import { Tabs, TabItem, Badge, Render } from "~/components";
 [Access for Infrastructure](/cloudflare-one/applications/non-http/infrastructure-apps/) uses the same deployment model as [WARP-to-Tunnel](/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-warp-to-tunnel/) but unlocks more granular policy options and command logging functionality.
 <Render file="access/short-lived-certs-intro" params={{ intro: "Furthermore, Access for Infrastructure replaces" }} />
 
+:::note
+SSH with Access for Infrastructure is currently available in early access.
+:::
+
 ## 1. Connect the server to Cloudflare
 
 1. Create a Cloudflare Tunnel for your server by following our [dashboard setup guide](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/). You can skip the connect an application step and go straight to connecting a network.
@@ -120,4 +124,4 @@ To manually retrieve logs:
 3. Select **Download** to download the session's command log.
 4. <Render file="ssh/decrypt-ssh-log" />
 
-Enterprise customers can also export command logs using [Logpush](/cloudflare-one/insights/logs/logpush/).
+Enterprise customers can also export command logs using [Logpush](/cloudflare-one/insights/logs/logpush/).