[sushant-me]

Fixes #7443.

The problem

Since kubernetes 37.0.0, the mock_k8s_clients fixture hands back the default MagicMock for create_namespaced_job. GkeCodeExecutor._add_owner_reference copies four fields from that Job into a V1OwnerReference:

owner_reference = k8s.client.V1OwnerReference(
    api_version=owner_job.api_version,
    kind=owner_job.kind,
    name=owner_job.metadata.name,
    uid=owner_job.metadata.uid,
)

An unconfigured MagicMock returns a MagicMock for each of those, and kubernetes 37 validates the model with pydantic:

ValidationError: 4 validation errors for V1OwnerReference
  api_version  Input should be a valid string [input_type=MagicMock]

execute_code catches the exception and returns "An unexpected executor error occurred", so five assertions failed and the Unit Tests jobs have been red on main for Python 3.11-3.14 since 51a20e24.

The change

Only the test fixture. It now returns a V1Job with the string fields a real cluster returns:

mock_batch_v1.create_namespaced_job.return_value = client.V1Job(
    api_version="batch/v1",
    kind="Job",
    metadata=client.V1ObjectMeta(name="test-job-name", uid="test-job-uid"),
)

No executor code changes: against a real cluster create_namespaced_job already returns a V1Job with string fields, so the production path was never affected. The failure was the mock being less realistic than the API it stands in for.

Verification

pip install "kubernetes==37.0.0"
pytest tests/unittests/code_executors/test_gke_code_executor.py
  18 passed        (was: 5 failed, 13 passed)

That matches the expected behaviour in the report — all 18 passing as they do on 36.0.3.

I confirmed the failure without the change first (ValidationError ... input_type=MagicMock), so the fix is measured against the real regression rather than assumed.

[sushant-me]

Closing as superseded — current main already carries this fix in tests/unittests/code_executors/test_gke_code_executor.py:

mock_batch_v1.create_namespaced_job.return_value = client.V1Job(
    api_version="batch/v1",
    kind="Job",
    metadata=client.V1ObjectMeta(name="test-job", uid="test-job-uid"),
)

That is the same change this PR made — giving the mocked Job the string fields kubernetes 37's pydantic validation requires — with a different name. There is nothing left to merge.

This PR was part of a four-commit stack (#7446 → #7447 → #7448 → #7450), which is why its diff included the a2a and tools changes. I am untangling that in #7446; the other three commits are all redundant now.