search

draios / instruqt-assets

3 stars 3 forks source link

[instruqt] helm chart upgrade #82

Closed pabloopez closed 1 year ago

pabloopez commented 1 year ago

Multiple changes to update how we deploy the agent with Helm:

TODO: check agent.auditLog.auditServerUrl and agent.auditLog.auditServerPort for our envs

pabloopez commented 1 year ago

This changes were not planned to be applied, but draios/instruqt#460 required to use the new chart.

pabloopez commented 1 year ago

I am not done yet with the tests.

pabloopez commented 1 year ago

Test results:


Configuring Sysdig SECURE API
  Visit https://secure.sysdig.com/#/settings/user to retrieve your Sysdig SECURE API Token.
  Insert here your Sysdig SECURE API Token: 17f43073-96e4-4221-9117-65ac17eaa84d
  Testing connection to API...   OK

Testing if Sysdig Agent is running correctly...
  FAIL
  Agent failed to connect to back-end. Check your Agent Key.

Some errors were detected configuring this lab. Please, run again this script with:
   /usr/bin/bash /root/prepare-track/init.sh

You can ask for help using Intercom or get in touch with us at team-training@sysdig.com
root@controlplane:~# ls /opt/sysdig/
MONITOR_API_ENDPOINT  SECURE_API_ENDPOINT  agent_deploy_date  helm_install.out  user_data_SECURE_API_OK
root@controlplane:~# cat /opt/sysdig/helm_install.out
"sysdig" already exists with the same configuration, skipping
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "sysdig" chart repository
Update Complete. ⎈Happy Helming!⎈
namespace/sysdig-agent created
NAME: sysdig-agent
LAST DEPLOYED: Fri Jan 20 12:09:03 2023
NAMESPACE: sysdig-agent
STATUS: deployed
REVISION: 1
NOTES:
The agent for Sysdig Secure DevOps Platform is spinning up on each node in your
cluster. After a few seconds, you should see your hosts appearing in the
Sysdig Agent Health & Status Dashboard.

Links for your deployment:
  * Sysdig Monitor: https://app.sysdigcloud.com/#/dashboard-template/view.sysdig.agents?last=10
  * Sysdig Secure: https://secure.sysdig.com/#/data-sources/agents
root@controlplane:~# kubectl get pods -n sysdig-agent
NAME                                          READY   STATUS    RESTARTS   AGE
sysdig-agent-kspmcollector-654d94f746-zchqw   1/1     Running   0          8m12s
sysdig-agent-node-analyzer-pv9ck              4/4     Running   0          8m12s
sysdig-agent-node-analyzer-tw5jv              4/4     Running   0          8m12s
sysdig-agent-xvjdw                            1/1     Running   0          8m12s
sysdig-agent-xw25j                            1/1     Running   0          8m12s
root@controlplane:~#
pabloopez commented 1 year ago

TLDR: probably something changed in agent logs that we check to see if the installation was successful.

The changes lgtm, agent is running with the new components. The problem is with our script checks.

pabloopez commented 1 year ago

Summary of the last changes after @pmusa review: this scripts were tested only with us1 region, now it should work with all regions available today.

I tested: us1, us2, us4, eu1, au1 and all are working fine to deploy agents and cloud accounts in aws.

Ready to merge now and be used in draios/instruqt#460.