New-PveClusterConfigJoin

Joins this node into an existing cluster. If no links are given, default to IP resolved by node’s hostname on single link (fallback fails for clusters with multiple links).

API: POST /cluster/config/join, Proxmox VE API viewer

Syntax

New-PveClusterConfigJoin
    [-PveTicket <PveTicket>]
    -Fingerprint <string>
    [-Force <bool>]
    -Hostname <string>
    [-LinkN <hashtable>]
    [-Nodeid <int>]
    -Password <SecureString>
    [-Votes <int>]
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-Fingerprint	string	Yes	Certificate SHA 256 fingerprint.
-Force	bool	No	Do not throw error if node already exists.
-Hostname	string	Yes	Hostname (or IP) of an existing cluster member.
-LinkN	hashtable	No	Address and priority information of a single corosync link. (up to 8 links supported; link0..link7)
-Nodeid	int	No	Node id for this node.
-Password	SecureString	Yes	Superuser (root) password of peer node.
-Votes	int	No	Number of votes for this node.

Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.

Output

A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.