The --knot option provisions a repository on the selected knot, but clone and initial push still build remotes for tangled.org. That leaves repositories created on self-hosted knots unable to complete the requested Git workflow.
Route those operations through the selected knot and accept its SSH port so deployments with nonstandard ports work too. Validate the connection settings before provisioning to avoid leaving behind a repository that cannot be reached as requested.