apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-88-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-88.ec2.internal uid: 5fb3340c-c681-4f0d-b3f8-e2fd68561d03 resourceVersion: "62304" uid: caf3ad70-cf74-4044-ad3d-10c617aa17fb spec: sourcePod: network-check-source-7bc5b6bf85-b4tq5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T12:50:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.270299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:25:58Z" - latency: 1.08565ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:24:58Z" - latency: 892.156µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:23:58Z" - latency: 880.703µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:22:58Z" - latency: 999.703µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:21:58Z" - latency: 1.394068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:20:58Z" - latency: 1.061693ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:19:58Z" - latency: 1.104452ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:18:58Z" - latency: 1.132607ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:17:58Z" - latency: 1.361318ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:16:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-88-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-88.ec2.internal uid: 5fb3340c-c681-4f0d-b3f8-e2fd68561d03 resourceVersion: "62307" uid: a63fad43-08ef-4bba-b7b0-beb2bce54faf spec: sourcePod: network-check-source-7bc5b6bf85-b4tq5 targetEndpoint: a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T12:49:58Z" message: 'load-balancer-api-external: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.00632ms message: 'load-balancer-api-external: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:25:58Z" - latency: 7.052009ms message: 'load-balancer-api-external: resolved host name a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:25:58Z" - latency: 9.733855ms message: 'load-balancer-api-external: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:24:58Z" - latency: 7.061421ms message: 'load-balancer-api-external: resolved host name a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:24:58Z" - latency: 5.404267ms message: 'load-balancer-api-external: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:23:58Z" - latency: 6.816669ms message: 'load-balancer-api-external: resolved host name a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:23:58Z" - latency: 5.124853ms message: 'load-balancer-api-external: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:22:58Z" - latency: 7.246919ms message: 'load-balancer-api-external: resolved host name a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:22:58Z" - latency: 5.61605ms message: 'load-balancer-api-external: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:21:58Z" - latency: 6.625676ms message: 'load-balancer-api-external: resolved host name a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:21:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-88-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-88.ec2.internal uid: 5fb3340c-c681-4f0d-b3f8-e2fd68561d03 resourceVersion: "62306" uid: edea22fa-efe2-461d-af00-afeb2656042d spec: sourcePod: network-check-source-7bc5b6bf85-b4tq5 targetEndpoint: a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T12:49:58Z" message: 'load-balancer-api-internal: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.3266ms message: 'load-balancer-api-internal: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:25:58Z" - latency: 6.932802ms message: 'load-balancer-api-internal: resolved host name a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:25:58Z" - latency: 3.352288ms message: 'load-balancer-api-internal: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:24:58Z" - latency: 7.171129ms message: 'load-balancer-api-internal: resolved host name a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:24:58Z" - latency: 5.724009ms message: 'load-balancer-api-internal: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:23:58Z" - latency: 6.808958ms message: 'load-balancer-api-internal: resolved host name a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:23:58Z" - latency: 5.097145ms message: 'load-balancer-api-internal: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:22:58Z" - latency: 7.318646ms message: 'load-balancer-api-internal: resolved host name a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:22:58Z" - latency: 5.593834ms message: 'load-balancer-api-internal: tcp connection to a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:21:58Z" - latency: 6.727188ms message: 'load-balancer-api-internal: resolved host name a365bf9e5810e465f9b7304ca1472cc6-b6b1bb31b31cbca9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:21:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-88-to-network-check-target-ip-10-0-129-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-88.ec2.internal uid: 5fb3340c-c681-4f0d-b3f8-e2fd68561d03 resourceVersion: "62302" uid: 7e091080-39b7-4326-94d3-3bc72fc02ad6 spec: sourcePod: network-check-source-7bc5b6bf85-b4tq5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T12:50:58Z" message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.299683ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:25:58Z" - latency: 2.033958ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:24:58Z" - latency: 2.169831ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:23:58Z" - latency: 2.146935ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:22:58Z" - latency: 2.214136ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:21:58Z" - latency: 2.365557ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:20:58Z" - latency: 2.341315ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:19:58Z" - latency: 2.93217ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:18:58Z" - latency: 2.228536ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:17:58Z" - latency: 2.290098ms message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:16:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-88-to-network-check-target-ip-10-0-137-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-88.ec2.internal uid: 5fb3340c-c681-4f0d-b3f8-e2fd68561d03 resourceVersion: "62300" uid: 730e4754-f765-46f6-b215-364534c34ac1 spec: sourcePod: network-check-source-7bc5b6bf85-b4tq5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T12:50:58Z" message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.249108ms message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:25:58Z" - latency: 2.241548ms message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:24:58Z" - latency: 2.141616ms message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:23:58Z" - latency: 2.129702ms message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:22:58Z" - latency: 2.133451ms message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:21:58Z" - latency: 2.40909ms message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:20:58Z" - latency: 2.407228ms message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:19:58Z" - latency: 2.644146ms message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:18:58Z" - latency: 2.216679ms message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:17:58Z" - latency: 2.176214ms message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:16:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-88-to-network-check-target-ip-10-0-137-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-88.ec2.internal uid: 5fb3340c-c681-4f0d-b3f8-e2fd68561d03 resourceVersion: "62301" uid: 7dc75073-68a9-45cd-be0d-4482e1792d3c spec: sourcePod: network-check-source-7bc5b6bf85-b4tq5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T12:50:58Z" message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 942.319µs message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:25:58Z" - latency: 872.739µs message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:24:58Z" - latency: 976.016µs message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:23:58Z" - latency: 1.349515ms message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:22:58Z" - latency: 878.761µs message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:21:58Z" - latency: 1.696785ms message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:20:58Z" - latency: 997.625µs message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:19:58Z" - latency: 1.873701ms message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:18:58Z" - latency: 1.459176ms message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:17:58Z" - latency: 961.833µs message: 'network-check-target-ip-10-0-137-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:16:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-88-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-88.ec2.internal uid: 5fb3340c-c681-4f0d-b3f8-e2fd68561d03 resourceVersion: "62303" uid: c36390bb-9e82-46c5-b9a7-626d42cf93c2 spec: sourcePod: network-check-source-7bc5b6bf85-b4tq5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T12:49:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 938.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:25:58Z" - latency: 1.683ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T13:25:58Z" - latency: 971.671µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:24:58Z" - latency: 1.773435ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T13:24:58Z" - latency: 1.192412ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:23:58Z" - latency: 1.804959ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T13:23:58Z" - latency: 1.015372ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:22:58Z" - latency: 1.948993ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T13:22:58Z" - latency: 1.110705ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:21:58Z" - latency: 1.598781ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T13:21:58Z" kind: List metadata: resourceVersion: ""