Tests: Enable default backend access logging tests.

[oyiz-michael]

Enable default backend access logging tests

• Remove Skip calls from two E2E tests for default backend access logging
• Tests were functionally complete but disabled with TODO comments
• Enables validation of enable-access-log-for-default-backend configuration
• Improves test coverage for default backend functionality

This change enhances test coverage without adding new features, aligning with the project's maintenance mode priorities.

What this PR does / why we need it:

This PR enables two E2E tests for default backend access logging that were previously skipped with TODO comments. The tests validate the enable-access-log-for-default-backend configuration option which controls whether nginx logs requests that hit the default backend (404 responses).

Why this is needed:

• These tests were functionally complete but disabled, leaving a gap in test coverage
• The enable-access-log-for-default-backend feature is important for debugging and monitoring
• Enabling these tests ensures the configuration works correctly across nginx reloads
• Improves reliability of default backend functionality without adding new features

The tests validate:

1. Enabling access logging: Requests to non-existent paths are logged when the option is true
2. Disabling access logging: Requests to non-existent paths are not logged when the option is false

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

This addresses a gap in test coverage rather than a specific reported issue. It enables existing tests that were disabled with TODO comments.

How Has This Been Tested?

Local Testing:

• Compilation: go build ./test/e2e/defaultbackend/... passes without errors
• Formatting: gofmt -s -d shows no formatting issues
• Syntax: Go syntax validation passes
• Test Structure: Ginkgo test definitions are properly formatted

Test Validation:

• Verified both test functions are properly defined with ginkgo.It()
• Confirmed test logic is complete and follows E2E testing patterns
• Tests use proper assertions with assert.Contains() and assert.NotContains()
• ConfigMap updates and nginx log checking logic is intact

Changes Made:

- // TODO: fix
- ginkgo.Skip("enable-access-log-for-default-backend")

**Checklist:**
 - [ ] My change requires a change to the documentation.
 - [ ]  I have updated the documentation accordingly.
 - [ ] I've read the CONTRIBUTION guide
 - [ ] I have added unit and/or e2e tests to cover my changes.
 - [x] All new and existing tests passed.

Note: This change enables existing E2E tests rather than adding new ones. The tests were already written and complete, just disabled with Skip calls.

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx canceled.

Name	Link
🔨 Latest commit	184ace6
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-ingress-nginx/deploys/68a128ca4f28d500084a5583

[k8s-ci-robot]

Hi @oyiz-michael. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[oyiz-michael]

/assign

[Gacko]

/triage accepted
/kind cleanup
/priority backlog
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Gacko, oyiz-michael

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Gacko]

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

[Gacko]

/cherry-pick release-1.13

[Gacko]

/cherry-pick release-1.12

[k8s-infra-cherrypick-robot]

@Gacko: once the present PR merges, I will cherry-pick it on top of release-1.13 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.13

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.

[k8s-infra-cherrypick-robot]

@Gacko: once the present PR merges, I will cherry-pick it on top of release-1.12 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.12

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.

[k8s-infra-cherrypick-robot]

@Gacko: new pull request created: #13788

In response to this:

/cherry-pick release-1.13

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.

[k8s-infra-cherrypick-robot]

@Gacko: new pull request created: #13789

In response to this:

/cherry-pick release-1.12

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.

[oyiz-michael]

@Gacko Thank you for the swift reviews, it's been pleasure contributing to this project.