apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:01:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-28-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-28.ec2.internal uid: 2d1eb4e7-6a4c-4694-a785-e38f09c15c1a resourceVersion: "53863" uid: 1374f178-a0d7-4daf-a0fd-f674757fc0a3 spec: sourcePod: network-check-source-56499946bc-gptgl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T17:08:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.959µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:36:41Z" - latency: 831.182µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:41Z" - latency: 960.437µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:41Z" - latency: 1.20313ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:41Z" - latency: 1.131455ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:41Z" - latency: 1.287016ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:31:41Z" - latency: 1.013663ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:30:41Z" - latency: 770.634µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:29:41Z" - latency: 1.010338ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:28:41Z" - latency: 1.026349ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:27:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:01:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-28-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-28.ec2.internal uid: 2d1eb4e7-6a4c-4694-a785-e38f09c15c1a resourceVersion: "54954" uid: 954b20c9-3040-4551-81c5-dbcd0adecad5 spec: sourcePod: network-check-source-56499946bc-gptgl targetEndpoint: a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T17:07:41Z" message: 'load-balancer-api-external: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.514433ms message: 'load-balancer-api-external: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:37:41Z" - latency: 8.531738ms message: 'load-balancer-api-external: resolved host name a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:37:41Z" - latency: 5.289854ms message: 'load-balancer-api-external: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:36:41Z" - latency: 7.026807ms message: 'load-balancer-api-external: resolved host name a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:36:41Z" - latency: 4.439835ms message: 'load-balancer-api-external: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:41Z" - latency: 7.982764ms message: 'load-balancer-api-external: resolved host name a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:35:41Z" - latency: 4.925558ms message: 'load-balancer-api-external: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:41Z" - latency: 13.649424ms message: 'load-balancer-api-external: resolved host name a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:34:41Z" - latency: 4.175175ms message: 'load-balancer-api-external: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:41Z" - latency: 8.676934ms message: 'load-balancer-api-external: resolved host name a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:33:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:01:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-28-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-28.ec2.internal uid: 2d1eb4e7-6a4c-4694-a785-e38f09c15c1a resourceVersion: "54955" uid: c8b06e1f-bb62-4d81-a6d9-72f7c9b3b0bc spec: sourcePod: network-check-source-56499946bc-gptgl targetEndpoint: a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T17:07:41Z" message: 'load-balancer-api-internal: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.557031ms message: 'load-balancer-api-internal: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:37:41Z" - latency: 8.581541ms message: 'load-balancer-api-internal: resolved host name a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:37:41Z" - latency: 5.737606ms message: 'load-balancer-api-internal: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:36:41Z" - latency: 7.125317ms message: 'load-balancer-api-internal: resolved host name a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:36:41Z" - latency: 4.456283ms message: 'load-balancer-api-internal: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:41Z" - latency: 8.075791ms message: 'load-balancer-api-internal: resolved host name a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:35:41Z" - latency: 4.938226ms message: 'load-balancer-api-internal: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:41Z" - latency: 13.621664ms message: 'load-balancer-api-internal: resolved host name a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:34:41Z" - latency: 4.801117ms message: 'load-balancer-api-internal: tcp connection to a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:41Z" - latency: 8.762514ms message: 'load-balancer-api-internal: resolved host name a0982126e3c4d4300aa49bdc444c76df-0aa7d40c4aa2717d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:33:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:01:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-28-to-network-check-target-ip-10-0-128-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-28.ec2.internal uid: 2d1eb4e7-6a4c-4694-a785-e38f09c15c1a resourceVersion: "53861" uid: 0dc34078-3c6d-465b-94a6-e74bd55bc6a4 spec: sourcePod: network-check-source-56499946bc-gptgl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T17:08:41Z" message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.898276ms message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:36:41Z" - latency: 1.843444ms message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:41Z" - latency: 2.384104ms message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:41Z" - latency: 2.241399ms message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:41Z" - latency: 2.177058ms message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:41Z" - latency: 2.016597ms message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:31:41Z" - latency: 2.409651ms message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:30:41Z" - latency: 2.628182ms message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:29:41Z" - latency: 2.139931ms message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:28:41Z" - latency: 2.435244ms message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:27:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:01:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-28-to-network-check-target-ip-10-0-139-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-28.ec2.internal uid: 2d1eb4e7-6a4c-4694-a785-e38f09c15c1a resourceVersion: "53860" uid: 04c1cf46-8f9f-4303-8853-0efb736b99de spec: sourcePod: network-check-source-56499946bc-gptgl targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T17:08:41Z" message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 736.321µs message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:36:41Z" - latency: 784.109µs message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:41Z" - latency: 1.586179ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:41Z" - latency: 759.902µs message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:41Z" - latency: 1.239994ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:41Z" - latency: 840.226µs message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:31:41Z" - latency: 913.917µs message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:30:41Z" - latency: 1.136925ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:29:41Z" - latency: 861.203µs message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:28:41Z" - latency: 1.27071ms message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:27:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:01:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-28-to-network-check-target-ip-10-0-140-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-28.ec2.internal uid: 2d1eb4e7-6a4c-4694-a785-e38f09c15c1a resourceVersion: "53862" uid: 8b80a92e-dfc1-4852-9a2e-164587f0697f spec: sourcePod: network-check-source-56499946bc-gptgl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T17:08:41Z" message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.188061ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:36:41Z" - latency: 1.917516ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:41Z" - latency: 2.404878ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:41Z" - latency: 2.359594ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:41Z" - latency: 2.247502ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:32:41Z" - latency: 1.854095ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:31:41Z" - latency: 2.32302ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:30:41Z" - latency: 2.469689ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:29:41Z" - latency: 2.175864ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:28:41Z" - latency: 2.193494ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:27:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:01:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-28-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-28.ec2.internal uid: 2d1eb4e7-6a4c-4694-a785-e38f09c15c1a resourceVersion: "54953" uid: f86df1b5-e446-42c6-b092-5f68a5d138f3 spec: sourcePod: network-check-source-56499946bc-gptgl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T17:07:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 734.051µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:37:41Z" - latency: 1.913028ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:37:41Z" - latency: 886.106µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:36:41Z" - latency: 1.608387ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:36:41Z" - latency: 1.044785ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:35:41Z" - latency: 1.631156ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:35:41Z" - latency: 912.365µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:34:41Z" - latency: 1.67383ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:34:41Z" - latency: 1.228891ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:33:41Z" - latency: 1.665528ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:33:41Z" kind: List metadata: resourceVersion: ""