apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:39:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-203-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-203.ec2.internal uid: 26528f14-8d73-475f-9c45-4e7986144e43 resourceVersion: "74580" uid: ad2d8d24-6791-4063-b6f8-0e86c85ebbc4 spec: sourcePod: network-check-source-7d88cb55d8-6lq5r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T23:46:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.721µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:28:58Z" - latency: 1.120588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:27:58Z" - latency: 1.223099ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:26:58Z" - latency: 1.142658ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:25:58Z" - latency: 1.330968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:24:58Z" - latency: 914µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:23:58Z" - latency: 1.036452ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:22:58Z" - latency: 1.310081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:21:58Z" - latency: 1.380955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:20:58Z" - latency: 797.123µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:19:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:39:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-203-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-203.ec2.internal uid: 26528f14-8d73-475f-9c45-4e7986144e43 resourceVersion: "72158" uid: c3206137-6213-4fdd-bcee-fd24d7ebbc7f spec: sourcePod: network-check-source-7d88cb55d8-6lq5r targetEndpoint: a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T23:45:58Z" message: 'load-balancer-api-external: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.32845ms message: 'load-balancer-api-external: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:27:58Z" - latency: 7.939617ms message: 'load-balancer-api-external: resolved host name a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:27:58Z" - latency: 4.968306ms message: 'load-balancer-api-external: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:26:58Z" - latency: 9.048527ms message: 'load-balancer-api-external: resolved host name a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:26:58Z" - latency: 3.484713ms message: 'load-balancer-api-external: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:25:58Z" - latency: 8.266346ms message: 'load-balancer-api-external: resolved host name a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:25:58Z" - latency: 5.732365ms message: 'load-balancer-api-external: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:24:58Z" - latency: 8.774103ms message: 'load-balancer-api-external: resolved host name a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:24:58Z" - latency: 4.3374ms message: 'load-balancer-api-external: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:23:58Z" - latency: 8.054796ms message: 'load-balancer-api-external: resolved host name a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:23:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:39:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-203-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-203.ec2.internal uid: 26528f14-8d73-475f-9c45-4e7986144e43 resourceVersion: "72159" uid: c9ac4631-0194-4d02-9efd-265bea352c7f spec: sourcePod: network-check-source-7d88cb55d8-6lq5r targetEndpoint: a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T23:45:58Z" message: 'load-balancer-api-internal: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.194437ms message: 'load-balancer-api-internal: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:27:58Z" - latency: 7.998542ms message: 'load-balancer-api-internal: resolved host name a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:27:58Z" - latency: 3.801544ms message: 'load-balancer-api-internal: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:26:58Z" - latency: 9.096079ms message: 'load-balancer-api-internal: resolved host name a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:26:58Z" - latency: 3.506288ms message: 'load-balancer-api-internal: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:25:58Z" - latency: 8.217302ms message: 'load-balancer-api-internal: resolved host name a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:25:58Z" - latency: 5.69165ms message: 'load-balancer-api-internal: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:24:58Z" - latency: 8.817988ms message: 'load-balancer-api-internal: resolved host name a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:24:58Z" - latency: 4.664106ms message: 'load-balancer-api-internal: tcp connection to a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:23:58Z" - latency: 8.174986ms message: 'load-balancer-api-internal: resolved host name a67b1527be723484e9d15bb062ebf0db-529d6f44acc1387c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T00:23:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:39:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-203-to-network-check-target-ip-10-0-128-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-203.ec2.internal uid: 26528f14-8d73-475f-9c45-4e7986144e43 resourceVersion: "74577" uid: 71c9985e-4987-41a8-a8a7-14fab525836b spec: sourcePod: network-check-source-7d88cb55d8-6lq5r targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T23:46:58Z" message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.917728ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:28:58Z" - latency: 1.912953ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:27:58Z" - latency: 1.795877ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:26:58Z" - latency: 1.810645ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:25:58Z" - latency: 1.926213ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:24:58Z" - latency: 1.751908ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:23:58Z" - latency: 1.78906ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:22:58Z" - latency: 1.827468ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:21:58Z" - latency: 1.7905ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:20:58Z" - latency: 1.858318ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:19:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:39:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-203-to-network-check-target-ip-10-0-130-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-203.ec2.internal uid: 26528f14-8d73-475f-9c45-4e7986144e43 resourceVersion: "74578" uid: af8eff80-2f55-4fbd-b59c-4d03b435afe2 spec: sourcePod: network-check-source-7d88cb55d8-6lq5r targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T23:46:58Z" message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.102103ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:28:58Z" - latency: 2.416875ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:27:58Z" - latency: 2.517816ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:26:58Z" - latency: 2.278015ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:25:58Z" - latency: 2.517335ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:24:58Z" - latency: 2.308771ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:23:58Z" - latency: 2.319803ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:22:58Z" - latency: 2.671969ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:21:58Z" - latency: 2.29014ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:20:58Z" - latency: 2.326182ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:19:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:39:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-203-to-network-check-target-ip-10-0-142-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-203.ec2.internal uid: 26528f14-8d73-475f-9c45-4e7986144e43 resourceVersion: "74576" uid: 3b52c8b1-f56a-4a60-b6f6-41e541bd5d85 spec: sourcePod: network-check-source-7d88cb55d8-6lq5r targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T23:46:58Z" message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.110165ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:28:58Z" - latency: 1.065375ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:27:58Z" - latency: 1.529423ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:26:58Z" - latency: 913.793µs message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:25:58Z" - latency: 881.518µs message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:24:58Z" - latency: 830.321µs message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:23:58Z" - latency: 799.428µs message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:22:58Z" - latency: 1.083194ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:21:58Z" - latency: 1.140007ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:20:58Z" - latency: 886.63µs message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:19:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T23:39:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-203-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-203.ec2.internal uid: 26528f14-8d73-475f-9c45-4e7986144e43 resourceVersion: "72156" uid: e7913211-37e0-404b-a2a5-407935188a7b spec: sourcePod: network-check-source-7d88cb55d8-6lq5r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T23:45:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 953.943µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:27:58Z" - latency: 1.914732ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T00:27:58Z" - latency: 887.775µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:26:58Z" - latency: 1.724268ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T00:26:58Z" - latency: 830.782µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:25:58Z" - latency: 1.78512ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T00:25:58Z" - latency: 913.329µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:24:58Z" - latency: 1.99405ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T00:24:58Z" - latency: 1.251252ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T00:23:58Z" - latency: 1.589563ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T00:23:58Z" kind: List metadata: resourceVersion: ""