apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T16:13:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-123-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-123.ec2.internal uid: 02f07eac-639a-45c5-a8ff-fca0d2a0a815 resourceVersion: "50337" uid: 6a595a62-85e4-4b0c-901a-2ef75f0a107a spec: sourcePod: network-check-source-6947749cfc-ktnjf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-14T16:20: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.192438ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:48:17Z" - latency: 948.114µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:47:17Z" - latency: 869.854µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:46:17Z" - latency: 792.538µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:45:17Z" - latency: 1.264421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:44:17Z" - latency: 953.363µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:43:17Z" - latency: 1.183364ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:42:17Z" - latency: 1.565835ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:41:17Z" - latency: 1.237778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:40:17Z" - latency: 1.230442ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T16:13:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-123-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-123.ec2.internal uid: 02f07eac-639a-45c5-a8ff-fca0d2a0a815 resourceVersion: "46259" uid: 4fe48ade-090a-4798-a615-dde99a29eed0 spec: sourcePod: network-check-source-6947749cfc-ktnjf targetEndpoint: a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T16:19:17Z" message: 'load-balancer-api-external: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.034208ms message: 'load-balancer-api-external: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:43:17Z" - latency: 8.780403ms message: 'load-balancer-api-external: resolved host name a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T16:43:17Z" - latency: 4.665449ms message: 'load-balancer-api-external: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:42:17Z" - latency: 10.668457ms message: 'load-balancer-api-external: resolved host name a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T16:42:17Z" - latency: 5.384637ms message: 'load-balancer-api-external: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:41:17Z" - latency: 8.575779ms message: 'load-balancer-api-external: resolved host name a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T16:41:17Z" - latency: 3.650862ms message: 'load-balancer-api-external: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:40:17Z" - latency: 8.990336ms message: 'load-balancer-api-external: resolved host name a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T16:40:17Z" - latency: 4.09075ms message: 'load-balancer-api-external: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:39:17Z" - latency: 9.306822ms message: 'load-balancer-api-external: resolved host name a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T16:13:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-123-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-123.ec2.internal uid: 02f07eac-639a-45c5-a8ff-fca0d2a0a815 resourceVersion: "46258" uid: 4b977f20-eb85-45f9-8a15-d797b492c43c spec: sourcePod: network-check-source-6947749cfc-ktnjf targetEndpoint: a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T16:19:17Z" message: 'load-balancer-api-internal: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.016188ms message: 'load-balancer-api-internal: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:43:17Z" - latency: 8.720916ms message: 'load-balancer-api-internal: resolved host name a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T16:43:17Z" - latency: 3.884766ms message: 'load-balancer-api-internal: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:42:17Z" - latency: 10.607649ms message: 'load-balancer-api-internal: resolved host name a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T16:42:17Z" - latency: 5.380588ms message: 'load-balancer-api-internal: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:41:17Z" - latency: 8.598248ms message: 'load-balancer-api-internal: resolved host name a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T16:41:17Z" - latency: 3.671357ms message: 'load-balancer-api-internal: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:40:17Z" - latency: 8.946272ms message: 'load-balancer-api-internal: resolved host name a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T16:40:17Z" - latency: 3.324065ms message: 'load-balancer-api-internal: tcp connection to a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:39:17Z" - latency: 9.326902ms message: 'load-balancer-api-internal: resolved host name a7e88f309b0cf4a559f303e987499f4e-435b3c708c1281d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T16:13:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-123-to-network-check-target-ip-10-0-130-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-123.ec2.internal uid: 02f07eac-639a-45c5-a8ff-fca0d2a0a815 resourceVersion: "50335" uid: f61710a5-09d0-44d5-b46e-1568472c63e4 spec: sourcePod: network-check-source-6947749cfc-ktnjf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-14T16:20:17Z" message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 896.954µs message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:48:17Z" - latency: 1.330502ms message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:47:17Z" - latency: 1.236762ms message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:46:17Z" - latency: 827.81µs message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:45:17Z" - latency: 1.278063ms message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:44:17Z" - latency: 1.114188ms message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:43:17Z" - latency: 1.353754ms message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:42:17Z" - latency: 772.268µs message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:41:17Z" - latency: 837.317µs message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:40:17Z" - latency: 1.416596ms message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T16:13:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-123-to-network-check-target-ip-10-0-131-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-123.ec2.internal uid: 02f07eac-639a-45c5-a8ff-fca0d2a0a815 resourceVersion: "44535" uid: a4fb1438-e51a-45dd-841d-e78a6727aec3 spec: sourcePod: network-check-source-6947749cfc-ktnjf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-14T16:20:41Z" message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.21567ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:41:41Z" - latency: 2.408591ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:40:41Z" - latency: 2.345777ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:39:41Z" - latency: 2.016787ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:38:41Z" - latency: 2.349012ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:37:41Z" - latency: 2.441698ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:36:41Z" - latency: 2.283028ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:35:41Z" - latency: 2.053065ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:34:41Z" - latency: 2.119828ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:33:41Z" - latency: 2.383986ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:32:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T16:13:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-123-to-network-check-target-ip-10-0-138-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-123.ec2.internal uid: 02f07eac-639a-45c5-a8ff-fca0d2a0a815 resourceVersion: "50336" uid: 1c168ea1-37fe-47dc-95f4-9cfbc6aae861 spec: sourcePod: network-check-source-6947749cfc-ktnjf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-14T16:20:17Z" message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.007241ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:48:17Z" - latency: 1.941525ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:47:17Z" - latency: 1.850994ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:46:17Z" - latency: 1.83503ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:45:17Z" - latency: 2.3492ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:44:17Z" - latency: 2.07221ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:43:17Z" - latency: 2.055108ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:42:17Z" - latency: 2.065563ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:41:17Z" - latency: 1.979336ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:40:17Z" - latency: 2.077345ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T16:13:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-123-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-123.ec2.internal uid: 02f07eac-639a-45c5-a8ff-fca0d2a0a815 resourceVersion: "46256" uid: 171b5a81-d688-4cbd-a484-d56148e9970a spec: sourcePod: network-check-source-6947749cfc-ktnjf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-14T16:19:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 807.187µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:43:17Z" - latency: 1.831326ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T16:43:17Z" - latency: 799.881µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:42:17Z" - latency: 2.094765ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T16:42:17Z" - latency: 2.273719ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:41:17Z" - latency: 1.958312ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T16:41:17Z" - latency: 804.034µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:40:17Z" - latency: 2.234187ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T16:40:17Z" - latency: 2.109358ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T16:39:17Z" - latency: 2.065745ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T16:39:17Z" kind: List metadata: resourceVersion: ""