Skip to content

Inject session identity header for session replay requests #504

Open
pavanipenumalla wants to merge 1 commit into
kubernetes-sigs:mainfrom
pavanipenumalla:otel-replay
Open

Inject session identity header for session replay requests #504
pavanipenumalla wants to merge 1 commit into
kubernetes-sigs:mainfrom
pavanipenumalla:otel-replay

Conversation

@pavanipenumalla
Copy link
Copy Markdown

@pavanipenumalla pavanipenumalla commented May 22, 2026

  • Added configurable session_id_header_key to SessionReplayConfig
  • Added session_id_header_key field to InferenceAPIData as a carrier for the client
  • Stamped session_id_header_key onto each request in load_generator
  • Propagated session_id_header_key during data materialization in datagen/base.py
  • Injected session_id as an HTTP header in openai_client when session_id_header_key is set
  • Updated example configs with session_id_header_key usage
  • Added unit tests verifying header injection and skip behavior

Resolves #492

@k8s-ci-robot k8s-ci-robot added the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label May 22, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented May 22, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pavanipenumalla
Once this PR has been reviewed and has the lgtm label, please assign sergeykanzhelev for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@linux-foundation-easycla
Copy link
Copy Markdown

linux-foundation-easycla Bot commented May 22, 2026 •
edited
Loading

CLA Not Signed

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented May 22, 2026

Welcome @pavanipenumalla!

It looks like this is your first PR to kubernetes-sigs/inference-perf 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/inference-perf has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 22, 2026
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels May 22, 2026
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label May 22, 2026
@pavanipenumalla
Copy link
Copy Markdown
Author

pavanipenumalla commented May 22, 2026

I have mistakenly signed the CLA as an Individual contributor instead of corporate CLA. While I figure this out to transition from ICLA to CCLA, I would be happy to hear the feedback on this PR. Thank you!

@jarias-lfx
Copy link
Copy Markdown

jarias-lfx commented May 25, 2026

/easycla

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. and removed cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 25, 2026
@pavanipenumalla
feat: inject session identity header for session replay requests
8e6feca 
- Added configurable session_id_header_key to SessionReplayConfig
- Added session_id_header_key field to InferenceAPIData as a carrier for the client
- Stamped session_id_header_key onto each request in load_generator
- Propagated session_id_header_key during data materialization in datagen/base.py
- Injected session_id as an HTTP header in openai_client when session_id_header_key is set
- Updated example configs with session_id_header_key usage
- Added unit tests verifying header injection and skip behavior

Signed-off-by: Pavani Penumalla <pavanipenumalla0@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Bslabe123 Bslabe123 Awaiting requested review from Bslabe123

@SachinVarghese SachinVarghese Awaiting requested review from SachinVarghese

Assignees

No one assigned

Labels

cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Inject session identity header for session replay requests

3 participants

@pavanipenumalla @k8s-ci-robot @jarias-lfx