Quickstart issues

[LuanaMartelli]

Hello !

Describe the bug Following the Quickstart guide (https://vsecm.com/docs/quickstart/), I ran into multiple issues.

To Reproduce Steps to reproduce the behavior:

$ make k8s-start
/bin/sh: 1: @CPU=2: not found
make: *** [makefiles/VSecMDeploy.mk:32: k8s-start] Error 127

I fixed (?) the issue by removing the @ of CPU in the file makefiles/VSecMDeploy.mk line 32:

@NODES=$(NODES) CPU=$(CPU) MEMORY=$(MEMORY) ./hack/minikube-start.sh

Then, still following the tutorial, I ran

helm repo add vsecm https://vmware-tanzu.github.io/secrets-manager/
helm repo update
helm install vsecm vsecm/vsecm
"vsecm" already exists with the same configuration, skipping
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "vsecm" chart repository
Update Complete. ⎈Happy Helming!⎈
NAME: vsecm
LAST DEPLOYED: Thu Jun  6 11:16:16 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None

But then I only got the server and not the agent, as expected.

$ kubectl get pods -n spire-system
NAME             READY   STATUS    RESTARTS   AGE
spire-server-0   2/2     Running   0          157m

What did I miss?

Expected behavior As described in the tutorial:

kubectl get po -n spire-system

# Output:
NAME                          READY   STATUS    RESTARTS      
spire-agent-wdhdh             3/3     Running   0             
spire-server-b594bdfc-szssx   2/2     Running   0             

Evidence N/A

Additional context Running Ubuntu 22.04.4 LTS

Thank you !

[v0lkan]

Hi @LuanaMartelli ; I just saw your report -- I don't know how it slipped.

Thanks for letting us know.

I'll triage it and look into that.

Best,

Volkan.