apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-72-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-72.us-east-2.compute.internal uid: 931f23a9-47c3-4ac8-a2c9-04be301bf465 resourceVersion: "33120" uid: 69e0c51b-8d71-41e2-9c56-d1d0c21ce7ab spec: sourcePod: network-check-source-6f78d59f99-mhpk5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T04:18:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.710725ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:21:25Z" - latency: 1.374841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:20:25Z" - latency: 1.471717ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:19:25Z" - latency: 1.16884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:18:25Z" - latency: 1.281935ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:17:25Z" - latency: 1.236603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:16:25Z" - latency: 1.236242ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:15:25Z" - latency: 1.238987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:14:25Z" - latency: 1.299987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:13:25Z" - latency: 2.138678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:12:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-72-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-72.us-east-2.compute.internal uid: 931f23a9-47c3-4ac8-a2c9-04be301bf465 resourceVersion: "33566" uid: 389be34a-04a2-4590-a08b-b53385fc4f31 spec: sourcePod: network-check-source-6f78d59f99-mhpk5 targetEndpoint: a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T04:17:25Z" message: 'load-balancer-api-external: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.962879ms message: 'load-balancer-api-external: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:23:25Z" - latency: 8.684644ms message: 'load-balancer-api-external: resolved host name a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:23:25Z" - latency: 6.158082ms message: 'load-balancer-api-external: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:22:25Z" - latency: 8.694637ms message: 'load-balancer-api-external: resolved host name a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:22:25Z" - latency: 6.103422ms message: 'load-balancer-api-external: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:21:25Z" - latency: 7.016066ms message: 'load-balancer-api-external: resolved host name a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:21:25Z" - latency: 5.068573ms message: 'load-balancer-api-external: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:20:25Z" - latency: 7.638786ms message: 'load-balancer-api-external: resolved host name a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:20:25Z" - latency: 5.321036ms message: 'load-balancer-api-external: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:19:25Z" - latency: 7.309991ms message: 'load-balancer-api-external: resolved host name a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:19:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-72-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-72.us-east-2.compute.internal uid: 931f23a9-47c3-4ac8-a2c9-04be301bf465 resourceVersion: "33565" uid: 03246f9d-717c-438b-ab5e-1fd397870786 spec: sourcePod: network-check-source-6f78d59f99-mhpk5 targetEndpoint: a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T04:17:25Z" message: 'load-balancer-api-internal: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.600714ms message: 'load-balancer-api-internal: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:23:25Z" - latency: 8.732191ms message: 'load-balancer-api-internal: resolved host name a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:23:25Z" - latency: 6.556737ms message: 'load-balancer-api-internal: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:22:25Z" - latency: 8.587591ms message: 'load-balancer-api-internal: resolved host name a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:22:25Z" - latency: 4.687053ms message: 'load-balancer-api-internal: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:21:25Z" - latency: 6.989727ms message: 'load-balancer-api-internal: resolved host name a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:21:25Z" - latency: 4.958387ms message: 'load-balancer-api-internal: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:20:25Z" - latency: 7.530185ms message: 'load-balancer-api-internal: resolved host name a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:20:25Z" - latency: 5.334276ms message: 'load-balancer-api-internal: tcp connection to a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:19:25Z" - latency: 7.391016ms message: 'load-balancer-api-internal: resolved host name a122cc66207964f958e1045509004477-cabed480cd66b3bf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:19:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-72-to-network-check-target-ip-10-0-131-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-72.us-east-2.compute.internal uid: 931f23a9-47c3-4ac8-a2c9-04be301bf465 resourceVersion: "33119" uid: 5b520492-2dac-4e3f-833c-a5f9a8f7df6e spec: sourcePod: network-check-source-6f78d59f99-mhpk5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T04:18:25Z" message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.653911ms message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:21:25Z" - latency: 1.85362ms message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:20:25Z" - latency: 1.640641ms message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:19:25Z" - latency: 1.357102ms message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:18:25Z" - latency: 1.451508ms message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:17:25Z" - latency: 1.758037ms message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:16:25Z" - latency: 1.128611ms message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:15:25Z" - latency: 1.789579ms message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:14:25Z" - latency: 1.575861ms message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:13:25Z" - latency: 2.238209ms message: 'network-check-target-ip-10-0-131-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:12:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:11:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-72-to-network-check-target-ip-10-0-133-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-72.us-east-2.compute.internal uid: 931f23a9-47c3-4ac8-a2c9-04be301bf465 resourceVersion: "33227" uid: b2669b94-0a7a-445d-acec-f1252a0bf8b9 spec: sourcePod: network-check-source-6f78d59f99-mhpk5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T04:18:56Z" message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.656227ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:21:56Z" - latency: 2.89305ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:20:56Z" - latency: 2.162025ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:19:56Z" - latency: 2.452924ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:18:56Z" - latency: 2.065381ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:17:56Z" - latency: 2.377265ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:16:56Z" - latency: 2.441342ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:15:56Z" - latency: 2.42112ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:14:56Z" - latency: 2.482174ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:13:56Z" - latency: 2.094502ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:12:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:11:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-72-to-network-check-target-ip-10-0-133-67 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-72.us-east-2.compute.internal uid: 931f23a9-47c3-4ac8-a2c9-04be301bf465 resourceVersion: "33149" uid: 916da2f6-fc84-4108-9572-486fe5d67f96 spec: sourcePod: network-check-source-6f78d59f99-mhpk5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T04:18:34Z" message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.521948ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:21:34Z" - latency: 3.153927ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:20:34Z" - latency: 2.57245ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:19:34Z" - latency: 1.447922ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:18:34Z" - latency: 1.355728ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:17:34Z" - latency: 1.331012ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:16:34Z" - latency: 2.740337ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:15:34Z" - latency: 2.679111ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:14:34Z" - latency: 1.532557ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:13:34Z" - latency: 3.0014ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:12:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-72-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-72.us-east-2.compute.internal uid: 931f23a9-47c3-4ac8-a2c9-04be301bf465 resourceVersion: "33564" uid: 84dd7605-167f-48ca-a5bc-2f5bb25ebb1b spec: sourcePod: network-check-source-6f78d59f99-mhpk5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T04:17:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.009022ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:23:25Z" - latency: 2.229639ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:23:25Z" - latency: 2.203075ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:22:25Z" - latency: 2.490702ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:22:25Z" - latency: 2.176123ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:21:25Z" - latency: 2.238401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:21:25Z" - latency: 2.145095ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:20:25Z" - latency: 2.373609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:20:25Z" - latency: 909.64µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:19:25Z" - latency: 2.058488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:19:25Z" kind: List metadata: resourceVersion: ""