apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:45:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-103-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-103.ec2.internal uid: 97a79af0-bda3-42ce-ab87-89dc81f1bc10 resourceVersion: "55937" uid: f1f5f7e4-b60d-4f02-929a-8a225943ab23 spec: sourcePod: network-check-source-869dcfcdcd-jqdnm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T17:52:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.278409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:20:15Z" - latency: 1.170979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:19:15Z" - latency: 1.122439ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:18:15Z" - latency: 946.087µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:17:15Z" - latency: 1.051835ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:16:15Z" - latency: 1.168316ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:15:15Z" - latency: 1.105983ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:14:15Z" - latency: 1.12258ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:13:15Z" - latency: 1.092845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:12:15Z" - latency: 1.054531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:11:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:45:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-103-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-103.ec2.internal uid: 97a79af0-bda3-42ce-ab87-89dc81f1bc10 resourceVersion: "56878" uid: 9ad46c6f-5694-4e9a-834e-8de2953e4563 spec: sourcePod: network-check-source-869dcfcdcd-jqdnm targetEndpoint: a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T17:51:15Z" message: 'load-balancer-api-external: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.328999ms message: 'load-balancer-api-external: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:21:15Z" - latency: 9.566697ms message: 'load-balancer-api-external: resolved host name a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:21:15Z" - latency: 4.478428ms message: 'load-balancer-api-external: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:20:15Z" - latency: 8.946614ms message: 'load-balancer-api-external: resolved host name a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:20:15Z" - latency: 4.687733ms message: 'load-balancer-api-external: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:19:15Z" - latency: 8.355905ms message: 'load-balancer-api-external: resolved host name a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:19:15Z" - latency: 5.459386ms message: 'load-balancer-api-external: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:18:15Z" - latency: 8.678647ms message: 'load-balancer-api-external: resolved host name a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:18:15Z" - latency: 4.32383ms message: 'load-balancer-api-external: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:17:15Z" - latency: 7.992093ms message: 'load-balancer-api-external: resolved host name a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:17:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:45:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-103-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-103.ec2.internal uid: 97a79af0-bda3-42ce-ab87-89dc81f1bc10 resourceVersion: "56879" uid: 1f208d7b-e0fa-438d-b140-a5afecdaab1f spec: sourcePod: network-check-source-869dcfcdcd-jqdnm targetEndpoint: a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T17:51:15Z" message: 'load-balancer-api-internal: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.353538ms message: 'load-balancer-api-internal: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:21:15Z" - latency: 9.512358ms message: 'load-balancer-api-internal: resolved host name a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:21:15Z" - latency: 4.529616ms message: 'load-balancer-api-internal: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:20:15Z" - latency: 8.789151ms message: 'load-balancer-api-internal: resolved host name a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:20:15Z" - latency: 4.697958ms message: 'load-balancer-api-internal: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:19:15Z" - latency: 8.28291ms message: 'load-balancer-api-internal: resolved host name a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:19:15Z" - latency: 4.382261ms message: 'load-balancer-api-internal: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:18:15Z" - latency: 8.709337ms message: 'load-balancer-api-internal: resolved host name a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:18:15Z" - latency: 4.308407ms message: 'load-balancer-api-internal: tcp connection to a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:17:15Z" - latency: 7.858883ms message: 'load-balancer-api-internal: resolved host name a068fb79196484fc3a17272aaed24ecb-e3b6236a10c28537.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:17:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:45:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-103-to-network-check-target-ip-10-0-131-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-103.ec2.internal uid: 97a79af0-bda3-42ce-ab87-89dc81f1bc10 resourceVersion: "55936" uid: b5e10d5d-2cb8-465e-b180-ce8f1f398a7a spec: sourcePod: network-check-source-869dcfcdcd-jqdnm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T17:52:15Z" message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.48702ms message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:20:15Z" - latency: 2.078914ms message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:19:15Z" - latency: 2.097759ms message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:18:15Z" - latency: 2.129484ms message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:17:15Z" - latency: 2.528808ms message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:16:15Z" - latency: 2.349217ms message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:15:15Z" - latency: 2.23936ms message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:14:15Z" - latency: 2.226394ms message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:13:15Z" - latency: 2.20155ms message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:12:15Z" - latency: 2.172648ms message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:11:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:45:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-103-to-network-check-target-ip-10-0-133-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-103.ec2.internal uid: 97a79af0-bda3-42ce-ab87-89dc81f1bc10 resourceVersion: "55935" uid: af5da27f-387e-4a44-ac36-82f3b4415fbe spec: sourcePod: network-check-source-869dcfcdcd-jqdnm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T17:52:15Z" message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.51165ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:20:15Z" - latency: 2.045022ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:19:15Z" - latency: 2.086466ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:18:15Z" - latency: 2.05794ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:17:15Z" - latency: 2.888195ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:16:15Z" - latency: 2.669018ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:15:15Z" - latency: 2.444332ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:14:15Z" - latency: 2.258874ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:13:15Z" - latency: 2.018139ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:12:15Z" - latency: 2.014974ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:11:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:45:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-103-to-network-check-target-ip-10-0-137-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-103.ec2.internal uid: 97a79af0-bda3-42ce-ab87-89dc81f1bc10 resourceVersion: "55934" uid: 49618d01-3ee7-41f4-aa70-4e22d5e7cb61 spec: sourcePod: network-check-source-869dcfcdcd-jqdnm targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T17:52:15Z" message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.449601ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:20:15Z" - latency: 1.411662ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:19:15Z" - latency: 1.207418ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:18:15Z" - latency: 901.717µs message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:17:15Z" - latency: 927.151µs message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:16:15Z" - latency: 1.472276ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:15:15Z" - latency: 900.132µs message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:14:15Z" - latency: 1.163491ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:13:15Z" - latency: 899.28µs message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:12:15Z" - latency: 882.339µs message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:11:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T17:45:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-103-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-103.ec2.internal uid: 97a79af0-bda3-42ce-ab87-89dc81f1bc10 resourceVersion: "56877" uid: d2a5b0cb-74b8-451e-bd93-2cf864c932d4 spec: sourcePod: network-check-source-869dcfcdcd-jqdnm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T17:51:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.060384ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:21:15Z" - latency: 1.627999ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:21:15Z" - latency: 930.491µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:20:15Z" - latency: 1.791341ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:20:15Z" - latency: 842.946µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:19:15Z" - latency: 1.995544ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:19:15Z" - latency: 892.819µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:18:15Z" - latency: 2.048601ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:18:15Z" - latency: 885.798µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:17:15Z" - latency: 1.612754ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:17:15Z" kind: List metadata: resourceVersion: ""