feat(container): update image ghcr.io/twin/gatus to v5.15.0

[renovate]

This PR contains the following updates:

Package	Update	Change
ghcr.io/twin/gatus	minor	v5.13.1 -> v5.15.0

---

Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[jsaveker]

Here is an automated review from ChatGPT of this pull request.

From the provided "git diff" snippet, we do not have direct visibility into any deeply rooted security issues purely from the version change in a Helm chart for a monitoring application (Gatus) deployment in Kubernetes. However, I will outline potential areas of concern and general recommendations for maintaining security hygiene in such updates:

Security Considerations:

1. Version Update Security: The update from v5.13.1 to v5.14.0 of the Gatus application does not inherently indicate a security issue. However, it is crucial to review the release notes and any security advisories associated with v5.14.0 to ensure that no new vulnerabilities are introduced and that any security fixes are understood and intentional.

2. Dependencies Security: Ensure that the new version of the software does not introduce any dependencies with known vulnerabilities. This requires checking the security advisories for the dependencies as well.

3. Configuration and Permissions: The snippet does not show any changes to configurations or permissions directly. Still, it's a good practice to verify that the new version does not alter any permissions or configurations in a way that could weaken security, especially when deployed in a Kubernetes environment.

4. Environment Variables: No changes are made to environment variables in this diff. However, always ensure that environment variables, such as TZ and GATUS_CONFIG_PATH, do not inadvertently expose sensitive information or configuration details that could be exploited.

Recommendations:

• Review Release Notes: Before upgrading to a new version, carefully review the release notes of Gatus v5.14.0 to understand what has changed. Pay special attention to any security fixes or known vulnerabilities that are addressed.

  - **Action**: Review Gatus `v5.14.0` release notes with a focus on security fixes and changes.

• Vulnerability Scanning: Use container image scanning tools to scan the new version (ghcr.io/twin/gatus:v5.14.0) for vulnerabilities before rolling it out to production.

  - **Action**: Scan the image `ghcr.io/twin/gatus:v5.14.0` using a tool like Trivy or Clair to identify any vulnerabilities.

• Change Management: Ensure proper change management practices are in place, including testing the new version in a non-production environment, to validate both functionality and security before production deployment.

  - **Action**: Deploy version `v5.14.0` in a staging environment. Conduct thorough testing, including performance and security regression tests.

• Monitoring and Auditing: After deployment, closely monitor the application for any unusual activity and audit logs to quickly identify and respond to potential security issues.

  - **Action**: Utilize Kubernetes monitoring and logging tools to keep an eye on Gatus’ behavior after the update.

Without specific details on the changes introduced in v5.14.0, or the complete setup and context of the Kubernetes deployment, these recommendations serve as a general guide to approach such updates with security in mind.