Accessing Fkh containers using a terminal
Fkh provides secure, just-in-time terminal access to Business Central containers running in Kubernetes clusters through three methods: kubectl with PowerShell, WinRM access via CLI, or WinRM access via VS Code. Each approach prioritizes security by avoiding public exposure and standing credentials.
Read it hereOpen in Claudehttps-freddysblog-com-2026-08-06-accessing-fkh-containers-using-a-terminal--97f2673eb6.md
post Freddys blog
Key points
- Containers run as Kubernetes pods in Azure subscriptions, not exposed publicly, requiring secure tunneling for access
- Two primary options: kubectl exec for admins with cluster access, or WinRM with GitHub authentication scoped to user IP and time-limited
- WinRM is the recommended Fkh-native approach offering the same secure, just-in-time model as database access without requiring kubectl installation
- Windows account lockout policy after three failed attempts in 15 minutes protects against brute-force attacks
- VS Code integration allows WinRM access from the editor with automatic output showing connection details
Context
- Features: Just-in-time terminal access, WinRM session management, kubectl integration, VS Code container terminals, GitHub authentication, IP-scoped access, Time-limited tunnels, PowerShell remoting
Source: Freddys blog, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.