apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:15:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-185-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-185.ec2.internal uid: fbf126d3-05b5-4c9e-9a96-16b6cb43b49f resourceVersion: "88906" uid: 4f101702-1b9c-499e-938b-93699c262e14 spec: sourcePod: network-check-source-685456655f-pmzjz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T20:22:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.447µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:25:51Z" - latency: 1.084032ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:24:51Z" - latency: 1.033501ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:51Z" - latency: 1.337861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:51Z" - latency: 1.163778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:51Z" - latency: 1.280082ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:51Z" - latency: 1.573065ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:51Z" - latency: 1.30323ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:51Z" - latency: 1.70628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:51Z" - latency: 1.760632ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:15:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-185-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-185.ec2.internal uid: fbf126d3-05b5-4c9e-9a96-16b6cb43b49f resourceVersion: "85054" uid: 6bb1ec91-1e13-4d53-80db-03b4da93a8f6 spec: sourcePod: network-check-source-685456655f-pmzjz targetEndpoint: a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:21:51Z" message: 'load-balancer-api-external: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.116624ms message: 'load-balancer-api-external: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:51Z" - latency: 7.51718ms message: 'load-balancer-api-external: resolved host name a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:21:51Z" - latency: 5.153337ms message: 'load-balancer-api-external: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:51Z" - latency: 7.572702ms message: 'load-balancer-api-external: resolved host name a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:20:51Z" - latency: 5.113884ms message: 'load-balancer-api-external: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:51Z" - latency: 7.301938ms message: 'load-balancer-api-external: resolved host name a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:19:51Z" - latency: 5.21435ms message: 'load-balancer-api-external: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:51Z" - latency: 8.004623ms message: 'load-balancer-api-external: resolved host name a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:18:51Z" - latency: 5.758029ms message: 'load-balancer-api-external: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:51Z" - latency: 7.150943ms message: 'load-balancer-api-external: resolved host name a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:17:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:15:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-185-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-185.ec2.internal uid: fbf126d3-05b5-4c9e-9a96-16b6cb43b49f resourceVersion: "85055" uid: 175f85d8-28f3-47c3-8c2b-62d42fdcd7ff spec: sourcePod: network-check-source-685456655f-pmzjz targetEndpoint: a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:21:51Z" message: 'load-balancer-api-internal: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.188478ms message: 'load-balancer-api-internal: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:51Z" - latency: 7.467957ms message: 'load-balancer-api-internal: resolved host name a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:21:51Z" - latency: 5.207377ms message: 'load-balancer-api-internal: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:51Z" - latency: 7.545439ms message: 'load-balancer-api-internal: resolved host name a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:20:51Z" - latency: 5.558812ms message: 'load-balancer-api-internal: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:51Z" - latency: 7.274316ms message: 'load-balancer-api-internal: resolved host name a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:19:51Z" - latency: 5.246928ms message: 'load-balancer-api-internal: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:51Z" - latency: 8.084004ms message: 'load-balancer-api-internal: resolved host name a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:18:51Z" - latency: 6.293153ms message: 'load-balancer-api-internal: tcp connection to a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:51Z" - latency: 7.101965ms message: 'load-balancer-api-internal: resolved host name a8574715afc1f4dedae37c0a331b4845-8b1dac3f5681aee7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:17:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:15:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-185-to-network-check-target-ip-10-0-131-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-185.ec2.internal uid: fbf126d3-05b5-4c9e-9a96-16b6cb43b49f resourceVersion: "88904" uid: 88733e6b-17f2-440b-a4d3-255641a8f31c spec: sourcePod: network-check-source-685456655f-pmzjz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:22:51Z" message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.20197ms message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:25:51Z" - latency: 883.838µs message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:24:51Z" - latency: 1.319379ms message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:51Z" - latency: 1.025716ms message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:51Z" - latency: 1.018924ms message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:51Z" - latency: 935.666µs message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:51Z" - latency: 1.521546ms message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:51Z" - latency: 1.491499ms message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:51Z" - latency: 1.261276ms message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:51Z" - latency: 1.107354ms message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:15:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-185-to-network-check-target-ip-10-0-132-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-185.ec2.internal uid: fbf126d3-05b5-4c9e-9a96-16b6cb43b49f resourceVersion: "88905" uid: 19805eb6-149f-445a-9331-2acddb0f8f86 spec: sourcePod: network-check-source-685456655f-pmzjz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:22:51Z" message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.707183ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:25:51Z" - latency: 1.894459ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:24:51Z" - latency: 1.846996ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:51Z" - latency: 1.849129ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:51Z" - latency: 2.237482ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:51Z" - latency: 1.915544ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:51Z" - latency: 1.806611ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:51Z" - latency: 1.655409ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:51Z" - latency: 1.885086ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:51Z" - latency: 2.791021ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:15:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-185-to-network-check-target-ip-10-0-134-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-185.ec2.internal uid: fbf126d3-05b5-4c9e-9a96-16b6cb43b49f resourceVersion: "88903" uid: 82c535dc-dd95-4a6d-a535-f46b858bd1e5 spec: sourcePod: network-check-source-685456655f-pmzjz targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:22:51Z" message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.889979ms message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:25:51Z" - latency: 2.245306ms message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:24:51Z" - latency: 2.248073ms message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:23:51Z" - latency: 2.410882ms message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:22:51Z" - latency: 2.740396ms message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:51Z" - latency: 2.362999ms message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:51Z" - latency: 2.329281ms message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:51Z" - latency: 2.482287ms message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:51Z" - latency: 2.621373ms message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:51Z" - latency: 2.372226ms message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:15:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-185-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-185.ec2.internal uid: fbf126d3-05b5-4c9e-9a96-16b6cb43b49f resourceVersion: "85053" uid: 215553f0-df74-4e7d-a58c-ae6f0105ca20 spec: sourcePod: network-check-source-685456655f-pmzjz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T20:21:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.10973ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:21:51Z" - latency: 2.360842ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:21:51Z" - latency: 929.822µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:20:51Z" - latency: 2.157393ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:20:51Z" - latency: 811.747µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:51Z" - latency: 2.00189ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:19:51Z" - latency: 1.123993ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:51Z" - latency: 2.219726ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:18:51Z" - latency: 832.778µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:51Z" - latency: 2.199709ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:17:51Z" kind: List metadata: resourceVersion: ""