Merge pull request kubernetes#130080 from elizabeth-dev/replace-network-e2e-replicationcontrollers-2

test(network): replace RCs with Deployments in util function StartServeHostnameService

Author: k8s-ci-robot

test/conformance/testdata/conformance.yaml

@@ -1865,9 +1865,9 @@
   description: 'Create a service of type "NodePort" and provide service port and protocol.
     Service''s sessionAffinity is set to "ClientIP". Service creation MUST be successful
     by assigning a "ClusterIP" to the service and allocating NodePort on all the nodes.
-    Create a Replication Controller to ensure that 3 pods are running and are targeted
-    by the service to serve hostname of the pod when requests are sent to the service.
-    Create another pod to make requests to the service. Update the service''s sessionAffinity
+    Create a Deployment to ensure that 3 pods are running and are targeted by the
+    service to serve hostname of the pod when requests are sent to the service. Create
+    another pod to make requests to the service. Update the service''s sessionAffinity
     to "None". Service update MUST be successful. When a requests are made to the
     service on node''s IP and NodePort, service MUST be able serve the hostname from
     any pod of the replica. When service''s sessionAffinily is updated back to "ClientIP",
@@ -1882,15 +1882,15 @@
     service with type clusterIP [LinuxOnly] [Conformance]'
   description: 'Create a service of type "ClusterIP". Service''s sessionAffinity is
     set to "ClientIP". Service creation MUST be successful by assigning "ClusterIP"
-    to the service. Create a Replication Controller to ensure that 3 pods are running
-    and are targeted by the service to serve hostname of the pod when requests are
-    sent to the service. Create another pod to make requests to the service. Update
-    the service''s sessionAffinity to "None". Service update MUST be successful. When
-    a requests are made to the service, it MUST be able serve the hostname from any
-    pod of the replica. When service''s sessionAffinily is updated back to "ClientIP",
-    service MUST serve the hostname from the same pod of the replica for all consecutive
-    requests. Service MUST be reachable over serviceName and the ClusterIP on servicePort.
-    [LinuxOnly]: Windows does not support session affinity.'
+    to the service. Create a Deployment to ensure that 3 pods are running and are
+    targeted by the service to serve hostname of the pod when requests are sent to
+    the service. Create another pod to make requests to the service. Update the service''s
+    sessionAffinity to "None". Service update MUST be successful. When a requests
+    are made to the service, it MUST be able serve the hostname from any pod of the
+    replica. When service''s sessionAffinily is updated back to "ClientIP", service
+    MUST serve the hostname from the same pod of the replica for all consecutive requests.
+    Service MUST be reachable over serviceName and the ClusterIP on servicePort. [LinuxOnly]:
+    Windows does not support session affinity.'
   release: v1.19
   file: test/e2e/network/service.go
 - testname: Service, complete ServiceStatus lifecycle
@@ -1922,24 +1922,24 @@
   description: 'Create a service of type "NodePort" and provide service port and protocol.
     Service''s sessionAffinity is set to "ClientIP". Service creation MUST be successful
     by assigning a "ClusterIP" to service and allocating NodePort on all nodes. Create
-    a Replication Controller to ensure that 3 pods are running and are targeted by
-    the service to serve hostname of the pod when a requests are sent to the service.
-    Create another pod to make requests to the service on node''s IP and NodePort.
-    Service MUST serve the hostname from the same pod of the replica for all consecutive
-    requests. Service MUST be reachable over serviceName and the ClusterIP on servicePort.
-    Service MUST also be reachable over node''s IP on NodePort. [LinuxOnly]: Windows
-    does not support session affinity.'
+    a Deployment to ensure that 3 pods are running and are targeted by the service
+    to serve hostname of the pod when a requests are sent to the service. Create another
+    pod to make requests to the service on node''s IP and NodePort. Service MUST serve
+    the hostname from the same pod of the replica for all consecutive requests. Service
+    MUST be reachable over serviceName and the ClusterIP on servicePort. Service MUST
+    also be reachable over node''s IP on NodePort. [LinuxOnly]: Windows does not support
+    session affinity.'
   release: v1.19
   file: test/e2e/network/service.go
 - testname: Service, ClusterIP type, session affinity to ClientIP
   codename: '[sig-network] Services should have session affinity work for service
     with type clusterIP [LinuxOnly] [Conformance]'
   description: 'Create a service of type "ClusterIP". Service''s sessionAffinity is
     set to "ClientIP". Service creation MUST be successful by assigning "ClusterIP"
-    to the service. Create a Replication Controller to ensure that 3 pods are running
-    and are targeted by the service to serve hostname of the pod when requests are
-    sent to the service. Create another pod to make requests to the service. Service
-    MUST serve the hostname from the same pod of the replica for all consecutive requests.
+    to the service. Create a Deployment to ensure that 3 pods are running and are
+    targeted by the service to serve hostname of the pod when requests are sent to
+    the service. Create another pod to make requests to the service. Service MUST
+    serve the hostname from the same pod of the replica for all consecutive requests.
     Service MUST be reachable over serviceName and the ClusterIP on servicePort. [LinuxOnly]:
     Windows does not support session affinity.'
   release: v1.19