Fix multinode-HA guide test failure on TLS package deploy

[Copilot]

The main / test GitHub Actions job was failing in the examples/operations/multinode-HA guide during the TLS-secured application deploy step. The HTTPS config server upload path was using a streamed zip payload that failed before activation completed.

• Root cause

  • The guide deployed the application package with a streamed archive:

    zip -r - ... | curl --data-binary @- https://localhost:19071/application/v2/tenant/default/prepareandactivate

  • In CI, that TLS upload path failed during the curl request, so the guide test never observed prepared and activated.

• Change

  • Update the TLS deploy example in examples/operations/multinode-HA/README.md to create the application package as a real zip file under /tmp and upload that file directly.
  • This keeps the guide flow unchanged while avoiding the failing streamed upload path.

• Guide update

  zip -r /tmp/multinode-ha-app.zip . -x "tls/*" "pki/*" "scripts/*" "gke/*" "img/*" README.md .gitignore services.xml.open "*.yaml"
  curl \
    --key pki/vespa/host.key --cert pki/vespa/host.pem --cacert pki/vespa/ca-vespa.pem \
    --header Content-Type:application/zip --data-binary @/tmp/multinode-ha-app.zip \
    https://localhost:19071/application/v2/tenant/default/prepareandactivate

[Copilot]

Copilot review overview

🟢 Approval recommended

The focused documentation change directly addresses the reported CI failure without altering the deployment flow.

Review effort: Balanced
Findings: None

What changed in this PR

Updates the multinode HA guide’s TLS deployment flow to avoid unreliable streamed uploads.

Changes:

• Creates the application package as a temporary ZIP file.
• Uploads the ZIP directly with curl.

File	Description
examples/​operations/​multinode-HA/​README.md	Revises the TLS deployment commands to use a file-backed ZIP upload.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.