fix: kong stops responding

[unlair]

kong easily gets overwhelmed when receiving many requests, resulting in an error complaining about not having enough workers. This was due to KONG_NGINX_WORKER_PROCESSES=1 being set. Kong automatically determins the right number of worker processes when this is not specified, which resolves the issue.

What kind of change does this PR introduce?

Bug fix (removing a bad env var for the Kong container).

What is the current behavior?

If many parallel requests are made to the Storage API, Kong will quickly stop responding and start terminating socket connections.

What is the new behavior?

Kong is able to handle many parallel connections without choking.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 94499ee9-703d-4660-b427-efaba939e5c4

📥 Commits

Reviewing files that changed from the base of the PR and between a2916f7 and 7437bd8.

📒 Files selected for processing (1)

• internal/start/start.go

💤 Files with no reviewable changes (1)

• internal/start/start.go

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Removed a fixed worker-process setting from the Kong container environment so it will use the platform's default worker configuration.

Walkthrough

Removed the environment variable KONG_NGINX_WORKER_PROCESSES=1 from the Kong container environment in internal/start/start.go. This single-line deletion modifies the environment passed to the Kong container at startup.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: removing a problematic environment variable that was causing Kong to stop responding under load.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into develop

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coveralls]

Pull Request Test Coverage Report for Build 22877942785

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 7 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.03%) to 61.703%

---

Files with Coverage Reduction	New Missed Lines	%
internal/storage/rm/rm.go	2	80.61%
internal/utils/git.go	5	57.14%

Totals
Change from base Build 22860224621:	-0.03%
Covered Lines:	7716
Relevant Lines:	12505

---

💛 - Coveralls