OCPBUGS-60833: Fix router access logs container name

[pacevedom]

Which issue(s) this PR addresses:

Closes #

[openshift-ci-robot]

@pacevedom: This pull request references Jira Issue OCPBUGS-60833, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.0) matches configured target version for branch (4.20.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jogeo

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Which issue(s) this PR addresses:

Closes #

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[pacevedom]

/retest

[ShudiLi]

Checked the router container's name and ran OCP-81996 passed

1.
% oc -n openshift-ingress get pods -o=jsonpath="{..spec.containers[*].name}"  
router logs%                                          
2.
passed: (5m6s) 2025-08-28T02:32:35 "[sig-network-edge] Network_Edge Author:shudili-MicroShiftOnly-NonPreRelease-High-81996-capture and log http cookies with specific prefixes via httpCaptureCookies option [Disruptive] [Serial]"

/label qe-approved
thanks

[openshift-ci-robot]

@pacevedom: This pull request references Jira Issue OCPBUGS-60833, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.0) matches configured target version for branch (4.20.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jogeo

Details

In response to this:

Which issue(s) this PR addresses:

Closes #

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[eslutsky]

looks good to me
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eslutsky, pacevedom

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [eslutsky,pacevedom]

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

[eslutsky]

/verified by eslutsky

[openshift-ci-robot]

@eslutsky: This PR has been marked as verified by eslutsky.

Details

In response to this:

/verified by eslutsky

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD d2c8a35 and 2 for PR HEAD 26fb612 in total

[openshift-ci]

@pacevedom: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@pacevedom: Jira Issue OCPBUGS-60833: All pull requests linked via external trackers have merged:

• openshift/microshift#5368

All linked pull requests have the verified tag. Jira Issue OCPBUGS-60833 has been moved to the VERIFIED state.

Details

In response to this:

Which issue(s) this PR addresses:

Closes #

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.