Migrate away from google.com gcp project k8s-authenticated-test

[spiffxp]

Part of umbrella issue to migrate away from google.com gcp projects: #1469

Part of umbrella to migrate kubernetes e2e test images/registries to community-owned infrastructure: #1458

The registry is used by the following kubernetes e2e tests:

• [sig-apps] ReplicaSet should serve a basic image on each replica with a private image
• [sig-apps] ReplicationController should serve a basic image on each replica with a private image

The k8s-authenticated-test project was accidentally earlier today, and has caused these tests to fail (ref: ref: kubernetes/kubernetes#97002 (comment))

We should:

• ensure the project is restored
• determine what permissions are setup on that project
• determine whether we want to keep the test that references this project at all (ref: Migrate private registry e2e tests away from gcr.io/k8s-authenticated-test kubernetes#97026 (comment))
  • if no, delete this test from all currently supported versions of kubernetes
  • if yes, setup a new project and migrate tests to use it (staging project with custom ACL? custom project?)
• flag project for removal post-deprecation window

[spiffxp]

/wg k8s-infra
/area artifacts
/sig testing
/sig release
/area release-eng

[spiffxp]

For reference, here's the output of gsutil iam get gs://artifacts.k8s-authenticated-test.appspot.com/

{
  "bindings": [
    {
      "members": [
        "projectEditor:k8s-authenticated-test",
        "projectOwner:k8s-authenticated-test"
      ],
      "role": "roles/storage.legacyBucketOwner"
    },
    {
      "members": [
        "allAuthenticatedUsers",
        "projectViewer:k8s-authenticated-test"
      ],
      "role": "roles/storage.legacyBucketReader"
    }
  ],
  "etag": "CAk="
}

To keep the behavior of these tests as-is using a new registry, the key part is allAuthenticatedUsers instead of allUsers.

That said, I question whether we should keep these tests at all, ref: kubernetes/kubernetes#97026 (comment)

[spiffxp]

/miletone v1.21
/sig apps
test owner
/sig node
I think this is a more appropriate test owner for this functionality