LCORE-2310: Adding explicit TLS output checks

[asimurka]

Description

Fixes bug in tls e2e mock server that was previously returning empty response. This was not previously caught by e2e tests. This PR adds explicit check for the LLM response.

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up service version
• Bump-up dependent library
• Bump-up library or tool used for development (does not change the final image)
• CI configuration change
• Konflux configuration change
• Unit tests improvement
• Integration tests improvement
• End to end tests improvement
• Benchmarks improvement

Tools used to create PR

Identify any AI code assistants used in this PR (for transparency and review context)

• Assisted-by: Cursor

Related Tickets & Documents

• Related Issue # https://redhat.atlassian.net/browse/LCORE-2310
• Closes #

Checklist before requesting a review

• I have performed a self-review of my code.
• PR has passed all pre-merge test jobs.
• If it is a core feature, I have added thorough tests.

Testing

• Please provide detailed steps to perform tests related to this code change.
• How were the fix/results from this change verified? Please provide relevant screenshots or results.

Summary by CodeRabbit

• Tests
  • Enhanced TLS end-to-end test scenarios to validate successful response content across TLS verification configurations, including CA certificate verification, mutual TLS authentication, and TLSv1.3 minimum version validation.

[coderabbitai]

Walkthrough

Adds SSE stream support and a shared response text in the mock TLS inference server; updates four TLS end-to-end test success scenarios to assert responses contain the mock server greeting "Hello from the TLS mock inference server".

Changes

TLS E2E Response Body Validation

Layer / File(s)	Summary
Mock TLS inference server: streaming and shared response text tests/e2e/mock_tls_inference_server/server.py	Adds shared completion_id/response_text, supports stream=true by emitting SSE chat.completion.chunk events and [DONE], and uses response_text for non-stream replies.
Response body assertions in TLS success scenarios tests/e2e/features/tls.feature	Four TLS success scenarios (TLS verification disabled, CA cert verification, mutual TLS auth, TLS minimum version TLSv1.3) now assert the HTTP 200 response body contains "Hello from the TLS mock inference server".

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'LCORE-2310: Adding explicit TLS output checks' clearly summarizes the main changes: adding explicit assertions for TLS output in the e2e tests and supporting streaming responses in the mock TLS inference server.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

✨ Simplify code

• Create PR with simplified code

---

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.}

[tisnik]

LGTM

[jrobertboos]

LGTM