Skip to main content

tls, fleet server, vm

·185 words·1 min
Author
daniel parriott
bored and boring

install it local!
#

I’m passing on an eck installed fleet server at the moment. I haven’t had the energy to play with it lately, and I’m not sure my little cluster has the resources for it.

So I’m moving on to a local install on a new VM, hagal, running Ubuntu.

Here’s the command I used to get it installed (after creating the cert and key):

./elastic-agent install --fleet-server-es=https://prod-es.lab.wafflelab.online:9200 \
  --fleet-server-service-token=AAEAAWVsYXN0aWMvZmxlZXQtc2VydmVyL3Rva2VuLTE3MTExMjIzNTQ1MjA6OS14X0xxMFdRRU9rX0x6TGpHNkgzZw \
  --fleet-server-policy=fleet-server-policy \
  --fleet-server-port=8220 \
  --fleet-server-cert /etc/elastic/certs/hagal.lab.wafflelab.online.pem \
  --fleet-server-cert-key /etc/elastic/certs/hagal.lab.wafflelab.online.key \
  --url https://hagal.lab.wafflelab.online:8220

Hopefully this system will be able to keep up with the minimal agent stuff I’m going to try and push its way.

I had to change the kibana definitions a bit. Previously I defined a fleet host at prod-fl, but I didn’t want to change the dns for that so I created fleet as well pointing to the new host. (Hovering over the agent’s status icon provides a little info in the popup that might be useful in troubleshooting unhealthy or similar statuses.)

I really need to pick up another system or 3.

But first, the firewall replacement (of doom)!