Tests that need to be removed/rewritten to support kops

[upodroid]

Various existing e2e tests are broken when they are ran on clusters that are provisioned by kops. This happens because:

• tests assume a component runs a systemd service when kops deploys it via container
• kubernetes resources have been renamed by upstream component maintainers and kops uses the updated names (an example of this is coredns. CoreDNS deployes kube-dns-autoscaler component with different names but current tests fail as kube-up cluster deploys the addon separately with a different name)
• tests use ssh to run commands on the control plane instance instead of using hostexec(look at Make crictl tests host local #103640 for an explanation)

Broken tests

1. [sig-node] NodeProblemDetector should run without error [sig-node]
   https://testgrid.k8s.io/sig-cluster-lifecycle-kubeup-to-kops#ci-kubernetes-e2e-cos-gce-canary&include-filter-by-regex=NodeProblemDetector
   The pod name that the test check doesnt match Configure COS to use NPD in daemonset mode and align kubeup NPD manifests with the manifests in the NPD repo #121007
2. [sig-autoscaling] DNS horizontal autoscaling kube-dns-autoscaler should scale kube-dns pods in both nonfaulty and faulty scenarios [sig-autoscaling]
   https://testgrid.k8s.io/sig-cluster-lifecycle-kubeup-to-kops#ci-kubernetes-e2e-cos-gce-canary&include-filter-by-regex=kube-dns
   kube-dns-autoscaler Configmap is now called coredns-autoscaler Fix dns autoscaling test to run with coredns #121422

Tests to be removed:

1. [sig-network] Firewall rule should have correct firewall rules for e2e cluster Remove an e2e test specific to kubeup clusters - Part Two #120977
2. [sig-cloud-provider-gcp] Addon update should propagate add-on file changes [Slow] Remove an e2e test specific to kubeup clusters - Part One #120968

Part of kubernetes/enhancements#4224
Part of kubernetes/enhancements#4250

/sig testing
/sig cluster-lifecycle
/triage accepted
/kind bug
/priority important-soon

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[upodroid]

/lifecycle frozen
/triage accepted

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted