apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:43:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-210-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-210.ec2.internal uid: 95b2728d-3cbe-45a7-91de-89ebfcc5d950 resourceVersion: "167643" uid: 2aaa6347-b5f1-4363-9b40-23c14f4ca139 spec: sourcePod: network-check-source-6f78d59f99-9zmkk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T00:50:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.073852ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:53:17Z" - latency: 1.420263ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:52:17Z" - latency: 1.172466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:51:17Z" - latency: 959.47µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:50:17Z" - latency: 1.377465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:49:17Z" - latency: 940.635µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:48:17Z" - latency: 933.638µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:47:17Z" - latency: 21.352729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:46:17Z" - latency: 996.345µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:45:17Z" - latency: 1.509276ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:44:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:43:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-210-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-210.ec2.internal uid: 95b2728d-3cbe-45a7-91de-89ebfcc5d950 resourceVersion: "173090" uid: 122b8f3b-3ae5-423f-abb8-39ad189ce9b7 spec: sourcePod: network-check-source-6f78d59f99-9zmkk targetEndpoint: a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T00:49:17Z" message: 'load-balancer-api-external: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.2161ms message: 'load-balancer-api-external: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:55:17Z" - latency: 7.108887ms message: 'load-balancer-api-external: resolved host name a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:55:17Z" - latency: 42.530959ms message: 'load-balancer-api-external: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:54:17Z" - latency: 6.851687ms message: 'load-balancer-api-external: resolved host name a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:54:17Z" - latency: 18.412046ms message: 'load-balancer-api-external: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:53:17Z" - latency: 6.941486ms message: 'load-balancer-api-external: resolved host name a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:53:17Z" - latency: 17.750097ms message: 'load-balancer-api-external: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:52:17Z" - latency: 7.798859ms message: 'load-balancer-api-external: resolved host name a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:52:17Z" - latency: 19.698704ms message: 'load-balancer-api-external: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:51:17Z" - latency: 6.227438ms message: 'load-balancer-api-external: resolved host name a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:51:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:43:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-210-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-210.ec2.internal uid: 95b2728d-3cbe-45a7-91de-89ebfcc5d950 resourceVersion: "173091" uid: 22af4925-4c02-40f3-89a3-cc12d1b4ce2a spec: sourcePod: network-check-source-6f78d59f99-9zmkk targetEndpoint: a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T00:49:17Z" message: 'load-balancer-api-internal: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 32.283303ms message: 'load-balancer-api-internal: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:55:17Z" - latency: 7.028918ms message: 'load-balancer-api-internal: resolved host name a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:55:17Z" - latency: 18.683748ms message: 'load-balancer-api-internal: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:54:17Z" - latency: 6.792454ms message: 'load-balancer-api-internal: resolved host name a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:54:17Z" - latency: 20.363369ms message: 'load-balancer-api-internal: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:53:17Z" - latency: 6.864099ms message: 'load-balancer-api-internal: resolved host name a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:53:17Z" - latency: 17.163896ms message: 'load-balancer-api-internal: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:52:17Z" - latency: 7.894975ms message: 'load-balancer-api-internal: resolved host name a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:52:17Z" - latency: 19.729831ms message: 'load-balancer-api-internal: tcp connection to a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:51:17Z" - latency: 6.160955ms message: 'load-balancer-api-internal: resolved host name a82121ed54ce5470798fec135375cbfd-c37369d98e738b08.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:51:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:43:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-210-to-network-check-target-ip-10-0-133-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-210.ec2.internal uid: 95b2728d-3cbe-45a7-91de-89ebfcc5d950 resourceVersion: "167641" uid: 3cc355ee-4d59-40ed-9f12-a854e44c551e spec: sourcePod: network-check-source-6f78d59f99-9zmkk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:50:17Z" message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.44108ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:53:17Z" - latency: 2.511799ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:52:17Z" - latency: 2.655439ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:51:17Z" - latency: 2.406705ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:50:17Z" - latency: 2.92223ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:49:17Z" - latency: 2.412262ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:48:17Z" - latency: 2.449618ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:47:17Z" - latency: 5.22437ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:46:17Z" - latency: 1.957723ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:45:17Z" - latency: 2.750399ms message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:44:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:43:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-210-to-network-check-target-ip-10-0-134-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-210.ec2.internal uid: 95b2728d-3cbe-45a7-91de-89ebfcc5d950 resourceVersion: "167639" uid: b7e91077-8e95-4483-af10-9a1b3b0c4c32 spec: sourcePod: network-check-source-6f78d59f99-9zmkk targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:50:17Z" message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.466µs message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:53:17Z" - latency: 1.705084ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:52:17Z" - latency: 978.294µs message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:51:17Z" - latency: 1.197761ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:50:17Z" - latency: 1.593338ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:49:17Z" - latency: 1.193319ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:48:17Z" - latency: 1.553058ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:47:17Z" - latency: 5.954364ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:46:17Z" - latency: 1.077288ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:45:17Z" - latency: 1.753716ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:44:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:43:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-210-to-network-check-target-ip-10-0-141-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-210.ec2.internal uid: 95b2728d-3cbe-45a7-91de-89ebfcc5d950 resourceVersion: "167640" uid: b9443cfd-d129-4502-bf86-93f71ca7b127 spec: sourcePod: network-check-source-6f78d59f99-9zmkk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:50:17Z" message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.036351ms message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:53:17Z" - latency: 3.425096ms message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:52:17Z" - latency: 2.867366ms message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:51:17Z" - latency: 2.562905ms message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:50:17Z" - latency: 2.45755ms message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:49:17Z" - latency: 2.598941ms message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:48:17Z" - latency: 2.858263ms message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:47:17Z" - latency: 23.264758ms message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:46:17Z" - latency: 2.805931ms message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:45:17Z" - latency: 3.252947ms message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:44:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:43:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-210-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-210.ec2.internal uid: 95b2728d-3cbe-45a7-91de-89ebfcc5d950 resourceVersion: "173084" uid: 0aec625f-8964-482a-8e7f-a29c6c9a4dfb spec: sourcePod: network-check-source-6f78d59f99-9zmkk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T00:49:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.74µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:55:17Z" - latency: 2.261836ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:55:17Z" - latency: 1.530734ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:54:17Z" - latency: 1.878942ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:54:17Z" - latency: 1.421794ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:53:17Z" - latency: 2.020234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:53:17Z" - latency: 953.468µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:52:17Z" - latency: 2.294509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:52:17Z" - latency: 1.030183ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:51:17Z" - latency: 2.172409ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:51:17Z" kind: List metadata: resourceVersion: ""