Running the remote-deployment PowerShell setup's .\main.ps1 -resource 'KUBERNETES' step fails, even though the preceding -resource 'KEY' step completed successfully and manual SSH from the management server to the middle-tier server works (albeit still prompting for a password).

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This has been traced to file and directory permission issues, affecting both the Windows-side folders/key files on the management server and the corresponding directories/files on the Linux middle-tier server — not a configuration mistake in main_config.json itself. Explicitly setting the correct permissions on both the Windows-side key/folder locations and the Linux-side SSH-related files and directories (rather than just the key file referenced in configuration) resolved this for at least one confirmed case; if the KEY step succeeds but KUBERNETES fails right after, permissions on both sides of that SSH trust relationship are the first thing worth checking.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions