New-PveClusterConfigNodes

Adds a node to the cluster configuration. This call is for internal use.

API: POST /cluster/config/nodes/{node}, Proxmox VE API viewer

Syntax

New-PveClusterConfigNodes
    [-PveTicket <PveTicket>]
    [-Apiversion <int>]
    [-Force <bool>]
    [-LinkN <hashtable>]
    [-NewNodeIp <string>]
    -Node <string>
    [-Nodeid <int>]
    [-Votes <int>]
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-Apiversion	int	No	The JOIN_API_VERSION of the new node.
-Force	bool	No	Do not throw error if node already exists.
-LinkN	hashtable	No	Address and priority information of a single corosync link. (up to 8 links supported; link0..link7)
-NewNodeIp	string	No	IP Address of node to add. Used as fallback if no links are given.
-Node	string	Yes	The cluster node name.
-Nodeid	int	No	Node id for this 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.