// Benutzung · Grundlagen
Adding a resource to a location
A resource is a specific piece of infrastructure under a location — a Proxmox node, a Kubernetes cluster, or an iDRAC host.
- Select Locations, then select the name of the location you want.
- In the New resource panel:
- Kind —
proxmox_node,k8s_cluster, oridrac_host. - Address — how the agent reaches it, e.g.
https://pve1.local:8006for Proxmox. Use a name or IP that resolves from wherever the agent runs (see networking for a homelab). - Allow invalid/self-signed TLS certs (proxmox/idrac only) — see self-signed TLS below.
- Tags (optional) — comma-separated labels for organizing and
filtering, e.g.
env:prod, owner:you.
- Kind —
- Select Add resource. It appears in the table with its tags and whether a credential is attached.
Editing or deleting
- Edit — select Edit on a row to change its kind, address, or tags, then Save changes.
- Delete — select Delete and confirm. A stored credential is not deleted with the resource: it stays in the location's credentials, marked orphaned (unless another resource still uses it), until you delete it there. The resources discovered under it (a Proxmox node's VMs and CTs, a cluster's Kubernetes objects) are deleted with it, and the confirmation says how many. They come back only if you register the resource again and the agent rediscovers them, as new resources. For a registered resource, its reachability state and theirs go with them: no unreachable alert fires for them, and one already firing is cleared as no longer monitored. Deleting a discovered resource on its own clears nothing, since the agent keeps collecting it through its parent. If ingestion-svc is unreachable during the delete, the gateway keeps retrying for about 10 minutes and the state goes once ingestion-svc is back; meanwhile an unreachable alert can fire, and it is cleared then. If it stays unreachable that long, or the agent predates rc.3, their state ages out instead, and an unreachable alert can fire until the stale ceiling retires it.
Self-signed TLS
For proxmox and idrac resources the form has an Allow invalid/self-signed
TLS certs checkbox. Proxmox's :8006 API and most BMCs ship a self-signed
certificate, so with the box unticked every collection fails TLS verification.
Ticking it makes the agent skip certificate verification for that endpoint
only. For a LAN-local homelab that's the usual choice; alternatively, install a
certificate the agent trusts and leave it unticked. The flag lives on the
resource (not the credential), so it applies no matter which credential is
attached.
With a saved credential (one picked from Existing credential, or one the
resource already has), ticking it needs the permission
resource.allow_invalid_certs at the location — with the checks off, a man in
the middle could read that stored secret. Without it the form keeps the box
off and says why; entering the secret as a new credential while creating the
resource works for anyone with resource.create.
Credentials
The Credential column shows set when a resource has an encrypted
credential attached and — when it does not. Credentials are stored encrypted
and are never displayed back. Each kind expects a different secret shape — see
credential shapes by kind;
attaching and rotating them is covered in
managing credentials.