This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 7 succeeded
Started2022-09-21 11:02
Elapsed1h15m
Revisionmain

No Test Failures!


Show 7 Passed Tests

Show 20 Skipped Tests

Error lines from build-log.txt

... skipping 768 lines ...
+ retVal=0
++ docker images -q kindest/node:v1.22.14
+ [[ '' == '' ]]
+ echo '+ Pulling kindest/node:v1.22.14'
+ Pulling kindest/node:v1.22.14
+ docker pull kindest/node:v1.22.14
Error response from daemon: manifest for kindest/node:v1.22.14 not found: manifest unknown: manifest unknown
+ retVal=1
+ [[ 1 != 0 ]]
+ echo '+ image for Kuberentes v1.22.14 is not available in docker hub, trying local build'
+ image for Kuberentes v1.22.14 is not available in docker hub, trying local build
+ kind::buildNodeImage v1.22.14
+ local version=v1.22.14
... skipping 196 lines ...
Status: Downloaded newer image for quay.io/jetstack/cert-manager-controller:v1.9.1
quay.io/jetstack/cert-manager-controller:v1.9.1
+ export GINKGO_NODES=3
+ GINKGO_NODES=3
+ export GINKGO_NOCOLOR=true
+ GINKGO_NOCOLOR=true
+ export GINKGO_ARGS=--fail-fast
+ GINKGO_ARGS=--fail-fast
+ export E2E_CONF_FILE=/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/config/docker.yaml
+ E2E_CONF_FILE=/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/config/docker.yaml
+ export ARTIFACTS=/logs/artifacts
+ ARTIFACTS=/logs/artifacts
+ export SKIP_RESOURCE_CLEANUP=false
+ SKIP_RESOURCE_CLEANUP=false
... skipping 78 lines ...
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-kcp-scale-in --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-kcp-scale-in.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-ipv6 --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-ipv6.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-topology --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-topology.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-ignition --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-ignition.yaml
mkdir -p /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/test-extension
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/extension/config/default > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/test-extension/deployment.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/ginkgo-v2.1.4 -v --trace --tags=e2e --focus="\[K8s-Upgrade\]"  --nodes=3 --no-color=true --output-dir="/logs/artifacts" --junit-report="junit.e2e_suite.1.xml" --fail-fast . -- \
    -e2e.artifacts-folder="/logs/artifacts" \
    -e2e.config="/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/config/docker.yaml" \
    -e2e.skip-resource-cleanup=false -e2e.use-existing-cluster=false
go: downloading k8s.io/apimachinery v0.25.0
go: downloading k8s.io/api v0.25.0
go: downloading github.com/blang/semver v3.5.1+incompatible
... skipping 228 lines ...
    kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-and-conformance-op826y-mp-0-config created
    kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-and-conformance-op826y-mp-0-config-cgroupfs created
    cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-op826y created
    machinepool.cluster.x-k8s.io/k8s-upgrade-and-conformance-op826y-mp-0 created
    dockermachinepool.infrastructure.cluster.x-k8s.io/k8s-upgrade-and-conformance-op826y-dmp-0 created

    Failed to get logs for Machine k8s-upgrade-and-conformance-op826y-8r46f-qkhlp, Cluster k8s-upgrade-and-conformance-w1mafc/k8s-upgrade-and-conformance-op826y: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-op826y-md-0-m2lf7-66b8cf447f-l57ll, Cluster k8s-upgrade-and-conformance-w1mafc/k8s-upgrade-and-conformance-op826y: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-op826y-md-0-m2lf7-66b8cf447f-m2c2f, Cluster k8s-upgrade-and-conformance-w1mafc/k8s-upgrade-and-conformance-op826y: exit status 2
    Failed to get logs for MachinePool k8s-upgrade-and-conformance-op826y-mp-0, Cluster k8s-upgrade-and-conformance-w1mafc/k8s-upgrade-and-conformance-op826y: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec 09/21/22 11:19:30.006
    INFO: Creating namespace k8s-upgrade-and-conformance-w1mafc
    INFO: Creating event watcher for namespace "k8s-upgrade-and-conformance-w1mafc"
... skipping 78 lines ...
    Sep 21 11:26:32.743: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating configMap with name configmap-test-volume-ac013872-bdbb-4ac0-9f74-77129a692275
    STEP: Creating a pod to test consume configMaps
    Sep 21 11:26:32.764: INFO: Waiting up to 5m0s for pod "pod-configmaps-c20f54e0-2326-463b-a663-813d24b09848" in namespace "configmap-5527" to be "Succeeded or Failed"

    Sep 21 11:26:32.768: INFO: Pod "pod-configmaps-c20f54e0-2326-463b-a663-813d24b09848": Phase="Pending", Reason="", readiness=false. Elapsed: 3.474061ms
    Sep 21 11:26:34.771: INFO: Pod "pod-configmaps-c20f54e0-2326-463b-a663-813d24b09848": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006588626s
    Sep 21 11:26:36.866: INFO: Pod "pod-configmaps-c20f54e0-2326-463b-a663-813d24b09848": Phase="Running", Reason="", readiness=true. Elapsed: 4.102151726s
    Sep 21 11:26:38.871: INFO: Pod "pod-configmaps-c20f54e0-2326-463b-a663-813d24b09848": Phase="Running", Reason="", readiness=false. Elapsed: 6.107040431s
    Sep 21 11:26:40.875: INFO: Pod "pod-configmaps-c20f54e0-2326-463b-a663-813d24b09848": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.111098214s
    STEP: Saw pod success
    Sep 21 11:26:40.875: INFO: Pod "pod-configmaps-c20f54e0-2326-463b-a663-813d24b09848" satisfied condition "Succeeded or Failed"

    Sep 21 11:26:40.879: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod pod-configmaps-c20f54e0-2326-463b-a663-813d24b09848 container agnhost-container: <nil>
    STEP: delete the pod
    Sep 21 11:26:40.909: INFO: Waiting for pod pod-configmaps-c20f54e0-2326-463b-a663-813d24b09848 to disappear
    Sep 21 11:26:40.912: INFO: Pod pod-configmaps-c20f54e0-2326-463b-a663-813d24b09848 no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:26:40.912: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-5527" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":21,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Aggregator
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 24 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:26:44.977: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "aggregator-8614" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Aggregator Should be able to support the 1.17 Sample API Server using the current Aggregator [Conformance]","total":-1,"completed":1,"skipped":32,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:26:47.908: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-231" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should update labels on modification [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":26,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 22 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:26:49.081: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-1339" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should verify ResourceQuota with best effort scope. [Conformance]","total":-1,"completed":1,"skipped":8,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 15 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:26:54.980: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-9961" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should adopt matching pods on creation [Conformance]","total":-1,"completed":3,"skipped":30,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 10 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:26:56.196: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "init-container-9399" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] InitContainer [NodeConformance] should invoke init containers on a RestartNever pod [Conformance]","total":-1,"completed":2,"skipped":32,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 113 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:26:57.502: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-636" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment should run the lifecycle of a Deployment [Conformance]","total":-1,"completed":2,"skipped":39,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 45 lines ...
    STEP: Destroying namespace "services-2667" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]","total":-1,"completed":4,"skipped":41,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-auth] ServiceAccounts
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 25 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:10.866: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svcaccounts-6139" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] ServiceAccounts should allow opting out of API token automount  [Conformance]","total":-1,"completed":5,"skipped":62,"failed":0}

    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:27:10.895: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 22 lines ...
    STEP: Destroying namespace "webhook-420-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]","total":-1,"completed":6,"skipped":62,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] StatefulSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 25 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:17.724: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-1908" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should have a working scale subresource [Conformance]","total":-1,"completed":3,"skipped":78,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:27:14.874: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable in multiple volumes in a pod [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating secret with name secret-test-1784b8c7-34ea-4bb4-bb2d-01f5d9e72073
    STEP: Creating a pod to test consume secrets
    Sep 21 11:27:14.953: INFO: Waiting up to 5m0s for pod "pod-secrets-48dd433f-a3d5-4b3f-a657-0fb90d106945" in namespace "secrets-5969" to be "Succeeded or Failed"

    Sep 21 11:27:14.957: INFO: Pod "pod-secrets-48dd433f-a3d5-4b3f-a657-0fb90d106945": Phase="Pending", Reason="", readiness=false. Elapsed: 4.757915ms
    Sep 21 11:27:16.962: INFO: Pod "pod-secrets-48dd433f-a3d5-4b3f-a657-0fb90d106945": Phase="Pending", Reason="", readiness=false. Elapsed: 2.009389594s
    Sep 21 11:27:18.984: INFO: Pod "pod-secrets-48dd433f-a3d5-4b3f-a657-0fb90d106945": Phase="Pending", Reason="", readiness=false. Elapsed: 4.031746567s
    Sep 21 11:27:20.991: INFO: Pod "pod-secrets-48dd433f-a3d5-4b3f-a657-0fb90d106945": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.038219184s
    STEP: Saw pod success
    Sep 21 11:27:20.991: INFO: Pod "pod-secrets-48dd433f-a3d5-4b3f-a657-0fb90d106945" satisfied condition "Succeeded or Failed"

    Sep 21 11:27:20.995: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod pod-secrets-48dd433f-a3d5-4b3f-a657-0fb90d106945 container secret-volume-test: <nil>
    STEP: delete the pod
    Sep 21 11:27:21.017: INFO: Waiting for pod pod-secrets-48dd433f-a3d5-4b3f-a657-0fb90d106945 to disappear
    Sep 21 11:27:21.021: INFO: Pod pod-secrets-48dd433f-a3d5-4b3f-a657-0fb90d106945 no longer exists
    [AfterEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:21.021: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-5969" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be consumable in multiple volumes in a pod [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":86,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Events
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 17 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:25.893: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-327" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Events should be sent by kubelets and the scheduler about pods scheduling and running  [Conformance]","total":-1,"completed":4,"skipped":80,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Job
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:31.281: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "job-642" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Job should delete a job [Conformance]","total":-1,"completed":3,"skipped":106,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:27:31.316: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] volume on tmpfs should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test emptydir volume type on tmpfs
    Sep 21 11:27:31.354: INFO: Waiting up to 5m0s for pod "pod-20a972e0-9ea8-4d50-a35a-354191e92dc2" in namespace "emptydir-928" to be "Succeeded or Failed"

    Sep 21 11:27:31.357: INFO: Pod "pod-20a972e0-9ea8-4d50-a35a-354191e92dc2": Phase="Pending", Reason="", readiness=false. Elapsed: 3.367348ms
    Sep 21 11:27:33.362: INFO: Pod "pod-20a972e0-9ea8-4d50-a35a-354191e92dc2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007585601s
    Sep 21 11:27:35.366: INFO: Pod "pod-20a972e0-9ea8-4d50-a35a-354191e92dc2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.01195611s
    STEP: Saw pod success
    Sep 21 11:27:35.366: INFO: Pod "pod-20a972e0-9ea8-4d50-a35a-354191e92dc2" satisfied condition "Succeeded or Failed"

    Sep 21 11:27:35.369: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-md-0-m2lf7-66b8cf447f-l57ll pod pod-20a972e0-9ea8-4d50-a35a-354191e92dc2 container test-container: <nil>
    STEP: delete the pod
    Sep 21 11:27:35.391: INFO: Waiting for pod pod-20a972e0-9ea8-4d50-a35a-354191e92dc2 to disappear
    Sep 21 11:27:35.393: INFO: Pod pod-20a972e0-9ea8-4d50-a35a-354191e92dc2 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:35.393: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-928" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes volume on tmpfs should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":121,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-scheduling] LimitRange
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 32 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:42.553: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "limitrange-4601" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-scheduling] LimitRange should create a LimitRange with defaults and ensure pod has those defaults applied. [Conformance]","total":-1,"completed":5,"skipped":160,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 14 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:43.199: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-probe-8029" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Probing container should be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]","total":-1,"completed":8,"skipped":103,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] StatefulSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 103 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:44.989: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-9279" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Scaling should happen in predictable order and halt if any stateful pod is unhealthy [Slow] [Conformance]","total":-1,"completed":1,"skipped":33,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:49.878: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-360" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should update annotations on modification [NodeConformance] [Conformance]","total":-1,"completed":9,"skipped":119,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/storage/projected_downwardapi.go:41
    [It] should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test downward API volume plugin
    Sep 21 11:27:45.042: INFO: Waiting up to 5m0s for pod "downwardapi-volume-ba1db9f2-214d-4ae7-876c-687947594078" in namespace "projected-9390" to be "Succeeded or Failed"

    Sep 21 11:27:45.048: INFO: Pod "downwardapi-volume-ba1db9f2-214d-4ae7-876c-687947594078": Phase="Pending", Reason="", readiness=false. Elapsed: 5.984453ms
    Sep 21 11:27:47.053: INFO: Pod "downwardapi-volume-ba1db9f2-214d-4ae7-876c-687947594078": Phase="Running", Reason="", readiness=true. Elapsed: 2.01025s
    Sep 21 11:27:49.060: INFO: Pod "downwardapi-volume-ba1db9f2-214d-4ae7-876c-687947594078": Phase="Running", Reason="", readiness=false. Elapsed: 4.017934756s
    Sep 21 11:27:51.064: INFO: Pod "downwardapi-volume-ba1db9f2-214d-4ae7-876c-687947594078": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.02201299s
    STEP: Saw pod success
    Sep 21 11:27:51.064: INFO: Pod "downwardapi-volume-ba1db9f2-214d-4ae7-876c-687947594078" satisfied condition "Succeeded or Failed"

    Sep 21 11:27:51.068: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod downwardapi-volume-ba1db9f2-214d-4ae7-876c-687947594078 container client-container: <nil>
    STEP: delete the pod
    Sep 21 11:27:51.082: INFO: Waiting for pod downwardapi-volume-ba1db9f2-214d-4ae7-876c-687947594078 to disappear
    Sep 21 11:27:51.084: INFO: Pod downwardapi-volume-ba1db9f2-214d-4ae7-876c-687947594078 no longer exists
    [AfterEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:51.084: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-9390" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":34,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 25 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:51.984: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-4838" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment Deployment should have a working scale subresource [Conformance]","total":-1,"completed":10,"skipped":124,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:27:56.160: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-5077" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes pod should support shared volumes between containers [Conformance]","total":-1,"completed":11,"skipped":139,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] StatefulSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 23 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:28:16.289: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-8186" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should list, patch and delete a collection of StatefulSets [Conformance]","total":-1,"completed":12,"skipped":150,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 21 lines ...
    STEP: Destroying namespace "crd-webhook-9910" for this suite.
    [AfterEach] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/crd_conversion_webhook.go:137
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]","total":-1,"completed":13,"skipped":166,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-node] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 8 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:28:25.982: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-probe-8419" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Probing container with readiness probe that fails should never be ready and never restart [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":105,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:28:25.996: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable via the environment [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating configMap configmap-7271/configmap-test-ce1b45a0-11cc-4bad-a568-915eb6ae28f8
    STEP: Creating a pod to test consume configMaps
    Sep 21 11:28:26.031: INFO: Waiting up to 5m0s for pod "pod-configmaps-be96b6e6-2458-4ee6-8bab-9c98021bc027" in namespace "configmap-7271" to be "Succeeded or Failed"

    Sep 21 11:28:26.034: INFO: Pod "pod-configmaps-be96b6e6-2458-4ee6-8bab-9c98021bc027": Phase="Pending", Reason="", readiness=false. Elapsed: 2.516252ms
    Sep 21 11:28:28.037: INFO: Pod "pod-configmaps-be96b6e6-2458-4ee6-8bab-9c98021bc027": Phase="Pending", Reason="", readiness=false. Elapsed: 2.005914507s
    Sep 21 11:28:30.042: INFO: Pod "pod-configmaps-be96b6e6-2458-4ee6-8bab-9c98021bc027": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.01086007s
    STEP: Saw pod success
    Sep 21 11:28:30.042: INFO: Pod "pod-configmaps-be96b6e6-2458-4ee6-8bab-9c98021bc027" satisfied condition "Succeeded or Failed"

    Sep 21 11:28:30.045: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod pod-configmaps-be96b6e6-2458-4ee6-8bab-9c98021bc027 container env-test: <nil>
    STEP: delete the pod
    Sep 21 11:28:30.062: INFO: Waiting for pod pod-configmaps-be96b6e6-2458-4ee6-8bab-9c98021bc027 to disappear
    Sep 21 11:28:30.066: INFO: Pod pod-configmaps-be96b6e6-2458-4ee6-8bab-9c98021bc027 no longer exists
    [AfterEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:28:30.066: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-7271" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] ConfigMap should be consumable via the environment [NodeConformance] [Conformance]","total":-1,"completed":6,"skipped":109,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:28:30.102: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (non-root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test emptydir 0644 on node default medium
    Sep 21 11:28:30.143: INFO: Waiting up to 5m0s for pod "pod-a6efbf15-45fe-45ae-81dc-3af7566639f4" in namespace "emptydir-4778" to be "Succeeded or Failed"

    Sep 21 11:28:30.146: INFO: Pod "pod-a6efbf15-45fe-45ae-81dc-3af7566639f4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.968738ms
    Sep 21 11:28:32.150: INFO: Pod "pod-a6efbf15-45fe-45ae-81dc-3af7566639f4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007386691s
    Sep 21 11:28:34.155: INFO: Pod "pod-a6efbf15-45fe-45ae-81dc-3af7566639f4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012161195s
    STEP: Saw pod success
    Sep 21 11:28:34.155: INFO: Pod "pod-a6efbf15-45fe-45ae-81dc-3af7566639f4" satisfied condition "Succeeded or Failed"

    Sep 21 11:28:34.157: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-md-0-m2lf7-66b8cf447f-l57ll pod pod-a6efbf15-45fe-45ae-81dc-3af7566639f4 container test-container: <nil>
    STEP: delete the pod
    Sep 21 11:28:34.173: INFO: Waiting for pod pod-a6efbf15-45fe-45ae-81dc-3af7566639f4 to disappear
    Sep 21 11:28:34.175: INFO: Pod pod-a6efbf15-45fe-45ae-81dc-3af7566639f4 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:28:34.175: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-4778" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":125,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 3 lines ...
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:752
    [It] should serve a basic endpoint from pods  [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: creating service endpoint-test2 in namespace services-8293
    STEP: waiting up to 3m0s for service endpoint-test2 in namespace services-8293 to expose endpoints map[]
    Sep 21 11:28:23.354: INFO: Failed go get Endpoints object: endpoints "endpoint-test2" not found

    Sep 21 11:28:24.364: INFO: successfully validated that service endpoint-test2 in namespace services-8293 exposes endpoints map[]
    STEP: Creating pod pod1 in namespace services-8293
    Sep 21 11:28:24.379: INFO: The status of Pod pod1 is Pending, waiting for it to be Running (with Ready = true)
    Sep 21 11:28:26.383: INFO: The status of Pod pod1 is Running (Ready = true)
    STEP: waiting up to 3m0s for service endpoint-test2 in namespace services-8293 to expose endpoints map[pod1:[80]]
    Sep 21 11:28:26.394: INFO: successfully validated that service endpoint-test2 in namespace services-8293 exposes endpoints map[pod1:[80]]
... skipping 36 lines ...
    STEP: Destroying namespace "services-8293" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should serve a basic endpoint from pods  [Conformance]","total":-1,"completed":14,"skipped":169,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] DisruptionController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:28:38.272: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "disruption-5044" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] DisruptionController should observe PodDisruptionBudget status updated [Conformance]","total":-1,"completed":8,"skipped":128,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 16 lines ...
    STEP: Registering the custom resource webhook via the AdmissionRegistration API
    Sep 21 11:28:05.340: INFO: Waiting for webhook configuration to be ready...
    Sep 21 11:28:15.451: INFO: Waiting for webhook configuration to be ready...
    Sep 21 11:28:25.553: INFO: Waiting for webhook configuration to be ready...
    Sep 21 11:28:35.651: INFO: Waiting for webhook configuration to be ready...
    Sep 21 11:28:45.660: INFO: Waiting for webhook configuration to be ready...
    Sep 21 11:28:45.660: FAIL: waiting for webhook configuration to be ready

    Unexpected error:

        <*errors.errorString | 0xc000248290>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 23 lines ...
    [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should be able to deny custom resource creation, update and deletion [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
      Sep 21 11:28:45.660: waiting for webhook configuration to be ready
      Unexpected error:

          <*errors.errorString | 0xc000248290>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:1749
    ------------------------------
    {"msg":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]","total":-1,"completed":2,"skipped":54,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:28:46.226: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 24 lines ...
    STEP: Destroying namespace "webhook-7301-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]","total":-1,"completed":3,"skipped":54,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] RuntimeClass
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 19 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:28:53.140: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "runtimeclass-6784" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] RuntimeClass  should support RuntimeClasses API operations [Conformance]","total":-1,"completed":4,"skipped":79,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:28:57.295: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-118" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":127,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] EndpointSlice
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 8 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:28:57.395: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "endpointslice-7136" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified [Conformance]","total":-1,"completed":6,"skipped":137,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 16 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:29:02.525: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-4331" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should be submitted and removed [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":141,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] PodTemplates
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 15 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:29:02.658: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "podtemplate-5847" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] PodTemplates should delete a collection of pod templates [Conformance]","total":-1,"completed":8,"skipped":179,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 14 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:29:05.736: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-4264" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should surface a failure condition on a common issue like exceeded quota [Conformance]","total":-1,"completed":9,"skipped":185,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Discovery
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 85 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:29:06.097: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "discovery-9443" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Discovery should validate PreferredVersion for each APIGroup [Conformance]","total":-1,"completed":10,"skipped":189,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:29:06.108: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename kubectl
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 17 lines ...
    Sep 21 11:29:09.308: INFO: ForEach: Found 1 pods from the filter.  Now looping through them.
    Sep 21 11:29:09.308: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-4927 describe pod agnhost-primary-9hgm8'
    Sep 21 11:29:09.398: INFO: stderr: ""
    Sep 21 11:29:09.398: INFO: stdout: "Name:         agnhost-primary-9hgm8\nNamespace:    kubectl-4927\nPriority:     0\nNode:         k8s-upgrade-and-conformance-op826y-md-0-m2lf7-66b8cf447f-l57ll/172.18.0.4\nStart Time:   Wed, 21 Sep 2022 11:29:07 +0000\nLabels:       app=agnhost\n              role=primary\nAnnotations:  <none>\nStatus:       Running\nIP:           192.168.0.15\nIPs:\n  IP:           192.168.0.15\nControlled By:  ReplicationController/agnhost-primary\nContainers:\n  agnhost-primary:\n    Container ID:   containerd://06f9939d90d2238c79e43ee4893d9fa16d4058e965ae651f68b24a0fec56001f\n    Image:          k8s.gcr.io/e2e-test-images/agnhost:2.39\n    Image ID:       k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e\n    Port:           6379/TCP\n    Host Port:      0/TCP\n    State:          Running\n      Started:      Wed, 21 Sep 2022 11:29:07 +0000\n    Ready:          True\n    Restart Count:  0\n    Environment:    <none>\n    Mounts:\n      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-tztws (ro)\nConditions:\n  Type              Status\n  Initialized       True \n  Ready             True \n  ContainersReady   True \n  PodScheduled      True \nVolumes:\n  kube-api-access-tztws:\n    Type:                    Projected (a volume that contains injected data from multiple sources)\n    TokenExpirationSeconds:  3607\n    ConfigMapName:           kube-root-ca.crt\n    ConfigMapOptional:       <nil>\n    DownwardAPI:             true\nQoS Class:                   BestEffort\nNode-Selectors:              <none>\nTolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s\n                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s\nEvents:\n  Type    Reason     Age   From               Message\n  ----    ------     ----  ----               -------\n  Normal  Scheduled  2s    default-scheduler  Successfully assigned kubectl-4927/agnhost-primary-9hgm8 to k8s-upgrade-and-conformance-op826y-md-0-m2lf7-66b8cf447f-l57ll\n  Normal  Pulled     2s    kubelet            Container image \"k8s.gcr.io/e2e-test-images/agnhost:2.39\" already present on machine\n  Normal  Created    2s    kubelet            Created container agnhost-primary\n  Normal  Started    2s    kubelet            Started container agnhost-primary\n"
    Sep 21 11:29:09.398: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-4927 describe rc agnhost-primary'
    Sep 21 11:29:09.504: INFO: stderr: ""
    Sep 21 11:29:09.504: INFO: stdout: "Name:         agnhost-primary\nNamespace:    kubectl-4927\nSelector:     app=agnhost,role=primary\nLabels:       app=agnhost\n              role=primary\nAnnotations:  <none>\nReplicas:     1 current / 1 desired\nPods Status:  1 Running / 0 Waiting / 0 Succeeded / 0 Failed\nPod Template:\n  Labels:  app=agnhost\n           role=primary\n  Containers:\n   agnhost-primary:\n    Image:        k8s.gcr.io/e2e-test-images/agnhost:2.39\n    Port:         6379/TCP\n    Host Port:    0/TCP\n    Environment:  <none>\n    Mounts:       <none>\n  Volumes:        <none>\nEvents:\n  Type    Reason            Age   From                    Message\n  ----    ------            ----  ----                    -------\n  Normal  SuccessfulCreate  2s    replication-controller  Created pod: agnhost-primary-9hgm8\n"

    Sep 21 11:29:09.504: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-4927 describe service agnhost-primary'
    Sep 21 11:29:09.583: INFO: stderr: ""
    Sep 21 11:29:09.583: INFO: stdout: "Name:              agnhost-primary\nNamespace:         kubectl-4927\nLabels:            app=agnhost\n                   role=primary\nAnnotations:       <none>\nSelector:          app=agnhost,role=primary\nType:              ClusterIP\nIP Family Policy:  SingleStack\nIP Families:       IPv4\nIP:                10.143.63.32\nIPs:               10.143.63.32\nPort:              <unset>  6379/TCP\nTargetPort:        agnhost-server/TCP\nEndpoints:         192.168.0.15:6379\nSession Affinity:  None\nEvents:            <none>\n"
    Sep 21 11:29:09.587: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-4927 describe node k8s-upgrade-and-conformance-op826y-8r46f-qkhlp'
    Sep 21 11:29:09.699: INFO: stderr: ""
    Sep 21 11:29:09.699: INFO: stdout: "Name:               k8s-upgrade-and-conformance-op826y-8r46f-qkhlp\nRoles:              control-plane,master\nLabels:             beta.kubernetes.io/arch=amd64\n                    beta.kubernetes.io/os=linux\n                    kubernetes.io/arch=amd64\n                    kubernetes.io/hostname=k8s-upgrade-and-conformance-op826y-8r46f-qkhlp\n                    kubernetes.io/os=linux\n                    node-role.kubernetes.io/control-plane=\n                    node-role.kubernetes.io/master=\n                    node.kubernetes.io/exclude-from-external-load-balancers=\nAnnotations:        cluster.x-k8s.io/cluster-name: k8s-upgrade-and-conformance-op826y\n                    cluster.x-k8s.io/cluster-namespace: k8s-upgrade-and-conformance-w1mafc\n                    cluster.x-k8s.io/machine: k8s-upgrade-and-conformance-op826y-8r46f-qkhlp\n                    cluster.x-k8s.io/owner-kind: KubeadmControlPlane\n                    cluster.x-k8s.io/owner-name: k8s-upgrade-and-conformance-op826y-8r46f\n                    kubeadm.alpha.kubernetes.io/cri-socket: unix:///var/run/containerd/containerd.sock\n                    node.alpha.kubernetes.io/ttl: 0\n                    volumes.kubernetes.io/controller-managed-attach-detach: true\nCreationTimestamp:  Wed, 21 Sep 2022 11:22:16 +0000\nTaints:             node-role.kubernetes.io/master:NoSchedule\nUnschedulable:      false\nLease:\n  HolderIdentity:  k8s-upgrade-and-conformance-op826y-8r46f-qkhlp\n  AcquireTime:     <unset>\n  RenewTime:       Wed, 21 Sep 2022 11:29:03 +0000\nConditions:\n  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message\n  ----             ------  -----------------                 ------------------                ------                       -------\n  MemoryPressure   False   Wed, 21 Sep 2022 11:28:17 +0000   Wed, 21 Sep 2022 11:22:16 +0000   KubeletHasSufficientMemory   kubelet has sufficient memory available\n  DiskPressure     False   Wed, 21 Sep 2022 11:28:17 +0000   Wed, 21 Sep 2022 11:22:16 +0000   KubeletHasNoDiskPressure     kubelet has no disk pressure\n  PIDPressure      False   Wed, 21 Sep 2022 11:28:17 +0000   Wed, 21 Sep 2022 11:22:16 +0000   KubeletHasSufficientPID      kubelet has sufficient PID available\n  Ready            True    Wed, 21 Sep 2022 11:28:17 +0000   Wed, 21 Sep 2022 11:23:15 +0000   KubeletReady                 kubelet is posting ready status\nAddresses:\n  InternalIP:  172.18.0.9\n  Hostname:    k8s-upgrade-and-conformance-op826y-8r46f-qkhlp\nCapacity:\n  cpu:                8\n  ephemeral-storage:  253882800Ki\n  hugepages-1Gi:      0\n  hugepages-2Mi:      0\n  memory:             65860676Ki\n  pods:               110\nAllocatable:\n  cpu:                8\n  ephemeral-storage:  253882800Ki\n  hugepages-1Gi:      0\n  hugepages-2Mi:      0\n  memory:             65860676Ki\n  pods:               110\nSystem Info:\n  Machine ID:                 5c0784de4f4147d29a26946f0623eb65\n  System UUID:                27754a0c-b4a0-4152-b6f1-159ac84e4a3e\n  Boot ID:                    464e1a86-c894-4ffc-8b14-5f9e82dcbc40\n  Kernel Version:             5.4.0-1076-gke\n  OS Image:                   Ubuntu 22.04.1 LTS\n  Operating System:           linux\n  Architecture:               amd64\n  Container Runtime Version:  containerd://1.6.7\n  Kubelet Version:            v1.22.14\n  Kube-Proxy Version:         v1.22.14\nPodCIDR:                      192.168.5.0/24\nPodCIDRs:                     192.168.5.0/24\nProviderID:                   docker:////k8s-upgrade-and-conformance-op826y-8r46f-qkhlp\nNon-terminated Pods:          (6 in total)\n  Namespace                   Name                                                                      CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age\n  ---------                   ----                                                                      ------------  ----------  ---------------  -------------  ---\n  kube-system                 etcd-k8s-upgrade-and-conformance-op826y-8r46f-qkhlp                       100m (1%)     0 (0%)      100Mi (0%)       0 (0%)         6m48s\n  kube-system                 kindnet-nnk7x                                                             100m (1%)     100m (1%)   50Mi (0%)        50Mi (0%)      6m53s\n  kube-system                 kube-apiserver-k8s-upgrade-and-conformance-op826y-8r46f-qkhlp             250m (3%)     0 (0%)      0 (0%)           0 (0%)         6m52s\n  kube-system                 kube-controller-manager-k8s-upgrade-and-conformance-op826y-8r46f-qkhlp    200m (2%)     0 (0%)      0 (0%)           0 (0%)         6m52s\n  kube-system                 kube-proxy-lq2hk                                                          0 (0%)        0 (0%)      0 (0%)           0 (0%)         5m1s\n  kube-system                 kube-scheduler-k8s-upgrade-and-conformance-op826y-8r46f-qkhlp             100m (1%)     0 (0%)      0 (0%)           0 (0%)         6m52s\nAllocated resources:\n  (Total limits may be over 100 percent, i.e., overcommitted.)\n  Resource           Requests    Limits\n  --------           --------    ------\n  cpu                750m (9%)   100m (1%)\n  memory             150Mi (0%)  50Mi (0%)\n  ephemeral-storage  0 (0%)      0 (0%)\n  hugepages-1Gi      0 (0%)      0 (0%)\n  hugepages-2Mi      0 (0%)      0 (0%)\nEvents:\n  Type     Reason                    Age                    From        Message\n  ----     ------                    ----                   ----        -------\n  Normal   Starting                  4m58s                  kube-proxy  \n  Normal   Starting                  6m53s                  kubelet     Starting kubelet.\n  Warning  InvalidDiskCapacity       6m53s                  kubelet     invalid capacity 0 on image filesystem\n  Normal   NodeHasSufficientMemory   6m53s (x2 over 6m53s)  kubelet     Node k8s-upgrade-and-conformance-op826y-8r46f-qkhlp status is now: NodeHasSufficientMemory\n  Normal   NodeHasSufficientPID      6m53s (x2 over 6m53s)  kubelet     Node k8s-upgrade-and-conformance-op826y-8r46f-qkhlp status is now: NodeHasSufficientPID\n  Normal   NodeAllocatableEnforced   6m53s                  kubelet     Updated Node Allocatable limit across pods\n  Warning  CheckLimitsForResolvConf  6m53s                  kubelet     Resolv.conf file '/etc/resolv.conf' contains search line consisting of more than 3 domains!\n  Normal   NodeHasNoDiskPressure     6m53s (x2 over 6m53s)  kubelet     Node k8s-upgrade-and-conformance-op826y-8r46f-qkhlp status is now: NodeHasNoDiskPressure\n  Normal   Starting                  6m35s                  kube-proxy  Starting kube-proxy.\n  Normal   NodeReady                 5m54s                  kubelet     Node k8s-upgrade-and-conformance-op826y-8r46f-qkhlp status is now: NodeReady\n"
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:29:09.776: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-4927" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for rc and pods  [Conformance]","total":-1,"completed":11,"skipped":189,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:29:09.864: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume as non-root [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating configMap with name projected-configmap-test-volume-383156b6-a661-4a50-9770-56b0141ebf81
    STEP: Creating a pod to test consume configMaps
    Sep 21 11:29:09.904: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-b160ff75-c52a-43c6-a328-6b1d0bade88b" in namespace "projected-5983" to be "Succeeded or Failed"

    Sep 21 11:29:09.907: INFO: Pod "pod-projected-configmaps-b160ff75-c52a-43c6-a328-6b1d0bade88b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.31593ms
    Sep 21 11:29:11.911: INFO: Pod "pod-projected-configmaps-b160ff75-c52a-43c6-a328-6b1d0bade88b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006922249s
    Sep 21 11:29:13.915: INFO: Pod "pod-projected-configmaps-b160ff75-c52a-43c6-a328-6b1d0bade88b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010985528s
    STEP: Saw pod success
    Sep 21 11:29:13.915: INFO: Pod "pod-projected-configmaps-b160ff75-c52a-43c6-a328-6b1d0bade88b" satisfied condition "Succeeded or Failed"

    Sep 21 11:29:13.918: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-cbeo0a pod pod-projected-configmaps-b160ff75-c52a-43c6-a328-6b1d0bade88b container agnhost-container: <nil>
    STEP: delete the pod
    Sep 21 11:29:13.939: INFO: Waiting for pod pod-projected-configmaps-b160ff75-c52a-43c6-a328-6b1d0bade88b to disappear
    Sep 21 11:29:13.942: INFO: Pod pod-projected-configmaps-b160ff75-c52a-43c6-a328-6b1d0bade88b no longer exists
    [AfterEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:29:13.942: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-5983" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume as non-root [NodeConformance] [Conformance]","total":-1,"completed":12,"skipped":247,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] version v1
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 39 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:29:16.140: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "proxy-5348" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Proxy version v1 A set of valid responses are returned for both pod and service ProxyWithPath [Conformance]","total":-1,"completed":13,"skipped":280,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:29:22.776: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-1641" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should update annotations on modification [NodeConformance] [Conformance]","total":-1,"completed":14,"skipped":310,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:29:22.794: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should fail to create secret due to empty secret key [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating projection with secret that has name secret-emptykey-test-83c554f9-92a1-45f0-bf1b-f6148a91b6b6
    [AfterEach] [sig-node] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:29:22.825: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-4736" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Secrets should fail to create secret due to empty secret key [Conformance]","total":-1,"completed":15,"skipped":316,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:38
    STEP: Setting up data
    [It] should support subpaths with secret pod [LinuxOnly] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating pod pod-subpath-test-secret-dkfj
    STEP: Creating a pod to test atomic-volume-subpath
    Sep 21 11:29:22.894: INFO: Waiting up to 5m0s for pod "pod-subpath-test-secret-dkfj" in namespace "subpath-7850" to be "Succeeded or Failed"

    Sep 21 11:29:22.896: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.632939ms
    Sep 21 11:29:24.901: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Running", Reason="", readiness=true. Elapsed: 2.007009578s
    Sep 21 11:29:26.905: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Running", Reason="", readiness=true. Elapsed: 4.010655644s
    Sep 21 11:29:28.909: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Running", Reason="", readiness=true. Elapsed: 6.014810911s
    Sep 21 11:29:30.913: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Running", Reason="", readiness=true. Elapsed: 8.019482644s
    Sep 21 11:29:32.917: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Running", Reason="", readiness=true. Elapsed: 10.023436981s
... skipping 2 lines ...
    Sep 21 11:29:38.929: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Running", Reason="", readiness=true. Elapsed: 16.035346127s
    Sep 21 11:29:40.934: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Running", Reason="", readiness=true. Elapsed: 18.039902012s
    Sep 21 11:29:42.938: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Running", Reason="", readiness=true. Elapsed: 20.043910655s
    Sep 21 11:29:44.942: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Running", Reason="", readiness=false. Elapsed: 22.04823422s
    Sep 21 11:29:46.947: INFO: Pod "pod-subpath-test-secret-dkfj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.053157561s
    STEP: Saw pod success
    Sep 21 11:29:46.947: INFO: Pod "pod-subpath-test-secret-dkfj" satisfied condition "Succeeded or Failed"

    Sep 21 11:29:46.950: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod pod-subpath-test-secret-dkfj container test-container-subpath-secret-dkfj: <nil>
    STEP: delete the pod
    Sep 21 11:29:46.965: INFO: Waiting for pod pod-subpath-test-secret-dkfj to disappear
    Sep 21 11:29:46.968: INFO: Pod pod-subpath-test-secret-dkfj no longer exists
    STEP: Deleting pod pod-subpath-test-secret-dkfj
    Sep 21 11:29:46.968: INFO: Deleting pod "pod-subpath-test-secret-dkfj" in namespace "subpath-7850"
... skipping 23 lines ...
    Sep 21 11:27:50.666: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:50.669: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:50.672: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:50.677: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:50.679: INFO: Unable to read jessie_udp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:50.682: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:50.682: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:27:55.689: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:55.693: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:55.696: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:55.702: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:55.704: INFO: Unable to read jessie_udp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:55.707: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:27:55.707: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:28:00.691: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:00.694: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:00.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:00.702: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:00.705: INFO: Unable to read jessie_udp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:00.707: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:00.707: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:28:05.698: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:05.703: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:05.706: INFO: Unable to read jessie_udp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:05.708: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:05.708: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:28:10.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:10.707: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:10.707: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:28:15.696: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:15.714: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:15.714: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:28:20.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:20.708: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:28:25.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:25.707: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:28:30.700: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:30.712: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:28:35.701: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:35.717: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:28:40.698: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:40.714: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:28:45.695: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:45.705: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:28:50.698: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:50.708: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:28:55.696: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:28:55.707: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:00.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:00.710: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:05.696: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:05.707: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:10.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:10.708: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:15.703: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:15.719: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:20.700: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:20.711: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:25.696: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:25.709: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:30.698: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:30.710: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:35.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:35.709: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:40.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:40.709: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:45.695: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:45.706: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:50.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:50.708: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:55.696: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:29:55.707: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:00.701: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:30:00.714: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:05.696: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:30:05.707: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:10.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:30:10.709: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:15.698: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:30:15.709: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:20.700: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:30:20.713: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:25.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e: the server could not find the requested resource (get pods dns-test-93e24d18-2605-4e43-8936-41b244c18c3e)
    Sep 21 11:30:25.707: INFO: Lookups using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:30.708: INFO: DNS probes using dns-7389/dns-test-93e24d18-2605-4e43-8936-41b244c18c3e succeeded
    
    STEP: deleting the pod
    [AfterEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
... skipping 4 lines ...
    • [SLOW TEST:168.133 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/framework.go:23
      should provide DNS for the cluster  [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide DNS for the cluster  [Conformance]","total":-1,"completed":6,"skipped":183,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/storage/downwardapi_volume.go:41
    [It] should provide container's memory request [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test downward API volume plugin
    Sep 21 11:30:30.778: INFO: Waiting up to 5m0s for pod "downwardapi-volume-079fa37f-9ea7-49f6-b773-c8680343f835" in namespace "downward-api-832" to be "Succeeded or Failed"

    Sep 21 11:30:30.782: INFO: Pod "downwardapi-volume-079fa37f-9ea7-49f6-b773-c8680343f835": Phase="Pending", Reason="", readiness=false. Elapsed: 4.11025ms
    Sep 21 11:30:32.785: INFO: Pod "downwardapi-volume-079fa37f-9ea7-49f6-b773-c8680343f835": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007691453s
    Sep 21 11:30:34.794: INFO: Pod "downwardapi-volume-079fa37f-9ea7-49f6-b773-c8680343f835": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.01630987s
    STEP: Saw pod success
    Sep 21 11:30:34.794: INFO: Pod "downwardapi-volume-079fa37f-9ea7-49f6-b773-c8680343f835" satisfied condition "Succeeded or Failed"

    Sep 21 11:30:34.798: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-cbeo0a pod downwardapi-volume-079fa37f-9ea7-49f6-b773-c8680343f835 container client-container: <nil>
    STEP: delete the pod
    Sep 21 11:30:34.813: INFO: Waiting for pod downwardapi-volume-079fa37f-9ea7-49f6-b773-c8680343f835 to disappear
    Sep 21 11:30:34.817: INFO: Pod downwardapi-volume-079fa37f-9ea7-49f6-b773-c8680343f835 no longer exists
    [AfterEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:30:34.817: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-832" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide container's memory request [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":184,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 7 lines ...
    STEP: Create set of pods
    Sep 21 11:30:34.879: INFO: created test-pod-1
    Sep 21 11:30:34.888: INFO: created test-pod-2
    Sep 21 11:30:34.892: INFO: created test-pod-3
    STEP: waiting for all 3 pods to be running
    Sep 21 11:30:34.893: INFO: Waiting up to 5m0s for all pods (need at least 3) in namespace 'pods-9034' to be running and ready
    Sep 21 11:30:34.904: INFO: The status of Pod test-pod-1 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep 21 11:30:34.904: INFO: The status of Pod test-pod-2 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep 21 11:30:34.904: INFO: The status of Pod test-pod-3 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep 21 11:30:34.904: INFO: 0 / 3 pods in namespace 'pods-9034' are running and ready (0 seconds elapsed)
    Sep 21 11:30:34.904: INFO: expected 0 pod replicas in namespace 'pods-9034', 0 are Running and Ready.
    Sep 21 11:30:34.904: INFO: POD         NODE                                                            PHASE    GRACE  CONDITIONS
    Sep 21 11:30:34.904: INFO: test-pod-1  k8s-upgrade-and-conformance-op826y-md-0-m2lf7-66b8cf447f-l57ll  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-21 11:30:34 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-21 11:30:34 +0000 UTC ContainersNotReady containers with unready status: [token-test]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-09-21 11:30:34 +0000 UTC ContainersNotReady containers with unready status: [token-test]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-21 11:30:34 +0000 UTC  }]
    Sep 21 11:30:34.904: INFO: test-pod-2  k8s-upgrade-and-conformance-op826y-md-0-m2lf7-66b8cf447f-l57ll  Pending         [{PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-21 11:30:34 +0000 UTC  }]
    Sep 21 11:30:34.904: INFO: test-pod-3  k8s-upgrade-and-conformance-op826y-worker-cbeo0a                Pending         [{PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-21 11:30:34 +0000 UTC  }]
... skipping 7 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:30:38.934: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-9034" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should delete a collection of pods [Conformance]","total":-1,"completed":8,"skipped":194,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-node] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:30:42.013: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-329" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Container Runtime blackbox test on terminated container should report termination message [LinuxOnly] from file when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]","total":-1,"completed":9,"skipped":195,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] PodTemplates
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 6 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:30:42.093: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "podtemplate-577" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] PodTemplates should run the lifecycle of PodTemplates [Conformance]","total":-1,"completed":10,"skipped":204,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-apps] StatefulSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 10 lines ...
    STEP: Looking for a node to schedule stateful set and pod
    STEP: Creating pod with conflicting port in namespace statefulset-2243
    STEP: Waiting until pod test-pod will start running in namespace statefulset-2243
    STEP: Creating statefulset with conflicting port in namespace statefulset-2243
    STEP: Waiting until stateful pod ss-0 will be recreated and deleted at least once in namespace statefulset-2243
    Sep 21 11:30:44.170: INFO: Observed stateful pod in namespace: statefulset-2243, name: ss-0, uid: 13f5df87-92dd-4ec4-874c-e10e775bc773, status phase: Pending. Waiting for statefulset controller to delete.
    Sep 21 11:30:44.182: INFO: Observed stateful pod in namespace: statefulset-2243, name: ss-0, uid: 13f5df87-92dd-4ec4-874c-e10e775bc773, status phase: Failed. Waiting for statefulset controller to delete.

    Sep 21 11:30:44.188: INFO: Observed stateful pod in namespace: statefulset-2243, name: ss-0, uid: 13f5df87-92dd-4ec4-874c-e10e775bc773, status phase: Failed. Waiting for statefulset controller to delete.

    Sep 21 11:30:44.191: INFO: Observed delete event for stateful pod ss-0 in namespace statefulset-2243
    STEP: Removing pod with conflicting port in namespace statefulset-2243
    STEP: Waiting when stateful pod ss-0 will be recreated in namespace statefulset-2243 and will be in running state
    [AfterEach] Basic StatefulSet functionality [StatefulSetBasic]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/statefulset.go:118
    Sep 21 11:30:46.209: INFO: Deleting all statefulset in ns statefulset-2243
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:30:56.239: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-2243" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Should recreate evicted statefulset [Conformance]","total":-1,"completed":11,"skipped":209,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with secret pod [LinuxOnly] [Conformance]","total":-1,"completed":16,"skipped":328,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    [BeforeEach] [sig-apps] CronJob
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:29:46.979: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename cronjob
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 9 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:31:01.034: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "cronjob-926" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] CronJob should replace jobs when ReplaceConcurrent [Conformance]","total":-1,"completed":17,"skipped":328,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:31:02.405: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-74" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":12,"skipped":266,"failed":0}

    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:31:02.416: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename crd-publish-openapi
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 6 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:31:14.112: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-2563" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group and version but different kinds [Conformance]","total":-1,"completed":13,"skipped":266,"failed":0}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] EndpointSlice
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 25 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:31:14.230: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "endpointslice-6554" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] EndpointSlice should support creating EndpointSlice API operations [Conformance]","total":-1,"completed":14,"skipped":280,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:31:14.247: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable via environment variable [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating configMap configmap-3320/configmap-test-7d9a9c8b-9cb0-4f9b-b249-8845e05e5eb3
    STEP: Creating a pod to test consume configMaps
    Sep 21 11:31:14.280: INFO: Waiting up to 5m0s for pod "pod-configmaps-7ecb7247-2aae-4124-9b89-4f20d47c09d7" in namespace "configmap-3320" to be "Succeeded or Failed"

    Sep 21 11:31:14.282: INFO: Pod "pod-configmaps-7ecb7247-2aae-4124-9b89-4f20d47c09d7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.351856ms
    Sep 21 11:31:16.287: INFO: Pod "pod-configmaps-7ecb7247-2aae-4124-9b89-4f20d47c09d7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007082117s
    Sep 21 11:31:18.290: INFO: Pod "pod-configmaps-7ecb7247-2aae-4124-9b89-4f20d47c09d7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010404486s
    STEP: Saw pod success
    Sep 21 11:31:18.290: INFO: Pod "pod-configmaps-7ecb7247-2aae-4124-9b89-4f20d47c09d7" satisfied condition "Succeeded or Failed"

    Sep 21 11:31:18.293: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-cbeo0a pod pod-configmaps-7ecb7247-2aae-4124-9b89-4f20d47c09d7 container env-test: <nil>
    STEP: delete the pod
    Sep 21 11:31:18.319: INFO: Waiting for pod pod-configmaps-7ecb7247-2aae-4124-9b89-4f20d47c09d7 to disappear
    Sep 21 11:31:18.321: INFO: Pod pod-configmaps-7ecb7247-2aae-4124-9b89-4f20d47c09d7 no longer exists
    [AfterEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:31:18.321: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-3320" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] ConfigMap should be consumable via environment variable [NodeConformance] [Conformance]","total":-1,"completed":15,"skipped":284,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:31:18.339: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename security-context-test
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/security_context.go:46
    [It] should run the container as unprivileged when false [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    Sep 21 11:31:18.372: INFO: Waiting up to 5m0s for pod "busybox-privileged-false-63d84f88-43d4-4bdb-b5ea-740feeeecd8d" in namespace "security-context-test-9888" to be "Succeeded or Failed"

    Sep 21 11:31:18.375: INFO: Pod "busybox-privileged-false-63d84f88-43d4-4bdb-b5ea-740feeeecd8d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.327304ms
    Sep 21 11:31:20.379: INFO: Pod "busybox-privileged-false-63d84f88-43d4-4bdb-b5ea-740feeeecd8d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006526572s
    Sep 21 11:31:22.383: INFO: Pod "busybox-privileged-false-63d84f88-43d4-4bdb-b5ea-740feeeecd8d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010854444s
    Sep 21 11:31:22.383: INFO: Pod "busybox-privileged-false-63d84f88-43d4-4bdb-b5ea-740feeeecd8d" satisfied condition "Succeeded or Failed"

    Sep 21 11:31:22.388: INFO: Got logs for pod "busybox-privileged-false-63d84f88-43d4-4bdb-b5ea-740feeeecd8d": "ip: RTNETLINK answers: Operation not permitted\n"
    [AfterEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:31:22.389: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-test-9888" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Security Context When creating a pod with privileged should run the container as unprivileged when false [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":16,"skipped":291,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 11 lines ...
    STEP: Destroying namespace "services-4786" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should find a service from listing all namespaces [Conformance]","total":-1,"completed":17,"skipped":315,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 18 lines ...
    • [SLOW TEST:242.628 seconds]
    [sig-node] Probing container
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/framework.go:23
      should *not* be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    ------------------------------
    {"msg":"PASSED [sig-node] Probing container should *not* be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]","total":-1,"completed":9,"skipped":143,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Watchers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 23 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:32:51.078: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-4482" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Watchers should observe an object deletion if it stops meeting the requirements of the selector [Conformance]","total":-1,"completed":10,"skipped":188,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:32:51.104: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename var-expansion
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should allow substituting values in a container's args [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test substitution in container's args
    Sep 21 11:32:51.138: INFO: Waiting up to 5m0s for pod "var-expansion-34f46f15-44eb-48f6-b2bc-b3a01abd20d0" in namespace "var-expansion-3657" to be "Succeeded or Failed"

    Sep 21 11:32:51.141: INFO: Pod "var-expansion-34f46f15-44eb-48f6-b2bc-b3a01abd20d0": Phase="Pending", Reason="", readiness=false. Elapsed: 2.351545ms
    Sep 21 11:32:53.145: INFO: Pod "var-expansion-34f46f15-44eb-48f6-b2bc-b3a01abd20d0": Phase="Pending", Reason="", readiness=false. Elapsed: 2.00686717s
    Sep 21 11:32:55.150: INFO: Pod "var-expansion-34f46f15-44eb-48f6-b2bc-b3a01abd20d0": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.011505876s
    STEP: Saw pod success
    Sep 21 11:32:55.150: INFO: Pod "var-expansion-34f46f15-44eb-48f6-b2bc-b3a01abd20d0" satisfied condition "Succeeded or Failed"

    Sep 21 11:32:55.152: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod var-expansion-34f46f15-44eb-48f6-b2bc-b3a01abd20d0 container dapi-container: <nil>
    STEP: delete the pod
    Sep 21 11:32:55.179: INFO: Waiting for pod var-expansion-34f46f15-44eb-48f6-b2bc-b3a01abd20d0 to disappear
    Sep 21 11:32:55.181: INFO: Pod var-expansion-34f46f15-44eb-48f6-b2bc-b3a01abd20d0 no longer exists
    [AfterEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:32:55.181: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-3657" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Variable Expansion should allow substituting values in a container's args [NodeConformance] [Conformance]","total":-1,"completed":11,"skipped":199,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 25 lines ...
    STEP: Destroying namespace "services-2012" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]","total":-1,"completed":12,"skipped":227,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 21 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:33:29.653: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-804" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Container Runtime blackbox test when starting a container that exits should run with the expected status [NodeConformance] [Conformance]","total":-1,"completed":13,"skipped":251,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:33:29.668: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings and Item mode set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating configMap with name configmap-test-volume-map-a932c901-e73f-47f3-bb42-325005144b29
    STEP: Creating a pod to test consume configMaps
    Sep 21 11:33:29.703: INFO: Waiting up to 5m0s for pod "pod-configmaps-59d8dd0d-0988-4d64-a9d6-4b192405c1e5" in namespace "configmap-2562" to be "Succeeded or Failed"

    Sep 21 11:33:29.706: INFO: Pod "pod-configmaps-59d8dd0d-0988-4d64-a9d6-4b192405c1e5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.509736ms
    Sep 21 11:33:31.711: INFO: Pod "pod-configmaps-59d8dd0d-0988-4d64-a9d6-4b192405c1e5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007017953s
    Sep 21 11:33:33.715: INFO: Pod "pod-configmaps-59d8dd0d-0988-4d64-a9d6-4b192405c1e5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.011754896s
    STEP: Saw pod success
    Sep 21 11:33:33.715: INFO: Pod "pod-configmaps-59d8dd0d-0988-4d64-a9d6-4b192405c1e5" satisfied condition "Succeeded or Failed"

    Sep 21 11:33:33.718: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod pod-configmaps-59d8dd0d-0988-4d64-a9d6-4b192405c1e5 container agnhost-container: <nil>
    STEP: delete the pod
    Sep 21 11:33:33.732: INFO: Waiting for pod pod-configmaps-59d8dd0d-0988-4d64-a9d6-4b192405c1e5 to disappear
    Sep 21 11:33:33.735: INFO: Pod pod-configmaps-59d8dd0d-0988-4d64-a9d6-4b192405c1e5 no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:33:33.735: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-2562" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings and Item mode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":14,"skipped":256,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:33:33.753: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename downward-api
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should provide default limits.cpu/memory from node allocatable [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test downward api env vars
    Sep 21 11:33:33.789: INFO: Waiting up to 5m0s for pod "downward-api-1b8c0ec8-c84d-4d6c-bbae-195a7a4cc54e" in namespace "downward-api-813" to be "Succeeded or Failed"

    Sep 21 11:33:33.792: INFO: Pod "downward-api-1b8c0ec8-c84d-4d6c-bbae-195a7a4cc54e": Phase="Pending", Reason="", readiness=false. Elapsed: 3.128942ms
    Sep 21 11:33:35.797: INFO: Pod "downward-api-1b8c0ec8-c84d-4d6c-bbae-195a7a4cc54e": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007706837s
    Sep 21 11:33:37.802: INFO: Pod "downward-api-1b8c0ec8-c84d-4d6c-bbae-195a7a4cc54e": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012679293s
    STEP: Saw pod success
    Sep 21 11:33:37.802: INFO: Pod "downward-api-1b8c0ec8-c84d-4d6c-bbae-195a7a4cc54e" satisfied condition "Succeeded or Failed"

    Sep 21 11:33:37.805: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod downward-api-1b8c0ec8-c84d-4d6c-bbae-195a7a4cc54e container dapi-container: <nil>
    STEP: delete the pod
    Sep 21 11:33:37.819: INFO: Waiting for pod downward-api-1b8c0ec8-c84d-4d6c-bbae-195a7a4cc54e to disappear
    Sep 21 11:33:37.821: INFO: Pod downward-api-1b8c0ec8-c84d-4d6c-bbae-195a7a4cc54e no longer exists
    [AfterEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:33:37.821: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-813" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Downward API should provide default limits.cpu/memory from node allocatable [NodeConformance] [Conformance]","total":-1,"completed":15,"skipped":262,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 18 lines ...
    • [SLOW TEST:242.872 seconds]
    [sig-node] Probing container
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/framework.go:23
      should *not* be restarted with a tcp:8080 liveness probe [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    ------------------------------
    {"msg":"PASSED [sig-node] Probing container should *not* be restarted with a tcp:8080 liveness probe [NodeConformance] [Conformance]","total":-1,"completed":16,"skipped":270,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:37:47.395: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-4488" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should update labels on modification [NodeConformance] [Conformance]","total":-1,"completed":17,"skipped":275,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:37:47.426: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename security-context-test
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/security_context.go:46
    [It] should not allow privilege escalation when false [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    Sep 21 11:37:47.484: INFO: Waiting up to 5m0s for pod "alpine-nnp-false-662026ac-f06f-43da-ad28-872f3e1c1164" in namespace "security-context-test-6175" to be "Succeeded or Failed"

    Sep 21 11:37:47.488: INFO: Pod "alpine-nnp-false-662026ac-f06f-43da-ad28-872f3e1c1164": Phase="Pending", Reason="", readiness=false. Elapsed: 4.345357ms
    Sep 21 11:37:49.494: INFO: Pod "alpine-nnp-false-662026ac-f06f-43da-ad28-872f3e1c1164": Phase="Pending", Reason="", readiness=false. Elapsed: 2.0097824s
    Sep 21 11:37:51.500: INFO: Pod "alpine-nnp-false-662026ac-f06f-43da-ad28-872f3e1c1164": Phase="Pending", Reason="", readiness=false. Elapsed: 4.016173141s
    Sep 21 11:37:53.507: INFO: Pod "alpine-nnp-false-662026ac-f06f-43da-ad28-872f3e1c1164": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.022752308s
    Sep 21 11:37:53.507: INFO: Pod "alpine-nnp-false-662026ac-f06f-43da-ad28-872f3e1c1164" satisfied condition "Succeeded or Failed"

    [AfterEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:37:53.516: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-test-6175" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Security Context when creating containers with AllowPrivilegeEscalation should not allow privilege escalation when false [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":18,"skipped":281,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:37:53.580: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename var-expansion
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should fail substituting values in a volume subpath with backticks [Slow] [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    Sep 21 11:37:55.659: INFO: Deleting pod "var-expansion-a69d4273-f0d1-4cd6-9fcb-ca6eac2f7da7" in namespace "var-expansion-930"
    Sep 21 11:37:55.668: INFO: Wait up to 5m0s for pod "var-expansion-a69d4273-f0d1-4cd6-9fcb-ca6eac2f7da7" to be fully deleted
    [AfterEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:37:57.681: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-930" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Variable Expansion should fail substituting values in a volume subpath with backticks [Slow] [Conformance]","total":-1,"completed":19,"skipped":301,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:37:57.777: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (non-root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test emptydir 0777 on node default medium
    Sep 21 11:37:57.842: INFO: Waiting up to 5m0s for pod "pod-88f0a450-3e8a-487e-9e6f-2899c8421f22" in namespace "emptydir-3055" to be "Succeeded or Failed"

    Sep 21 11:37:57.848: INFO: Pod "pod-88f0a450-3e8a-487e-9e6f-2899c8421f22": Phase="Pending", Reason="", readiness=false. Elapsed: 5.403649ms
    Sep 21 11:37:59.860: INFO: Pod "pod-88f0a450-3e8a-487e-9e6f-2899c8421f22": Phase="Running", Reason="", readiness=true. Elapsed: 2.01756457s
    Sep 21 11:38:01.866: INFO: Pod "pod-88f0a450-3e8a-487e-9e6f-2899c8421f22": Phase="Running", Reason="", readiness=false. Elapsed: 4.023914453s
    Sep 21 11:38:03.873: INFO: Pod "pod-88f0a450-3e8a-487e-9e6f-2899c8421f22": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.030904588s
    STEP: Saw pod success
    Sep 21 11:38:03.873: INFO: Pod "pod-88f0a450-3e8a-487e-9e6f-2899c8421f22" satisfied condition "Succeeded or Failed"

    Sep 21 11:38:03.878: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod pod-88f0a450-3e8a-487e-9e6f-2899c8421f22 container test-container: <nil>
    STEP: delete the pod
    Sep 21 11:38:03.909: INFO: Waiting for pod pod-88f0a450-3e8a-487e-9e6f-2899c8421f22 to disappear
    Sep 21 11:38:03.913: INFO: Pod pod-88f0a450-3e8a-487e-9e6f-2899c8421f22 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:03.913: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-3055" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":20,"skipped":337,"failed":0}

    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:38:03.926: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating configMap with name projected-configmap-test-volume-a88dfc03-907c-422c-bc13-ebdac66ff024
    STEP: Creating a pod to test consume configMaps
    Sep 21 11:38:03.989: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-c29329ae-9f97-49d8-bfe7-b5fc40b6c0ab" in namespace "projected-5817" to be "Succeeded or Failed"

    Sep 21 11:38:03.994: INFO: Pod "pod-projected-configmaps-c29329ae-9f97-49d8-bfe7-b5fc40b6c0ab": Phase="Pending", Reason="", readiness=false. Elapsed: 4.029178ms
    Sep 21 11:38:06.001: INFO: Pod "pod-projected-configmaps-c29329ae-9f97-49d8-bfe7-b5fc40b6c0ab": Phase="Pending", Reason="", readiness=false. Elapsed: 2.011069778s
    Sep 21 11:38:08.007: INFO: Pod "pod-projected-configmaps-c29329ae-9f97-49d8-bfe7-b5fc40b6c0ab": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.01687766s
    STEP: Saw pod success
    Sep 21 11:38:08.007: INFO: Pod "pod-projected-configmaps-c29329ae-9f97-49d8-bfe7-b5fc40b6c0ab" satisfied condition "Succeeded or Failed"

    Sep 21 11:38:08.012: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod pod-projected-configmaps-c29329ae-9f97-49d8-bfe7-b5fc40b6c0ab container agnhost-container: <nil>
    STEP: delete the pod
    Sep 21 11:38:08.033: INFO: Waiting for pod pod-projected-configmaps-c29329ae-9f97-49d8-bfe7-b5fc40b6c0ab to disappear
    Sep 21 11:38:08.037: INFO: Pod pod-projected-configmaps-c29329ae-9f97-49d8-bfe7-b5fc40b6c0ab no longer exists
    [AfterEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:08.037: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-5817" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":21,"skipped":337,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:38:08.070: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename downward-api
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should provide container's limits.cpu/memory and requests.cpu/memory as env vars [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test downward api env vars
    Sep 21 11:38:08.124: INFO: Waiting up to 5m0s for pod "downward-api-407bc2ad-4212-4ddf-ab05-544b5ef8b632" in namespace "downward-api-5125" to be "Succeeded or Failed"

    Sep 21 11:38:08.129: INFO: Pod "downward-api-407bc2ad-4212-4ddf-ab05-544b5ef8b632": Phase="Pending", Reason="", readiness=false. Elapsed: 4.775651ms
    Sep 21 11:38:10.135: INFO: Pod "downward-api-407bc2ad-4212-4ddf-ab05-544b5ef8b632": Phase="Pending", Reason="", readiness=false. Elapsed: 2.010834911s
    Sep 21 11:38:12.142: INFO: Pod "downward-api-407bc2ad-4212-4ddf-ab05-544b5ef8b632": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.017341493s
    STEP: Saw pod success
    Sep 21 11:38:12.142: INFO: Pod "downward-api-407bc2ad-4212-4ddf-ab05-544b5ef8b632" satisfied condition "Succeeded or Failed"

    Sep 21 11:38:12.146: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod downward-api-407bc2ad-4212-4ddf-ab05-544b5ef8b632 container dapi-container: <nil>
    STEP: delete the pod
    Sep 21 11:38:12.181: INFO: Waiting for pod downward-api-407bc2ad-4212-4ddf-ab05-544b5ef8b632 to disappear
    Sep 21 11:38:12.183: INFO: Pod downward-api-407bc2ad-4212-4ddf-ab05-544b5ef8b632 no longer exists
    [AfterEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:12.183: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-5125" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Downward API should provide container's limits.cpu/memory and requests.cpu/memory as env vars [NodeConformance] [Conformance]","total":-1,"completed":22,"skipped":344,"failed":0}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:38:12.240: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating configMap with name configmap-test-volume-map-9bba7211-c0c2-4cbc-970d-d120ea3567e4
    STEP: Creating a pod to test consume configMaps
    Sep 21 11:38:12.314: INFO: Waiting up to 5m0s for pod "pod-configmaps-ae998dbd-c164-4970-ad7d-681e51e42684" in namespace "configmap-5405" to be "Succeeded or Failed"

    Sep 21 11:38:12.320: INFO: Pod "pod-configmaps-ae998dbd-c164-4970-ad7d-681e51e42684": Phase="Pending", Reason="", readiness=false. Elapsed: 5.95191ms
    Sep 21 11:38:14.327: INFO: Pod "pod-configmaps-ae998dbd-c164-4970-ad7d-681e51e42684": Phase="Pending", Reason="", readiness=false. Elapsed: 2.013203558s
    Sep 21 11:38:16.332: INFO: Pod "pod-configmaps-ae998dbd-c164-4970-ad7d-681e51e42684": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.01835903s
    STEP: Saw pod success
    Sep 21 11:38:16.332: INFO: Pod "pod-configmaps-ae998dbd-c164-4970-ad7d-681e51e42684" satisfied condition "Succeeded or Failed"

    Sep 21 11:38:16.335: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod pod-configmaps-ae998dbd-c164-4970-ad7d-681e51e42684 container agnhost-container: <nil>
    STEP: delete the pod
    Sep 21 11:38:16.347: INFO: Waiting for pod pod-configmaps-ae998dbd-c164-4970-ad7d-681e51e42684 to disappear
    Sep 21 11:38:16.349: INFO: Pod pod-configmaps-ae998dbd-c164-4970-ad7d-681e51e42684 no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:16.349: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-5405" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]","total":-1,"completed":23,"skipped":358,"failed":0}

    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:38:16.359: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename services
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:752
    [It] should serve multiport endpoints from pods  [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: creating service multi-endpoint-test in namespace services-4477
    STEP: waiting up to 3m0s for service multi-endpoint-test in namespace services-4477 to expose endpoints map[]
    Sep 21 11:38:16.401: INFO: Failed go get Endpoints object: endpoints "multi-endpoint-test" not found

    Sep 21 11:38:17.411: INFO: successfully validated that service multi-endpoint-test in namespace services-4477 exposes endpoints map[]
    STEP: Creating pod pod1 in namespace services-4477
    Sep 21 11:38:17.420: INFO: The status of Pod pod1 is Pending, waiting for it to be Running (with Ready = true)
    Sep 21 11:38:19.425: INFO: The status of Pod pod1 is Running (Ready = true)
    STEP: waiting up to 3m0s for service multi-endpoint-test in namespace services-4477 to expose endpoints map[pod1:[100]]
    Sep 21 11:38:19.437: INFO: successfully validated that service multi-endpoint-test in namespace services-4477 exposes endpoints map[pod1:[100]]
... skipping 28 lines ...
    STEP: Destroying namespace "services-4477" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should serve multiport endpoints from pods  [Conformance]","total":-1,"completed":24,"skipped":358,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Garbage collector
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 9 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:31.620: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "gc-7675" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should not be blocked by dependency circle [Conformance]","total":-1,"completed":25,"skipped":382,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:38:31.779: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename init-container
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-node] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/init_container.go:162
    [It] should not start app containers and fail the pod if init containers fail on a RestartNever pod [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: creating the pod
    Sep 21 11:38:31.808: INFO: PodSpec: initContainers in spec.initContainers
    [AfterEach] [sig-node] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:37.070: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "init-container-3476" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] InitContainer [NodeConformance] should not start app containers and fail the pod if init containers fail on a RestartNever pod [Conformance]","total":-1,"completed":26,"skipped":482,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Garbage collector
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 52 lines ...
    STEP: Creating replication controller my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022
    Sep 21 11:31:22.567: INFO: Pod name my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022: Found 0 pods out of 1
    Sep 21 11:31:27.573: INFO: Pod name my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022: Found 1 pods out of 1
    Sep 21 11:31:27.573: INFO: Ensuring all pods for ReplicationController "my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022" are running
    Sep 21 11:31:27.576: INFO: Pod "my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022-zv2ns" is running (conditions: [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-09-21 11:31:22 +0000 UTC Reason: Message:} {Type:Ready Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-09-21 11:31:23 +0000 UTC Reason: Message:} {Type:ContainersReady Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-09-21 11:31:23 +0000 UTC Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-09-21 11:31:22 +0000 UTC Reason: Message:}])
    Sep 21 11:31:27.576: INFO: Trying to dial the pod
    Sep 21 11:35:05.382: INFO: Controller my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022: Failed to GET from replica 1 [my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022-zv2ns]: the server is currently unable to handle the request (get pods my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022-zv2ns)

    pod status: v1.PodStatus{Phase:"Running", Conditions:[]v1.PodCondition{v1.PodCondition{Type:"Initialized", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63799356682, loc:(*time.Location)(0xa04d060)}}, Reason:"", Message:""}, v1.PodCondition{Type:"Ready", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63799356683, loc:(*time.Location)(0xa04d060)}}, Reason:"", Message:""}, v1.PodCondition{Type:"ContainersReady", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63799356683, loc:(*time.Location)(0xa04d060)}}, Reason:"", Message:""}, v1.PodCondition{Type:"PodScheduled", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63799356682, loc:(*time.Location)(0xa04d060)}}, Reason:"", Message:""}}, Message:"", Reason:"", NominatedNodeName:"", HostIP:"172.18.0.7", PodIP:"192.168.3.20", PodIPs:[]v1.PodIP{v1.PodIP{IP:"192.168.3.20"}}, StartTime:(*v1.Time)(0xc0025ef908), InitContainerStatuses:[]v1.ContainerStatus(nil), ContainerStatuses:[]v1.ContainerStatus{v1.ContainerStatus{Name:"my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022", State:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(0xc0025ef920), Terminated:(*v1.ContainerStateTerminated)(nil)}, LastTerminationState:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, Ready:true, RestartCount:0, Image:"k8s.gcr.io/e2e-test-images/agnhost:2.39", ImageID:"k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e", ContainerID:"containerd://5845a0b7609ae07ec931b2c9b231b4c4b6dc6b3bf97e43a33fd43f8be23b358c", Started:(*bool)(0xc003e7a1aa)}}, QOSClass:"BestEffort", EphemeralContainerStatuses:[]v1.ContainerStatus(nil)}
    Sep 21 11:38:38.371: INFO: Controller my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022: Failed to GET from replica 1 [my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022-zv2ns]: the server is currently unable to handle the request (get pods my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022-zv2ns)

    pod status: v1.PodStatus{Phase:"Running", Conditions:[]v1.PodCondition{v1.PodCondition{Type:"Initialized", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63799356682, loc:(*time.Location)(0xa04d060)}}, Reason:"", Message:""}, v1.PodCondition{Type:"Ready", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63799356683, loc:(*time.Location)(0xa04d060)}}, Reason:"", Message:""}, v1.PodCondition{Type:"ContainersReady", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63799356683, loc:(*time.Location)(0xa04d060)}}, Reason:"", Message:""}, v1.PodCondition{Type:"PodScheduled", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63799356682, loc:(*time.Location)(0xa04d060)}}, Reason:"", Message:""}}, Message:"", Reason:"", NominatedNodeName:"", HostIP:"172.18.0.7", PodIP:"192.168.3.20", PodIPs:[]v1.PodIP{v1.PodIP{IP:"192.168.3.20"}}, StartTime:(*v1.Time)(0xc0025ef908), InitContainerStatuses:[]v1.ContainerStatus(nil), ContainerStatuses:[]v1.ContainerStatus{v1.ContainerStatus{Name:"my-hostname-basic-e28e4089-2e4f-4c75-9c87-a0dd362b4022", State:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(0xc0025ef920), Terminated:(*v1.ContainerStateTerminated)(nil)}, LastTerminationState:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, Ready:true, RestartCount:0, Image:"k8s.gcr.io/e2e-test-images/agnhost:2.39", ImageID:"k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e", ContainerID:"containerd://5845a0b7609ae07ec931b2c9b231b4c4b6dc6b3bf97e43a33fd43f8be23b358c", Started:(*bool)(0xc003e7a1aa)}}, QOSClass:"BestEffort", EphemeralContainerStatuses:[]v1.ContainerStatus(nil)}
    Sep 21 11:38:38.372: FAIL: Did not get expected responses within the timeout period of 120.00 seconds.

    
    Full Stack Trace
    k8s.io/kubernetes/test/e2e/apps.glob..func7.2()
    	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/rc.go:65 +0x57
    k8s.io/kubernetes/test/e2e.RunE2ETests(0xc000bfcf00)
    	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 35 lines ...
    STEP: creating a pod to probe DNS
    STEP: submitting the pod to kubernetes
    STEP: retrieving the pod
    STEP: looking for the results for each expected name from probers
    Sep 21 11:28:43.741: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:28:43.753: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:28:43.753: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:28:48.772: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:28:48.794: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:28:48.794: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:28:53.765: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:28:53.776: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:28:53.776: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:28:58.773: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:28:58.786: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:28:58.786: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:29:03.773: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:03.784: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:08.778: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:08.789: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:13.771: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:13.782: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:18.770: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:18.782: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:23.766: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:23.776: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:28.766: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:28.778: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:33.766: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:33.777: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:38.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:38.781: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:43.765: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:43.775: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:48.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:48.781: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:53.765: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:53.777: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:29:58.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:29:58.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:03.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:03.780: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:08.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:08.781: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:13.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:13.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:18.779: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:18.791: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:23.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:23.778: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:28.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:28.785: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:33.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:33.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:38.764: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:38.773: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:43.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:43.781: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:48.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:48.784: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:53.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:53.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:30:58.771: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:30:58.784: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:03.765: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:03.776: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:08.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:08.780: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:13.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:13.778: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:18.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:18.784: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:23.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:23.777: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:28.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:28.785: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:33.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:33.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:38.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:38.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:43.765: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:43.776: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:48.770: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:48.785: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:53.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:53.777: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:31:58.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:31:58.780: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:03.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:03.780: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:08.766: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:08.777: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:13.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:13.780: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:18.774: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:18.791: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:23.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:23.780: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:28.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:28.781: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:33.766: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:33.778: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:38.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:38.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:43.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:43.778: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:48.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:48.777: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:53.766: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:53.776: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:32:58.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:32:58.783: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:03.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:03.778: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:08.765: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:08.776: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:13.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:13.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:18.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:18.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:23.766: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:23.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:28.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:28.788: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:33.771: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:33.786: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:38.766: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:38.778: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:43.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:43.783: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:48.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:48.777: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:53.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:53.780: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:33:58.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:33:58.780: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:03.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:03.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:08.765: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:08.775: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:13.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:13.780: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:18.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:18.791: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:23.783: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:23.820: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:28.776: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:28.809: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:33.776: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:33.794: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:38.778: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:38.806: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:43.780: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:43.802: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:48.778: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:48.800: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:53.778: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:53.798: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:34:58.794: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:34:58.824: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:03.807: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:03.859: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:08.781: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:08.817: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:13.774: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:13.792: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:18.782: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:18.804: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:23.780: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:23.797: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:28.774: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:28.794: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:33.781: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:33.802: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:38.781: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:38.817: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:43.777: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:43.795: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:48.793: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:48.825: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:53.777: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:53.799: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:35:58.784: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:35:58.807: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:03.777: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:03.799: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:08.776: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:08.803: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:13.775: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:13.792: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:18.776: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:18.808: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:23.781: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:23.802: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:28.780: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:28.810: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:33.777: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:33.795: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:38.778: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:38.800: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:43.772: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:43.791: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:48.780: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:48.802: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:53.777: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:53.795: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:36:58.788: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:36:58.815: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:03.777: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:03.797: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:08.781: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:08.804: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:13.778: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:13.800: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:18.786: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:18.807: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:23.778: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:23.797: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:28.774: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:28.798: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:33.776: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:33.801: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:38.778: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:38.797: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:43.776: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:43.797: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:48.788: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:48.816: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:53.781: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:53.806: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:37:58.787: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:37:58.812: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:03.777: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:38:03.795: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:08.781: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:38:08.809: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:13.775: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:38:13.793: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:18.770: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:38:18.784: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:23.767: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:38:23.777: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:28.769: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:38:28.781: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:33.768: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:38:33.779: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:38.781: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:38:38.796: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:43.774: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:38:43.788: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:43.800: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227: the server could not find the requested resource (get pods dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227)
    Sep 21 11:38:43.812: INFO: Lookups using dns-9840/dns-test-36d2ff63-e4bf-4868-bfb1-8e50bce1a227 failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:38:43.812: FAIL: Unexpected error:

        <*errors.errorString | 0xc0002c8290>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 25 lines ...
    • Failure [608.184 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/framework.go:23
      should provide DNS for pods for Hostname [LinuxOnly] [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
      Sep 21 11:38:43.812: Unexpected error:

          <*errors.errorString | 0xc0002c8290>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:463
    ------------------------------
    {"msg":"FAILED [sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","total":-1,"completed":17,"skipped":367,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:38:38.384: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename replication-controller
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:48.452: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-9780" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","total":-1,"completed":18,"skipped":367,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should delete RS created by deployment when not orphaning [Conformance]","total":-1,"completed":27,"skipped":509,"failed":0}

    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:38:38.340: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename resourcequota
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 10 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:49.414: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-3165" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replication controller. [Conformance]","total":-1,"completed":28,"skipped":509,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-instrumentation] Events
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 15 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:49.506: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-1600" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-instrumentation] Events should delete a collection of events [Conformance]","total":-1,"completed":29,"skipped":518,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-node] Kubelet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 10 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:53.567: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubelet-test-3468" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Kubelet when scheduling a busybox command that always fails in a pod should have an terminated reason [NodeConformance] [Conformance]","total":-1,"completed":30,"skipped":521,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-apps] ReplicaSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 34 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:38:58.649: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replicaset-8031" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicaSet should validate Replicaset Status endpoints [Conformance]","total":-1,"completed":31,"skipped":522,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 17 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:39:01.227: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-1617" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should be updated [NodeConformance] [Conformance]","total":-1,"completed":32,"skipped":523,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 7 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:39:01.821: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "custom-resource-definition-7967" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition getting/updating/patching custom resource definition status sub-resource works  [Conformance]","total":-1,"completed":33,"skipped":540,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 20 lines ...
    STEP: Destroying namespace "services-774" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should test the lifecycle of an Endpoint [Conformance]","total":-1,"completed":34,"skipped":543,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] server version
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:39:01.938: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "server-version-1973" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] server version should find the server version [Conformance]","total":-1,"completed":35,"skipped":550,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 19 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:40:05.094: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-watch-4725" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin] CustomResourceDefinition Watch watch on custom resource definition objects [Conformance]","total":-1,"completed":36,"skipped":567,"failed":0}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Kubelet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 10 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:40:07.182: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubelet-test-5715" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Kubelet when scheduling a busybox Pod with hostAliases should write entries to /etc/hosts [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":37,"skipped":585,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 65 lines ...
    STEP: Destroying namespace "services-9837" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly] [Conformance]","total":-1,"completed":38,"skipped":589,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 10 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:40:40.699: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-9250" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap binary data should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":39,"skipped":594,"failed":0}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 36 lines ...
    Sep 21 11:31:03.240: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:03.243: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:03.246: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:03.249: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:03.251: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:03.255: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:03.255: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-740 wheezy_tcp@dns-test-service.dns-740 wheezy_udp@dns-test-service.dns-740.svc wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740 jessie_udp@dns-test-service.dns-740.svc jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:08.262: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:08.269: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:08.275: INFO: Unable to read wheezy_udp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:08.279: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:08.283: INFO: Unable to read wheezy_udp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 17 lines ...
    Sep 21 11:31:08.351: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:08.356: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:08.360: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:08.367: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:08.370: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:08.374: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:08.374: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-740 wheezy_tcp@dns-test-service.dns-740 wheezy_udp@dns-test-service.dns-740.svc wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740 jessie_udp@dns-test-service.dns-740.svc jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:13.259: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:13.263: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:13.266: INFO: Unable to read wheezy_udp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:13.268: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:13.271: INFO: Unable to read wheezy_udp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 16 lines ...
    Sep 21 11:31:13.329: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:13.331: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:13.334: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:13.336: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:13.339: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:13.341: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:13.341: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-740 wheezy_tcp@dns-test-service.dns-740 wheezy_udp@dns-test-service.dns-740.svc wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_udp@dns-test-service.dns-740.svc jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:18.259: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:18.262: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:18.265: INFO: Unable to read wheezy_udp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:18.267: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:18.270: INFO: Unable to read wheezy_udp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 16 lines ...
    Sep 21 11:31:18.322: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:18.324: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:18.327: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:18.330: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:18.334: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:18.337: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:18.337: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-740 wheezy_tcp@dns-test-service.dns-740 wheezy_udp@dns-test-service.dns-740.svc wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_udp@dns-test-service.dns-740.svc jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:23.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:23.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:23.267: INFO: Unable to read wheezy_udp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:23.271: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:23.273: INFO: Unable to read wheezy_udp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 16 lines ...
    Sep 21 11:31:23.325: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:23.327: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:23.330: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:23.334: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:23.338: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:23.342: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:23.342: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-740 wheezy_tcp@dns-test-service.dns-740 wheezy_udp@dns-test-service.dns-740.svc wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_udp@dns-test-service.dns-740.svc jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:28.262: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:28.265: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:28.268: INFO: Unable to read wheezy_udp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:28.272: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:28.275: INFO: Unable to read wheezy_udp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 16 lines ...
    Sep 21 11:31:28.321: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:28.324: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:28.327: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:28.330: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:28.333: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:28.336: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:28.336: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-740 wheezy_tcp@dns-test-service.dns-740 wheezy_udp@dns-test-service.dns-740.svc wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_udp@dns-test-service.dns-740.svc jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:33.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:33.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:33.271: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:33.274: INFO: Unable to read wheezy_udp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:33.277: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 15 lines ...
    Sep 21 11:31:33.321: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:33.324: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:33.326: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:33.328: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:33.331: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:33.333: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:33.333: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740 wheezy_udp@dns-test-service.dns-740.svc wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_udp@dns-test-service.dns-740.svc jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:38.259: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:38.262: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:38.268: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:38.271: INFO: Unable to read wheezy_udp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:38.274: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 15 lines ...
    Sep 21 11:31:38.331: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:38.334: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:38.337: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:38.340: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:38.343: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:38.345: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:38.345: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740 wheezy_udp@dns-test-service.dns-740.svc wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_udp@dns-test-service.dns-740.svc jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:43.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:43.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:43.270: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:43.272: INFO: Unable to read wheezy_udp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:43.275: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 14 lines ...
    Sep 21 11:31:43.320: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:43.323: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:43.326: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:43.329: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:43.331: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:43.340: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:43.340: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740 wheezy_udp@dns-test-service.dns-740.svc wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:48.260: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:48.263: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:48.274: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:48.276: INFO: Unable to read wheezy_udp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:48.279: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 14 lines ...
    Sep 21 11:31:48.322: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:48.324: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:48.327: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:48.329: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:48.332: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:48.334: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:48.334: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740 wheezy_udp@dns-test-service.dns-740.svc wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:53.258: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:53.261: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:53.272: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:53.274: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:53.277: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 12 lines ...
    Sep 21 11:31:53.317: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:53.319: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:53.321: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:53.324: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:53.327: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:53.329: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:53.329: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:31:58.259: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:58.262: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:58.274: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:58.276: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:58.279: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 12 lines ...
    Sep 21 11:31:58.317: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:58.320: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:58.323: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:58.325: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:58.327: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:58.330: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:31:58.330: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_udp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:03.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:03.265: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:03.278: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:03.281: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:03.284: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 11 lines ...
    Sep 21 11:32:03.329: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:03.332: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:03.335: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:03.338: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:03.340: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:03.343: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:03.343: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:08.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:08.265: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:08.277: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:08.280: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:08.282: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 11 lines ...
    Sep 21 11:32:08.320: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:08.323: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:08.326: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:08.328: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:08.330: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:08.333: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:08.333: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_udp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:13.262: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:13.265: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:13.276: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:13.279: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:13.282: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 10 lines ...
    Sep 21 11:32:13.319: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:13.324: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:13.327: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:13.329: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:13.332: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:13.334: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:13.334: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:18.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:18.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:18.274: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:18.277: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:18.279: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 10 lines ...
    Sep 21 11:32:18.316: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:18.322: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:18.325: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:18.327: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:18.330: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:18.333: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:18.333: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_udp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:23.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:23.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:23.277: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:23.283: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:23.285: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 9 lines ...
    Sep 21 11:32:23.322: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:23.327: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:23.330: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:23.332: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:23.335: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:23.337: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:23.337: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:28.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:28.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:28.275: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:28.280: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:28.283: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 9 lines ...
    Sep 21 11:32:28.316: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:28.321: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:28.323: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:28.325: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:28.328: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:28.330: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:28.330: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:33.260: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:33.263: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:33.275: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:33.280: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:33.283: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 9 lines ...
    Sep 21 11:32:33.318: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:33.323: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:33.325: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:33.328: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:33.331: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:33.333: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:33.333: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:38.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:38.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:38.277: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:38.282: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:38.285: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 9 lines ...
    Sep 21 11:32:38.321: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:38.326: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:38.328: INFO: Unable to read jessie_udp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:38.331: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:38.334: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:38.336: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:38.336: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:43.259: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:43.262: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:43.276: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:43.284: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:43.287: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 8 lines ...
    Sep 21 11:32:43.318: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:43.324: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:43.330: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:43.336: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:43.339: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:43.341: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:43.341: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:48.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:48.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:48.275: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:48.282: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:48.284: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 8 lines ...
    Sep 21 11:32:48.313: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:48.317: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:48.322: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:48.327: INFO: Unable to read jessie_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:48.329: INFO: Unable to read 10.132.186.104_udp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:48.331: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:48.331: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_udp@_http._tcp.test-service-2.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc jessie_tcp@PodARecord 10.132.186.104_udp@PTR 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:53.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:53.266: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:53.280: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:53.286: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:53.291: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 4 lines ...
    Sep 21 11:32:53.306: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:53.310: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:53.315: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:53.320: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:53.324: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:53.334: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:53.334: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc 10.132.186.104_tcp@PTR]

    
    Sep 21 11:32:58.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:58.265: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:58.276: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:58.280: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:58.286: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
... skipping 4 lines ...
    Sep 21 11:32:58.302: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:58.308: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:58.314: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:58.320: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:58.327: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:58.338: INFO: Unable to read 10.132.186.104_tcp@PTR from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:32:58.338: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.test-service-2.dns-740.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.186.104_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc 10.132.186.104_tcp@PTR]

    
    Sep 21 11:33:03.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.277: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.284: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.295: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.305: INFO: Unable to read jessie_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.307: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.312: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.317: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.322: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.330: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:03.341: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:08.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:08.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:08.273: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:08.279: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:08.290: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:08.300: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:08.304: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:08.310: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:08.314: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:08.319: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:08.330: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:13.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:13.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:13.277: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:13.282: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:13.294: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:13.314: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:13.320: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:13.327: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:13.332: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:13.337: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:13.349: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:18.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:18.266: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:18.277: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:18.282: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:18.293: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:18.303: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:18.308: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:18.313: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:18.318: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:18.323: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:18.333: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:23.259: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:23.262: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:23.273: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:23.278: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:23.289: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:23.302: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:23.307: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:23.313: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:23.319: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:23.324: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:23.334: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:28.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:28.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:28.277: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:28.282: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:28.293: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:28.303: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:28.308: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:28.313: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:28.318: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:28.324: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:28.335: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:33.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:33.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:33.276: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:33.280: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:33.290: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:33.301: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:33.307: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:33.312: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:33.319: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:33.329: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:33.340: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:38.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:38.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:38.274: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:38.279: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:38.293: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:38.306: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:38.312: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:38.318: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:38.325: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:38.330: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:38.342: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:43.261: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:43.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:43.276: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:43.281: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:43.291: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:43.301: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:43.306: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:43.311: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:43.317: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:43.322: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:43.333: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:48.262: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:48.273: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:48.277: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:48.286: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:48.296: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:48.301: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:48.306: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:48.311: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:48.316: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:48.326: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:53.261: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:53.272: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:53.277: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:53.286: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:53.299: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:53.305: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:53.309: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:53.314: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:53.320: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:53.331: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:33:58.263: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:58.273: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:58.278: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:58.294: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:58.305: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:58.310: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:58.316: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:58.321: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:58.325: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:33:58.336: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:34:03.262: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:03.273: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:03.280: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:03.294: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:03.304: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:03.310: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:03.315: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:03.320: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:03.327: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:03.337: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:34:08.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:08.274: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:08.279: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:08.311: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:08.327: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:08.332: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:08.337: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:08.342: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:08.347: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:08.357: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:34:13.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:13.275: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:13.281: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:13.291: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:13.303: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:13.308: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:13.313: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:13.318: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:13.323: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:13.334: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:34:18.264: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:18.274: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:18.279: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:18.290: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:18.299: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:18.304: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:18.309: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:18.321: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:18.325: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:18.336: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:34:23.270: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:23.300: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:23.314: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:23.336: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:23.360: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:23.372: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:23.385: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:23.398: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:23.414: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:23.445: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:34:28.271: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:28.293: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:28.302: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:28.319: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:28.343: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:28.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:28.361: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:28.371: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:28.381: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:28.401: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:34:33.269: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:33.288: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:33.298: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:33.320: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:33.339: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:33.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:33.361: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:33.370: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:33.383: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:33.404: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc jessie_tcp@_http._tcp.test-service-2.dns-740.svc]

    
    Sep 21 11:34:38.269: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:38.289: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:38.300: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:38.324: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:38.342: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:38.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:38.361: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:38.371: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:38.399: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:34:43.268: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:43.295: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:43.305: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:43.326: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:43.345: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:43.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:43.364: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:43.373: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:43.401: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:34:48.270: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:48.292: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:48.302: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:48.321: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:48.341: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:48.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:48.364: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:48.374: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:48.411: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:34:53.268: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:53.290: INFO: Unable to read wheezy_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:53.302: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:53.326: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:53.353: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:53.365: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:53.378: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:53.388: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:53.420: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-740.svc wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:34:58.272: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:58.309: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:58.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:58.349: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:58.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:58.367: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:58.382: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:34:58.407: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:03.273: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:03.314: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:03.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:03.354: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:03.363: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:03.374: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:03.390: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:03.447: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:08.271: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:08.300: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:08.318: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:08.337: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:08.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:08.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:08.367: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:08.399: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:13.268: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:13.298: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:13.317: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:13.339: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:13.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:13.365: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:13.376: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:13.402: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:18.267: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:18.299: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:18.319: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:18.341: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:18.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:18.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:18.365: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:18.389: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:23.269: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:23.302: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:23.322: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:23.340: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:23.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:23.359: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:23.370: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:23.397: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:28.268: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:28.300: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:28.322: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:28.343: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:28.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:28.364: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:28.374: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:28.401: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:33.270: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:33.305: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:33.328: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:33.347: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:33.357: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:33.366: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:33.378: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:33.402: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:38.267: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:38.305: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:38.326: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:38.346: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:38.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:38.365: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:38.374: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:38.409: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:43.269: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:43.302: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:43.323: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:43.343: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:43.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:43.362: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:43.371: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:43.400: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:48.270: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:48.299: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:48.318: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:48.337: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:48.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:48.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:48.365: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:48.392: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:53.267: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:53.302: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:53.321: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:53.341: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:53.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:53.366: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:53.376: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:53.405: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:35:58.271: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:58.309: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:58.339: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:58.381: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:58.396: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:58.412: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:58.423: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:35:58.460: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:03.274: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:03.314: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:03.337: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:03.358: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:03.369: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:03.381: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:03.390: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:03.420: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:08.267: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:08.304: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:08.321: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:08.337: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:08.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:08.356: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:08.364: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:08.395: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:13.266: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:13.296: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:13.319: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:13.338: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:13.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:13.356: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:13.367: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:13.393: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:18.268: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:18.298: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:18.317: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:18.336: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:18.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:18.357: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:18.365: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:18.394: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:23.270: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:23.308: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:23.326: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:23.346: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:23.356: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:23.372: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:23.385: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:23.415: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:28.301: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:28.327: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:28.348: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:28.359: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:28.368: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:28.377: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:28.409: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:33.299: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:33.319: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:33.339: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:33.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:33.357: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:33.367: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:33.395: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-740.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:38.322: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:38.340: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:38.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:38.364: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:38.375: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:38.407: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:43.319: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:43.339: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:43.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:43.357: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:43.370: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:43.405: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:48.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:48.347: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:48.357: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:48.368: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:48.378: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:48.411: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:53.327: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:53.352: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:53.362: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:53.369: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:53.377: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:53.399: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:36:58.328: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:58.346: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:58.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:58.365: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:58.373: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:36:58.401: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:03.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:03.350: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:03.357: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:03.365: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:03.373: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:03.400: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:08.316: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:08.332: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:08.341: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:08.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:08.363: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:08.384: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:13.324: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:13.340: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:13.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:13.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:13.367: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:13.393: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:18.323: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:18.348: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:18.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:18.366: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:18.377: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:18.407: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:23.324: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:23.342: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:23.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:23.363: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:23.372: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:23.396: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:28.314: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:28.334: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:28.343: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:28.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:28.361: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:28.391: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:33.326: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:33.344: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:33.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:33.362: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:33.371: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:33.406: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:38.311: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:38.336: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:38.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:38.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:38.366: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:38.405: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:43.339: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:43.361: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:43.377: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:43.388: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:43.397: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:43.425: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:48.315: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:48.333: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:48.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:48.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:48.365: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:48.393: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:53.344: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:53.362: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:53.374: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:53.384: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:53.396: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:53.428: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:37:58.319: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:58.346: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:58.357: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:58.369: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:58.379: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:37:58.409: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:03.352: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:03.389: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:03.402: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:03.413: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:03.426: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:03.457: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:08.318: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:08.339: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:08.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:08.368: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:08.379: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:08.409: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:13.338: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:13.362: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:13.373: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:13.383: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:13.390: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:13.416: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:18.291: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:18.303: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:18.310: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:18.315: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:18.321: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:18.338: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:23.291: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:23.303: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:23.307: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:23.313: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:23.318: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:23.334: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:28.289: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:28.300: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:28.305: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:28.310: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:28.315: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:28.331: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:33.290: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:33.304: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:33.310: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:33.317: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:33.322: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:33.340: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:38.295: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:38.308: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:38.317: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:38.323: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:38.330: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:38.358: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:43.299: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:43.311: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:43.316: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:43.322: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:43.328: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:43.351: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:48.292: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:48.302: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:48.307: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:48.312: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:48.318: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:48.336: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:53.289: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:53.300: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:53.307: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:53.312: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:53.317: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:53.332: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc jessie_tcp@_http._tcp.dns-test-service.dns-740.svc]

    
    Sep 21 11:38:58.291: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:58.316: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:58.324: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:58.330: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:38:58.350: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:03.295: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:03.307: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:03.314: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:03.319: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:03.342: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:08.291: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:08.303: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:08.308: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:08.314: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:08.335: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:13.288: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:13.298: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:13.304: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:13.309: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:13.330: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:18.292: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:18.303: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:18.309: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:18.314: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:18.335: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:23.291: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:23.300: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:23.306: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:23.311: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:23.332: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:28.295: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:28.306: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:28.311: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:28.316: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:28.337: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:33.291: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:33.302: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:33.307: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:33.312: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:33.332: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:38.286: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:38.298: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:38.304: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:38.309: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:38.330: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:43.297: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:43.310: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:43.315: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:43.321: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:43.343: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:48.289: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:48.301: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:48.306: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:48.311: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:48.332: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:53.292: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:53.303: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:53.313: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:53.319: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:53.345: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:39:58.290: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:58.303: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:58.307: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:58.312: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:39:58.333: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:03.298: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:03.309: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:03.315: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:03.320: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:03.342: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:08.290: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:08.300: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:08.305: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:08.311: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:08.331: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:13.291: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:13.303: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:13.309: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:13.314: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:13.356: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:18.292: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:18.302: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:18.307: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:18.313: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:18.332: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:23.292: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:23.304: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:23.310: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:23.322: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:23.347: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:28.289: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:28.299: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:28.306: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:28.311: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:28.332: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:33.292: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:33.302: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:33.307: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:33.311: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:33.332: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:38.292: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:38.302: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:38.308: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:38.314: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:38.334: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:43.295: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:43.321: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:43.332: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:43.339: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:43.373: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:48.290: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:48.300: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:48.306: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:48.311: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:48.332: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:53.297: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:53.308: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:53.314: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:53.320: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:53.343: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:40:58.294: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:58.305: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:58.310: INFO: Unable to read jessie_tcp@dns-test-service.dns-740 from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:58.315: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:40:58.335: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-740 jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:41:03.299: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:41:03.321: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:41:03.341: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:41:03.372: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:41:03.392: INFO: Unable to read jessie_tcp@dns-test-service.dns-740.svc from pod dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2: the server could not find the requested resource (get pods dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2)
    Sep 21 11:41:03.562: INFO: Lookups using dns-740/dns-test-ec269362-67b5-4574-a39c-c037dd6be6d2 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-740.svc]

    
    Sep 21 11:41:03.563: FAIL: Unexpected error:

        <*errors.errorString | 0xc000248290>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 26 lines ...
    • Failure [602.696 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/framework.go:23
      should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
      Sep 21 11:41:03.563: Unexpected error:

          <*errors.errorString | 0xc000248290>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
... skipping 163 lines ...
    Sep 21 11:40:42.494: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-2455 create -f -'
    Sep 21 11:40:42.729: INFO: stderr: ""
    Sep 21 11:40:42.729: INFO: stdout: "deployment.apps/agnhost-replica created\n"
    STEP: validating guestbook app
    Sep 21 11:40:42.729: INFO: Waiting for all frontend pods to be Running.
    Sep 21 11:40:47.780: INFO: Waiting for frontend to serve content.
    Sep 21 11:44:22.434: INFO: Failed to get response from guestbook. err: the server is currently unable to handle the request (get services frontend), response: k8s

    
    v1Status�
    
    Failureierror trying to reach service: read tcp 172.18.0.9:41670->192.168.3.23:80: read: connection reset by peer"ServiceUnavailable0�"
    Sep 21 11:44:27.445: INFO: Trying to add a new entry to the guestbook.
    Sep 21 11:44:27.469: INFO: Verifying that added entry can be retrieved.
... skipping 32 lines ...
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/framework.go:23
      Guestbook application
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:339
        should create and stop a working application  [Conformance]
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Guestbook application should create and stop a working application  [Conformance]","total":-1,"completed":40,"skipped":608,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:44:28.282: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] volume on default medium should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test emptydir volume type on node default medium
    Sep 21 11:44:28.333: INFO: Waiting up to 5m0s for pod "pod-3e124c37-a80e-49de-bcff-f59fb9cc36a6" in namespace "emptydir-5441" to be "Succeeded or Failed"

    Sep 21 11:44:28.336: INFO: Pod "pod-3e124c37-a80e-49de-bcff-f59fb9cc36a6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.94732ms
    Sep 21 11:44:30.341: INFO: Pod "pod-3e124c37-a80e-49de-bcff-f59fb9cc36a6": Phase="Running", Reason="", readiness=false. Elapsed: 2.007098819s
    Sep 21 11:44:32.345: INFO: Pod "pod-3e124c37-a80e-49de-bcff-f59fb9cc36a6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.011869901s
    STEP: Saw pod success
    Sep 21 11:44:32.345: INFO: Pod "pod-3e124c37-a80e-49de-bcff-f59fb9cc36a6" satisfied condition "Succeeded or Failed"

    Sep 21 11:44:32.348: INFO: Trying to get logs from node k8s-upgrade-and-conformance-op826y-worker-622wqp pod pod-3e124c37-a80e-49de-bcff-f59fb9cc36a6 container test-container: <nil>
    STEP: delete the pod
    Sep 21 11:44:32.385: INFO: Waiting for pod pod-3e124c37-a80e-49de-bcff-f59fb9cc36a6 to disappear
    Sep 21 11:44:32.389: INFO: Pod pod-3e124c37-a80e-49de-bcff-f59fb9cc36a6 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:44:32.389: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-5441" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes volume on default medium should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":41,"skipped":635,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 24 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:44:38.259: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-2084" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD without validation schema [Conformance]","total":-1,"completed":42,"skipped":650,"failed":0}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 6 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep 21 11:44:38.356: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-1326" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be immutable if `immutable` field is set [Conformance]","total":-1,"completed":43,"skipped":668,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"FAILED [sig-network] DNS should provide DNS for pods for Hostname [LinuxOnly] [Conformance]","total":-1,"completed":14,"skipped":240,"failed":1,"failures":["[sig-network] DNS should provide DNS for pods for Hostname [LinuxOnly] [Conformance]"]}

    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:38:43.870: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename dns
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 7 lines ...
    STEP: creating a pod to probe DNS
    STEP: submitting the pod to kubernetes
    STEP: retrieving the pod
    STEP: looking for the results for each expected name from probers
    Sep 21 11:38:45.951: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:38:45.962: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:38:45.962: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:38:50.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:38:50.984: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:38:50.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:38:55.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:38:55.986: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:38:55.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:00.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:00.984: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:00.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:05.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:05.985: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:05.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:10.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:10.984: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:10.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:15.973: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:15.983: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:15.983: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:20.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:20.984: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:20.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:25.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:25.984: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:25.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:30.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:30.984: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:30.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:35.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:35.985: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:35.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:40.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:40.984: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:40.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:45.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:45.985: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:45.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:50.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:50.994: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:50.994: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:39:55.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:55.985: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:39:55.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:40:00.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:00.988: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:00.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:40:05.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:05.985: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:05.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:40:10.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:10.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:40:15.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:15.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:40:20.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:20.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:40:25.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:25.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:40:30.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:30.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:40:35.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:35.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:40:40.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:40.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:40:45.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:45.991: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:40:50.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:50.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:40:55.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:40:55.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:00.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:00.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:05.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:05.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:10.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:10.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:15.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:15.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:20.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:20.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:25.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:25.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:30.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:30.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:35.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:35.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:40.977: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:40.990: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:45.980: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:45.990: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:50.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:50.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:41:55.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:41:55.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:00.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:00.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:05.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:05.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:10.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:10.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:15.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:15.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:20.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:20.990: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:25.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:25.983: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:30.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:30.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:35.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:35.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:40.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:40.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:45.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:45.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:50.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:50.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:42:55.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:42:55.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:00.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:00.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:05.977: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:05.989: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:10.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:10.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:15.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:15.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:20.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:20.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:25.983: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:26.000: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:30.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:30.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:35.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:35.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:40.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:40.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:45.980: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:45.992: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:50.979: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:50.990: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:43:55.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:43:55.989: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:00.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:00.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:05.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:05.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:10.988: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:11.000: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:15.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:15.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:20.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:20.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:25.977: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:25.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:30.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:30.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:35.977: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:35.989: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:40.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:40.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:45.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:45.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:50.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:50.990: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:44:55.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:44:55.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:00.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:00.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:05.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:05.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:10.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:10.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:15.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:15.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:20.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:20.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:25.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:25.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:30.977: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:30.990: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:35.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:35.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:40.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:40.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:45.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:45.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:50.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:50.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:45:55.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:45:55.989: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:00.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:00.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:05.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:05.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:10.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:10.990: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:15.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:15.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:20.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:20.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:25.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:25.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:30.973: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:30.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:35.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:35.990: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:40.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:40.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:45.983: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:45.993: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:50.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:50.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:46:55.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:46:55.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:00.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:00.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:05.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:05.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:10.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:10.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:15.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:15.984: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:20.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:20.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:25.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:25.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:30.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:30.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:35.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:35.987: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:40.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:40.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:45.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:45.986: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:50.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:50.999: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:47:55.978: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:47:55.989: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:00.977: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:00.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:05.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:05.985: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:10.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:10.988: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:15.977: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:15.994: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:20.985: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:21.006: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:25.986: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:26.002: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:30.983: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:31.002: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:35.983: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:36.002: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:40.985: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:41.007: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:45.989: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:46.011: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:46.028: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b: the server could not find the requested resource (get pods dns-test-2363e86d-6af0-4e66-a436-433c5924e33b)
    Sep 21 11:48:46.047: INFO: Lookups using dns-9786/dns-test-2363e86d-6af0-4e66-a436-433c5924e33b failed for: [wheezy_tcp@PodARecord]

    
    Sep 21 11:48:46.048: FAIL: Unexpected error:

        <*errors.errorString | 0xc0002c8290>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 25 lines ...
    • Failure [602.316 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/framework.go:23
      should provide DNS for pods for Hostname [LinuxOnly] [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
      Sep 21 11:48:46.048: Unexpected error:

          <*errors.errorString | 0xc0002c8290>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:463
    ------------------------------
    {"msg":"FAILED [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]","total":-1,"completed":17,"skipped":387,"failed":2,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]","[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}

    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:41:03.823: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename dns
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 33 lines ...
    Sep 21 11:41:05.959: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:05.962: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:05.965: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:05.968: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:05.970: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:05.973: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:05.973: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-7371 wheezy_tcp@dns-test-service.dns-7371 wheezy_udp@dns-test-service.dns-7371.svc wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_udp@dns-test-service.dns-7371.svc jessie_tcp@dns-test-service.dns-7371.svc jessie_udp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:41:10.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:10.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:10.982: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:10.985: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:10.987: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 17 lines ...
    Sep 21 11:41:11.034: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:11.037: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:11.039: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:11.042: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:11.044: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:11.046: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:11.046: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-7371 wheezy_tcp@dns-test-service.dns-7371 wheezy_udp@dns-test-service.dns-7371.svc wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_udp@dns-test-service.dns-7371.svc jessie_tcp@dns-test-service.dns-7371.svc jessie_udp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:41:15.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:15.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:15.982: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:15.985: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:15.988: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 17 lines ...
    Sep 21 11:41:16.033: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:16.036: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:16.038: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:16.041: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:16.043: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:16.046: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:16.046: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-7371 wheezy_tcp@dns-test-service.dns-7371 wheezy_udp@dns-test-service.dns-7371.svc wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_udp@dns-test-service.dns-7371.svc jessie_tcp@dns-test-service.dns-7371.svc jessie_udp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:41:20.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:20.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:20.983: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:20.986: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:20.988: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 17 lines ...
    Sep 21 11:41:21.036: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:21.038: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:21.041: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:21.043: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:21.046: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:21.048: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:21.048: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-7371 wheezy_tcp@dns-test-service.dns-7371 wheezy_udp@dns-test-service.dns-7371.svc wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_udp@dns-test-service.dns-7371.svc jessie_tcp@dns-test-service.dns-7371.svc jessie_udp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:41:25.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:25.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:25.982: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:25.984: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:25.987: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 17 lines ...
    Sep 21 11:41:26.038: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:26.041: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:26.043: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:26.045: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:26.048: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:26.050: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:26.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-7371 wheezy_tcp@dns-test-service.dns-7371 wheezy_udp@dns-test-service.dns-7371.svc wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_udp@dns-test-service.dns-7371.svc jessie_tcp@dns-test-service.dns-7371.svc jessie_udp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:41:30.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:30.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:30.983: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:30.986: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:30.988: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 17 lines ...
    Sep 21 11:41:31.064: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:31.067: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:31.069: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:31.071: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:31.074: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:31.077: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:31.077: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-7371 wheezy_tcp@dns-test-service.dns-7371 wheezy_udp@dns-test-service.dns-7371.svc wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_udp@dns-test-service.dns-7371.svc jessie_tcp@dns-test-service.dns-7371.svc jessie_udp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:41:35.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:35.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:35.988: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:35.991: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:35.993: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 16 lines ...
    Sep 21 11:41:36.040: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:36.042: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:36.045: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:36.047: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:36.049: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:36.051: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:36.051: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371 wheezy_udp@dns-test-service.dns-7371.svc wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_udp@dns-test-service.dns-7371.svc jessie_tcp@dns-test-service.dns-7371.svc jessie_udp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:41:40.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:40.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:40.986: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:40.988: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:40.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 16 lines ...
    Sep 21 11:41:41.039: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:41.042: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:41.044: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:41.046: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:41.048: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:41.051: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:41.051: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371 wheezy_udp@dns-test-service.dns-7371.svc wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_udp@dns-test-service.dns-7371.svc jessie_tcp@dns-test-service.dns-7371.svc jessie_udp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:41:45.978: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:45.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:45.987: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:45.990: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:45.992: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 13 lines ...
    Sep 21 11:41:46.036: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:46.039: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:46.041: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:46.044: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:46.046: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:46.049: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:46.049: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371 wheezy_udp@dns-test-service.dns-7371.svc wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:41:50.976: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:50.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:50.984: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:50.988: INFO: Unable to read wheezy_udp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:50.993: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 13 lines ...
    Sep 21 11:41:51.038: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:51.040: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:51.042: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:51.045: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:51.047: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:51.050: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:51.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371 wheezy_udp@dns-test-service.dns-7371.svc wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:41:55.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:55.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:56.001: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:56.003: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:56.006: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 11 lines ...
    Sep 21 11:41:56.045: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:56.047: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:56.050: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:56.052: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:56.054: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:56.058: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:41:56.058: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:42:00.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:00.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:00.992: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:00.995: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:00.998: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 11 lines ...
    Sep 21 11:42:01.035: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:01.038: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:01.040: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:01.043: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:01.046: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:01.048: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:01.048: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_udp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:42:05.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:05.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:05.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:05.993: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:05.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 10 lines ...
    Sep 21 11:42:06.034: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:06.039: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:06.042: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:06.044: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:06.046: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:06.049: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:06.049: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:42:10.979: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:10.983: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:10.994: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:10.997: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:10.999: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 10 lines ...
    Sep 21 11:42:11.038: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:11.043: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:11.047: INFO: Unable to read jessie_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:11.050: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:11.052: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:11.055: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:11.055: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:42:15.976: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:15.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:15.989: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:15.991: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:15.994: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 9 lines ...
    Sep 21 11:42:16.019: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:16.028: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:16.033: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:16.039: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:16.041: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:16.044: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:16.044: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:42:20.982: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:20.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:20.995: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:20.998: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:21.001: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 9 lines ...
    Sep 21 11:42:21.026: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:21.038: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:21.044: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:21.049: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:21.052: INFO: Unable to read 10.135.24.158_udp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:21.055: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:21.055: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc jessie_tcp@PodARecord 10.135.24.158_udp@PTR 10.135.24.158_tcp@PTR]

    
    Sep 21 11:42:25.976: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:25.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:25.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:25.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:25.997: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 5 lines ...
    Sep 21 11:42:26.015: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:26.017: INFO: Unable to read jessie_udp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:26.019: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:26.028: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:26.033: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:26.043: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:26.043: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc 10.135.24.158_tcp@PTR]

    
    Sep 21 11:42:30.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:30.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:30.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:30.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:30.998: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 5 lines ...
    Sep 21 11:42:31.017: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:31.019: INFO: Unable to read jessie_udp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:31.022: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:31.032: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:31.038: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:31.051: INFO: Unable to read 10.135.24.158_tcp@PTR from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:31.051: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.24.158_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc 10.135.24.158_tcp@PTR]

    
    Sep 21 11:42:35.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:35.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:35.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:35.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:35.998: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 3 lines ...
    Sep 21 11:42:36.012: INFO: Unable to read jessie_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:36.015: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:36.017: INFO: Unable to read jessie_udp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:36.019: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:36.029: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:36.034: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:36.044: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:42:40.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:40.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:40.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:40.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:40.997: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 2 lines ...
    Sep 21 11:42:41.007: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:41.018: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:41.020: INFO: Unable to read jessie_udp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:41.022: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:41.032: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:41.037: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:41.046: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:42:45.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:45.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:45.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:45.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:45.997: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
... skipping 2 lines ...
    Sep 21 11:42:46.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:46.016: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:46.018: INFO: Unable to read jessie_udp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:46.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:46.031: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:46.036: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:46.049: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-7371 jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:42:50.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:50.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:50.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:50.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:51.001: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:51.004: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:51.006: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:51.009: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:51.020: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:51.026: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:51.035: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:51.040: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:51.049: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_udp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:42:55.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:55.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:55.994: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:56.000: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:56.004: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:56.007: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:56.009: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:56.019: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:56.025: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:56.035: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:56.040: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:42:56.051: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:00.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:00.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:00.989: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:00.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:01.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:01.002: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:01.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:01.017: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:01.022: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:01.032: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:01.037: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:01.048: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:05.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:05.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:05.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:05.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:06.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:06.004: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:06.007: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:06.017: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:06.023: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:06.033: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:06.039: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:06.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:10.978: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:10.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:10.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:10.994: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:10.999: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:11.001: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:11.003: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:11.013: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:11.018: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:11.028: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:11.033: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:11.044: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:15.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:15.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:15.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:15.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:16.003: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:16.005: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:16.008: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:16.019: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:16.024: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:16.034: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:16.040: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:16.051: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:20.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:20.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:20.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:20.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:21.002: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:21.004: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:21.008: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:21.018: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:21.023: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:21.033: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:21.040: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:21.049: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:25.978: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:25.983: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:26.000: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:26.009: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:26.017: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:26.024: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:26.040: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:26.048: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:26.069: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:26.079: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:26.095: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:30.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:30.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:30.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:30.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:31.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:31.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:31.016: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:31.022: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:31.032: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:31.038: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:31.047: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:35.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:35.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:35.989: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:35.994: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:35.998: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:36.004: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:36.014: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:36.020: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:36.030: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:36.036: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:36.047: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:40.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:40.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:40.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:40.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:41.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:41.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:41.017: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:41.023: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:41.034: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:41.039: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:41.056: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:45.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:45.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:45.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:45.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:46.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:46.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:46.017: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:46.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:46.031: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:46.037: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:46.047: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:50.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:50.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:50.992: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:50.997: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:51.003: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:51.008: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:51.020: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:51.026: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:51.037: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:51.044: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:51.056: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:43:55.980: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:55.986: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:55.998: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:56.003: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:56.009: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:56.013: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:56.024: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:56.029: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:56.040: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:56.045: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:43:56.055: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:00.979: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:00.982: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:00.995: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:01.000: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:01.007: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:01.013: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:01.024: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:01.029: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:01.040: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:01.045: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:01.058: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:05.977: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:05.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:05.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:05.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:06.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:06.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:06.015: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:06.020: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:06.032: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:06.037: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:06.047: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:10.983: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:10.996: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:11.002: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:11.009: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:11.021: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:11.036: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:11.047: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:11.052: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:11.063: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:15.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:15.989: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:15.994: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:16.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:16.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:16.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:16.031: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:16.036: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:16.047: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:20.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:20.993: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:20.999: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:21.004: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:21.009: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:21.024: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:21.036: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:21.042: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:21.053: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:25.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:25.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:25.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:26.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:26.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:26.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:26.031: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:26.035: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:26.046: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:30.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:30.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:30.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:31.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:31.007: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:31.026: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:31.039: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:31.044: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:31.055: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:35.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:35.994: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:36.000: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:36.006: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:36.012: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:36.028: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:36.040: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:36.045: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:36.055: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:40.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:40.992: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:40.997: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:41.002: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:41.008: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:41.024: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:41.034: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:41.039: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:41.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:45.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:45.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:45.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:46.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:46.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:46.022: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:46.031: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:46.036: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:46.046: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:50.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:50.993: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:50.999: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:51.005: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:51.010: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:51.028: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:51.038: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:51.043: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:51.054: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:44:55.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:55.992: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:55.997: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:56.002: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:56.007: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:56.023: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:56.034: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:56.041: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:44:56.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:00.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:00.989: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:00.994: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:00.999: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:01.004: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:01.023: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:01.034: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:01.039: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:01.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:05.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:05.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:05.997: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:06.003: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:06.008: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:06.023: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:06.034: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:06.038: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:06.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:10.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:10.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:10.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:11.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:11.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:11.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:11.031: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:11.036: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:11.049: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:15.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:15.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:15.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:16.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:16.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:16.020: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:16.029: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:16.036: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:16.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:20.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:20.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:20.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:21.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:21.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:21.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:21.029: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:21.033: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:21.043: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:25.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:25.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:25.997: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:26.002: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:26.007: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:26.022: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:26.032: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:26.038: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:26.048: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:30.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:30.994: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:31.000: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:31.006: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:31.011: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:31.027: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:31.037: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:31.042: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:31.052: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:35.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:35.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:35.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:36.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:36.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:36.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:36.032: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:36.037: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:36.046: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:40.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:40.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:40.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:41.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:41.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:41.022: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:41.033: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:41.038: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:41.048: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:45.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:45.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:45.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:46.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:46.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:46.020: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:46.030: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:46.035: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:46.045: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:50.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:50.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:50.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:51.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:51.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:51.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:51.034: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:51.039: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:51.048: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:45:55.982: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:55.994: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:55.999: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:56.004: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:56.009: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:56.026: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:56.039: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:56.044: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:45:56.055: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:00.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:00.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:00.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:01.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:01.008: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:01.024: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:01.035: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:01.040: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:01.051: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:05.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:05.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:05.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:06.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:06.004: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:06.022: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:06.035: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:06.040: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:06.049: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:10.984: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:10.996: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:11.000: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:11.005: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:11.011: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:11.026: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:11.037: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:11.042: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:11.051: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:15.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:15.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:15.997: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:16.002: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:16.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:16.022: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:16.043: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:16.051: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:16.071: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:20.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:20.992: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:20.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:21.002: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:21.007: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:21.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:21.034: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:21.039: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:21.049: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:25.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:25.989: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:25.994: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:25.999: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:26.003: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:26.020: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:26.030: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:26.037: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:26.048: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:30.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:30.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:30.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:31.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:31.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:31.020: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:31.030: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:31.035: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:31.045: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:35.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:35.992: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:35.997: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:36.002: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:36.007: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:36.024: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:36.035: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:36.043: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:36.054: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:40.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:40.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:40.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:41.002: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:41.008: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:41.023: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:41.037: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:41.043: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:41.053: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:45.983: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:45.993: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:45.998: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:46.003: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:46.009: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:46.025: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:46.036: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:46.041: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:46.051: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:50.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:50.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:50.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:51.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:51.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:51.020: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:51.030: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:51.035: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:51.045: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:46:55.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:55.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:55.994: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:55.998: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:56.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:56.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:56.031: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:56.037: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:46:56.047: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:00.978: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:00.988: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:00.993: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:00.998: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:01.007: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:01.025: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:01.035: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:01.040: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:01.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:05.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:05.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:05.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:06.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:06.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:06.023: INFO: Unable to read jessie_tcp@dns-test-service.dns-7371 from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:06.032: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:06.038: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:06.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-7371 jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:10.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:10.991: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:10.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:11.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:11.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:11.033: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:11.038: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:11.046: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:15.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:15.989: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:15.994: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:15.999: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:16.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:16.028: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:16.033: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:16.042: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:20.979: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:20.989: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:20.994: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:21.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:21.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:21.030: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:21.036: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:21.048: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:25.981: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:25.993: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:25.998: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:26.003: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:26.008: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:26.033: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:26.039: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:26.048: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:30.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:30.990: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:30.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:31.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:31.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:31.030: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:31.034: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:31.046: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:35.982: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:35.997: INFO: Unable to read wheezy_tcp@dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:36.003: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:36.008: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:36.012: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:36.038: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:36.043: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:36.053: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:40.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:40.996: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:41.001: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:41.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:41.031: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:41.036: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:41.046: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:45.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:45.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:46.005: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:46.011: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:46.037: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:46.041: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:46.052: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:50.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:51.016: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:51.022: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:51.027: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:51.052: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:51.057: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:51.070: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:47:55.982: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:55.997: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:56.003: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:56.010: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:56.044: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:56.050: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:47:56.060: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:00.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:00.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:01.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:01.005: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:01.034: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:01.040: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:01.049: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:05.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:05.995: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:06.000: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:06.006: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:06.031: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:06.036: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:06.051: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@_http._tcp.test-service-2.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:10.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:10.997: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:11.007: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:11.033: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:11.038: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:11.050: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:15.980: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:16.002: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:16.012: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:16.038: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:16.043: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:16.053: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:20.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:21.017: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:21.046: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:21.107: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:21.121: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:21.137: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:25.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:26.011: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:26.029: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:26.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:26.090: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:26.112: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:30.983: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:31.014: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:31.032: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:31.090: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:31.099: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:31.121: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:35.984: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:36.014: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:36.032: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:36.079: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:36.090: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:36.113: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:40.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:41.015: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:41.033: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:41.086: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:41.096: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:41.111: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:45.984: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:46.014: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:46.034: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:46.178: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:46.208: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:46.255: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:50.988: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:51.025: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:51.045: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:51.092: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:51.109: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:51.130: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:48:55.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:56.022: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:56.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:56.099: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:56.110: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:48:56.129: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:00.986: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:01.018: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:01.045: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:01.103: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:01.111: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:01.132: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:05.987: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:06.016: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:06.039: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:06.101: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:06.111: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:06.133: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:10.988: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:11.018: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:11.042: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:11.096: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:11.107: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:11.127: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:15.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:16.019: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:16.037: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:16.094: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:16.104: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:16.126: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:20.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:21.014: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:21.038: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:21.087: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:21.096: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:21.117: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:25.986: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:26.015: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:26.039: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:26.093: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:26.103: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:26.126: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:30.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:31.014: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:31.038: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:31.101: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:31.113: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:31.134: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:35.986: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:36.014: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:36.033: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:36.083: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:36.092: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:36.111: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:40.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:41.016: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:41.037: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:41.090: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:41.103: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:41.125: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:45.987: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:46.014: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:46.035: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:46.087: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:46.098: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:46.122: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:50.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:51.091: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:51.117: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:51.170: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:51.180: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:51.205: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:49:55.986: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:56.021: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:56.043: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:56.094: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:56.107: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:49:56.130: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:00.987: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:01.021: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:01.039: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:01.088: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:01.099: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:01.119: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:05.989: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:06.019: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:06.038: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:06.093: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:06.105: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:06.128: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:10.988: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:11.026: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:11.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:11.098: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:11.110: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:11.135: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:15.986: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:16.020: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:16.040: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:16.099: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:16.108: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:16.130: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:20.986: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:21.017: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:21.036: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:21.085: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:21.097: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:21.121: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:25.987: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:26.019: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:26.042: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:26.098: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:26.108: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:26.130: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-7371.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:30.986: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:31.039: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:31.101: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:31.111: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:31.127: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:35.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:36.039: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:36.102: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:36.113: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:36.129: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:40.986: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:41.035: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:41.097: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:41.107: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:41.128: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:45.985: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:46.032: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:46.081: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:46.090: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:46.108: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:50.986: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:51.036: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:51.081: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:51.090: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:51.114: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:50:55.987: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:56.034: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:56.080: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:56.090: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:50:56.109: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:51:00.989: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:01.054: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:01.108: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:01.119: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:01.137: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:51:05.987: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:06.032: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:06.086: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:06.096: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:06.116: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:51:06.126: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:06.171: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:06.222: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:06.230: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-7371.svc from pod dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5: the server could not find the requested resource (get pods dns-test-eae3627f-66b3-4684-9344-6439154a3ca5)
    Sep 21 11:51:06.280: INFO: Lookups using dns-7371/dns-test-eae3627f-66b3-4684-9344-6439154a3ca5 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-7371.svc jessie_tcp@_http._tcp.test-service-2.dns-7371.svc]

    
    Sep 21 11:51:06.280: FAIL: Unexpected error:

        <*errors.errorString | 0xc000248290>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 26 lines ...
    • Failure [602.713 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/framework.go:23
      should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
      Sep 21 11:51:06.280: Unexpected error:

          <*errors.errorString | 0xc000248290>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
... skipping 25 lines ...
    Sep 21 11:44:40.504: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:40.507: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:40.510: INFO: Unable to read jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:40.513: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:40.516: INFO: Unable to read jessie_udp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:40.519: INFO: Unable to read jessie_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:40.519: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_udp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:44:45.523: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.529: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.535: INFO: Unable to read wheezy_udp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.540: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.543: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.546: INFO: Unable to read jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.549: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.552: INFO: Unable to read jessie_udp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.556: INFO: Unable to read jessie_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:45.556: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_udp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

    
    Sep 21 11:44:50.523: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:50.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:50.539: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:50.542: INFO: Unable to read wheezy_udp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:50.546: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:50.548: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:50.551: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:50.555: INFO: Unable to read jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:50.558: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:50.563: INFO: Unable to read jessie_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:50.563: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@PodARecord]

    
    Sep 21 11:44:55.524: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:55.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:55.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:55.535: INFO: Unable to read wheezy_udp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:55.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:55.540: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:55.543: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:55.545: INFO: Unable to read jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:55.547: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:55.552: INFO: Unable to read jessie_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:44:55.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@PodARecord]

    
    Sep 21 11:45:00.524: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:00.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:00.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:00.535: INFO: Unable to read wheezy_udp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:00.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:00.541: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:00.544: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:00.547: INFO: Unable to read jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:00.549: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:00.555: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:45:05.524: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:05.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:05.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:05.535: INFO: Unable to read wheezy_udp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:05.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:05.540: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:05.543: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:05.545: INFO: Unable to read jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:05.549: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:05.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:45:10.524: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:10.528: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:10.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:10.536: INFO: Unable to read wheezy_udp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:10.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:10.541: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:10.543: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:10.545: INFO: Unable to read jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:10.548: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:10.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_udp@dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:45:15.523: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:15.526: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:15.531: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:15.535: INFO: Unable to read wheezy_udp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:15.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:15.540: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:15.547: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:15.552: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:45:20.523: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:20.526: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:20.531: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:20.536: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:20.538: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:20.546: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:20.551: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local jessie_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:45:25.524: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:25.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:25.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:25.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:25.539: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:25.552: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:45:30.523: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:30.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:30.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:30.539: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:30.542: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:30.563: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord jessie_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:45:35.523: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:35.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:35.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:35.539: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:35.556: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:45:40.524: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:40.528: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:40.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:40.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:40.554: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:45:45.524: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:45.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:45.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:45.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:45.554: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:45:50.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:50.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:50.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:50.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:45:55.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:55.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:55.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:45:55.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:00.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:00.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:00.539: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:00.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:05.527: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:05.534: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:05.541: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:05.557: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-querier-2.dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:10.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:10.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:10.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:15.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:15.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:15.552: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:20.534: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:20.539: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:20.557: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:25.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:25.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:25.557: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:30.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:30.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:30.555: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:35.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:35.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:35.551: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:40.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:40.539: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:40.557: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:45.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:45.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:45.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:50.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:50.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:50.555: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:46:55.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:55.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:46:55.552: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:00.531: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:00.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:00.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:05.531: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:05.536: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:05.559: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:10.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:10.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:10.554: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:15.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:15.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:15.552: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:20.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:20.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:20.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:25.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:25.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:25.552: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:30.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:30.536: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:30.550: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:35.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:35.539: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:35.554: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:40.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:40.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:40.552: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:45.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:45.537: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:45.552: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:50.534: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:50.540: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:50.555: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:47:55.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:55.539: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:47:55.554: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:00.534: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:00.539: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:00.556: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:05.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:05.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:05.554: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:10.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:10.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:10.554: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:15.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:15.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:15.551: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:20.551: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:20.565: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:20.602: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:25.548: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:25.557: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:25.585: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:30.544: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:30.556: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:30.588: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:35.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:35.551: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:35.616: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:40.545: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:40.555: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:40.585: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:45.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:45.552: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:45.587: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:50.540: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:50.558: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:50.589: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:48:55.543: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:55.556: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:48:55.596: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:49:00.548: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:00.559: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:00.610: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:49:05.550: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:05.560: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:05.602: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:49:10.553: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:10.565: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:10.621: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:49:15.543: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:15.554: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:15.584: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:49:20.545: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:20.553: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:20.595: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:49:25.540: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:25.550: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:25.584: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:49:30.544: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:30.556: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:30.600: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep 21 11:49:35.544: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:35.590: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:49:40.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:40.600: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:49:45.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:45.582: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:49:50.540: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:50.588: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:49:55.539: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:49:55.576: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:00.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:00.584: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:05.544: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:05.588: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:10.538: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:10.590: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:15.543: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:15.588: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:20.549: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:20.599: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:25.548: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:25.585: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:30.541: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:30.588: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:35.588: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:35.625: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:40.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:40.588: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:45.541: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:45.584: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:50.543: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:50.598: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:50:55.543: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:50:55.582: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:00.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:00.586: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:05.538: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:05.580: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:10.538: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:10.584: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:15.541: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:15.580: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:20.538: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:20.578: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:25.546: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:25.589: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:30.544: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:30.586: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:35.543: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:35.582: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:40.543: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:40.584: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:45.539: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:45.573: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:50.545: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:50.579: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:51:55.537: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:51:55.574: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:00.544: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:00.589: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:05.541: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:05.579: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:10.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:10.593: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:15.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:15.587: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:20.545: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:20.601: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:25.550: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:25.587: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:30.541: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:30.595: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:35.539: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:35.578: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:40.544: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:40.594: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:45.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:45.578: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:50.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:50.598: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:52:55.541: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:52:55.584: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:00.540: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:00.577: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:05.543: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:05.581: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:10.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:10.582: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:15.544: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:15.581: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:20.543: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:20.582: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:25.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:25.580: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:30.542: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:30.595: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:35.545: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:35.593: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:40.549: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:40.592: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:45.543: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:45.587: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:50.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:50.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:53:55.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:53:55.554: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:00.531: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:54:00.572: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:05.532: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:54:05.554: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:10.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:54:10.552: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:15.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:54:15.554: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:20.534: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:54:20.557: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:25.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:54:25.558: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:30.533: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:54:30.553: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:35.534: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:54:35.559: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:40.535: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:54:40.558: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:40.570: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local from pod dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298: the server could not find the requested resource (get pods dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298)
    Sep 21 11:54:40.593: INFO: Lookups using dns-4978/dns-test-ac362ea6-18a2-482a-a1a5-a6a9fe479298 failed for: [wheezy_tcp@dns-test-service-2.dns-4978.svc.cluster.local]

    
    Sep 21 11:54:40.594: FAIL: Unexpected error:

        <*errors.errorString | 0xc000244280>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 25 lines ...
    • Failure [602.250 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/framework.go:23
      should provide DNS for pods for Subdomain [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
      Sep 21 11:54:40.594: Unexpected error:

          <*errors.errorString | 0xc000244280>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:463
    ------------------------------
    {"msg":"FAILED [sig-network] DNS should provide DNS for pods for Subdomain [Conformance]","total":-1,"completed":43,"skipped":717,"failed":1,"failures":["[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]"]}

    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep 21 11:54:40.690: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename dns
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 13 lines ...
    Sep 21 11:54:48.782: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:48.785: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:48.794: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:48.801: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:48.804: INFO: Unable to read jessie_udp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:48.807: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:48.812: INFO: Lookups using dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local wheezy_udp@dns-test-service-2.dns-7211.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-7211.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local jessie_udp@dns-test-service-2.dns-7211.svc.cluster.local jessie_tcp@dns-test-service-2.dns-7211.svc.cluster.local]

    
    Sep 21 11:54:53.818: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:53.821: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:53.824: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:53.826: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:53.833: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:53.836: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:53.838: INFO: Unable to read jessie_udp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:53.841: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:53.846: INFO: Lookups using dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local wheezy_udp@dns-test-service-2.dns-7211.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-7211.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local jessie_udp@dns-test-service-2.dns-7211.svc.cluster.local jessie_tcp@dns-test-service-2.dns-7211.svc.cluster.local]

    
    Sep 21 11:54:58.819: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:58.822: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:58.825: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:58.828: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:58.836: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:58.840: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:58.843: INFO: Unable to read jessie_udp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:58.845: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:54:58.851: INFO: Lookups using dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local wheezy_udp@dns-test-service-2.dns-7211.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-7211.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local jessie_udp@dns-test-service-2.dns-7211.svc.cluster.local jessie_tcp@dns-test-service-2.dns-7211.svc.cluster.local]

    
    Sep 21 11:55:03.818: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:55:03.821: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:55:03.824: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:55:03.827: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:55:03.835: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:55:03.837: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:55:03.840: INFO: Unable to read jessie_udp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:55:03.843: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-7211.svc.cluster.local from pod dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2: the server could not find the requested resource (get pods dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2)
    Sep 21 11:55:03.848: INFO: Lookups using dns-7211/dns-test-c3268bc5-b0ae-4de7-bdbe-5054292321d2 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local wheezy_udp@dns-test-service-2.dns-7211.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-7211.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-7211.svc.cluster.local jessie_udp@dns-test-service-2.dns-7211.svc.cluster.local jessie_tcp@dns-test-service-2.dns-7211.svc.cluster.local]

    
    Sep 21 11:55:08.817: INFO: Unable to