Fix env var conflict issues with fake-gcs-server

[anveshreddy18]

How to categorize this PR?

/area usability
/kind bug

What this PR does / why we need it:

This PR changes the fake-gcs service name to fake-gcs-service to avoid conflicts with k8s injected env var FAKE_GCS_PORT that sets it to tcp://PodIP:4443 as it constructs this env var from the service name, The specific FAKE_GCS_PORT is important as the fsouza/fake-gcs-server refers to this env variable which resulted in the following error in the container:

2026/02/25 06:32:48 invalid value for environment variable FAKE_GCS_PORT="tcp://10.96.89.231:4443": strconv.ParseUint: parsing "tcp://10.96.89.231:4443": invalid syntax
stream closed EOF for default/fake-gcs-7d96b5f4b5-wb2d6 (fake-gcs-server)

Changing the service name to fake-gcs-service fixes this as it no longer conflicts with the k8s ways of adding env vars for endpoints.

Which issue(s) this PR fixes:
Fixes #

Checklist:

• Update documentation in the /docs folder (if applicable)
  • If new files added to docs, or docs structure modified:
    • Update mkdocs.yml. Follow Updating Documentation guide to test the changes locally.
    • Update Table of Contents for the docs.
• Add tests that cover your changes (if applicable)
  • Unit tests
  • Integration tests
  • E2E tests

Special notes for your reviewer:

Release note:

fix env var conflict issues with fake-gcs-server container setup.

[CaptainIRS]

Could we instead just set enableServiceLinks to false in the fake-gcs deployment's pod spec since this is just a fsouza/fake-gcs-server-specific thing? I believe that one change should be sufficient to get this to work.

[anveshreddy18]

Thanks @CaptainIRS for the review, I did that originally and it worked, there is another way of explicitly setting FAKE_GCS_PORT to 4443 as well which also solves the problem, I tried both but they are essentially bandages to the root cause, and such issues can occur again if we don't solve the actual root of the issue which is the conflicting env var stemming from service name, so I instead chose to do that so we can solve it once and for all.

[CaptainIRS]

Sounds good, thanks for the explanation!

[gardener-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: CaptainIRS
Once this PR has been reviewed and has the lgtm label, please assign shreyas-s-rao 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:

• OWNERS

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

[gardener-prow]

LGTM label has been added.

Details

Git tree hash: 2f361d08babf87ffc13580be93575e7d8e1656f8

[anveshreddy18]

@ishan16696 can you take a look at this PR for approval ? Thanks