Change the default nginx/curl app to one that curls automatically

Context

Currently, our default demo app/services setup (nginx server & curl client) requires manual intervention for testing networking: the curl client does not automatically initiate requests. To verify connectivity, users must attach to the container via ctr, which is not ideal for a quick demo or for new users.

This has been a recurring pain point, and I would like to propose a minimal change to improve the out-of-the-box experience.

Proposed Change

Update the default curl service command so that it continuously sends requests to the nginx server, making networking tests automatic and observable via logs. Example configuration:

json
"microserviceID": "",
"microservice_name": "curl",
"microservice_namespace": "test",
"virtualization": "container",
"cmd": [
"sh",
"-c",
"while true; do echo --CURL-START--; curl -s http://10.30.30.30/; sleep 5; done"
]

Rationale

The current curl demo app does not actually perform any curl requests by default.

Users must manually attach to the container to test networking, which is not documented and can be confusing.

Updating the default behavior will make demos more intuitive and better aligned with user expectations.

This change would also bring the CLI and documentation in sync with the actual demo experience.

Related Discussion

The current approach may be a legacy from before we had log monitoring, and it seems the SLA example in the docs is outdated.

There is a similar example in the docs (nginx-client-server-with-load-balancing), but the default app does not reflect this improved behavior.
We can and should use the new upgraded default application for the load-balancing example too.
There is no need for a separate SLA.

Action Items

Update the default curl service configuration to automatically curl the nginx server.

Ensure this behavior is reflected in both the CLI and documentation.

Review and update any related screenshots and guides to match the new default behavior.