apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:06:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 2008f1e9-6e8a-49fe-8b72-0a0c93abc732 resourceVersion: "14442" uid: 88c1d1ae-b25c-4ebd-ac77-4390d2343d22 spec: sourcePod: network-check-source-7d88cb55d8-nlbz9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T15:13:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 982.284µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:47Z" - latency: 1.304586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:12:47Z" - latency: 1.303774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:11:47Z" - latency: 907.187µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:10:47Z" - latency: 1.007913ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:09:47Z" - latency: 1.134843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:08:47Z" - latency: 909.493µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:07:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:06:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 2008f1e9-6e8a-49fe-8b72-0a0c93abc732 resourceVersion: "16181" uid: 2e1e6c6c-6c2b-451c-9d31-979e2d3c1b97 spec: sourcePod: network-check-source-7d88cb55d8-nlbz9 targetEndpoint: a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T15:12:47Z" message: 'load-balancer-api-external: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.771315ms message: 'load-balancer-api-external: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:18:47Z" - latency: 8.094239ms message: 'load-balancer-api-external: resolved host name a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:18:47Z" - latency: 4.107643ms message: 'load-balancer-api-external: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:17:47Z" - latency: 8.24218ms message: 'load-balancer-api-external: resolved host name a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:17:47Z" - latency: 5.73417ms message: 'load-balancer-api-external: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:16:47Z" - latency: 7.783527ms message: 'load-balancer-api-external: resolved host name a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:16:47Z" - latency: 3.50663ms message: 'load-balancer-api-external: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:15:47Z" - latency: 8.131119ms message: 'load-balancer-api-external: resolved host name a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:15:47Z" - latency: 6.055239ms message: 'load-balancer-api-external: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:14:47Z" - latency: 10.12317ms message: 'load-balancer-api-external: resolved host name a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:14:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:06:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 2008f1e9-6e8a-49fe-8b72-0a0c93abc732 resourceVersion: "16182" uid: 75c5c4a1-f7e9-4fd0-b08a-3c80ea556736 spec: sourcePod: network-check-source-7d88cb55d8-nlbz9 targetEndpoint: a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T15:12:47Z" message: 'load-balancer-api-internal: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.759681ms message: 'load-balancer-api-internal: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:18:47Z" - latency: 8.141515ms message: 'load-balancer-api-internal: resolved host name a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:18:47Z" - latency: 4.194911ms message: 'load-balancer-api-internal: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:17:47Z" - latency: 8.183076ms message: 'load-balancer-api-internal: resolved host name a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:17:47Z" - latency: 5.754234ms message: 'load-balancer-api-internal: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:16:47Z" - latency: 7.874451ms message: 'load-balancer-api-internal: resolved host name a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:16:47Z" - latency: 4.857451ms message: 'load-balancer-api-internal: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:15:47Z" - latency: 8.105284ms message: 'load-balancer-api-internal: resolved host name a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:15:47Z" - latency: 6.00878ms message: 'load-balancer-api-internal: tcp connection to a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:14:47Z" - latency: 10.144204ms message: 'load-balancer-api-internal: resolved host name a720f7e89b71846d8a6c795abe87acd2-0e06e09304954c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:14:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:06:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-129-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 2008f1e9-6e8a-49fe-8b72-0a0c93abc732 resourceVersion: "14439" uid: 4b38e093-ca7f-4c9d-b283-c1bf89dd5a69 spec: sourcePod: network-check-source-7d88cb55d8-nlbz9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:13:47Z" message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.743µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:47Z" - latency: 1.452989ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:12:47Z" - latency: 1.453616ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:11:47Z" - latency: 829.647µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:10:47Z" - latency: 844.658µs message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:09:47Z" - latency: 1.339405ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:08:47Z" - latency: 1.222511ms message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:07:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:06:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-131-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 2008f1e9-6e8a-49fe-8b72-0a0c93abc732 resourceVersion: "14440" uid: 05dfdb0e-38c7-46f2-8efa-3231681267fc spec: sourcePod: network-check-source-7d88cb55d8-nlbz9 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:13:47Z" message: 'network-check-target-ip-10-0-131-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.383262ms message: 'network-check-target-ip-10-0-131-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:47Z" - latency: 2.137281ms message: 'network-check-target-ip-10-0-131-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:12:47Z" - latency: 2.312101ms message: 'network-check-target-ip-10-0-131-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:11:47Z" - latency: 1.972662ms message: 'network-check-target-ip-10-0-131-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:10:47Z" - latency: 2.222013ms message: 'network-check-target-ip-10-0-131-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:09:47Z" - latency: 2.312126ms message: 'network-check-target-ip-10-0-131-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:08:47Z" - latency: 2.478134ms message: 'network-check-target-ip-10-0-131-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:07:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:06:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-142-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 2008f1e9-6e8a-49fe-8b72-0a0c93abc732 resourceVersion: "14441" uid: a59dddd0-159e-4564-a4d3-2c42996fba4d spec: sourcePod: network-check-source-7d88cb55d8-nlbz9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:13:47Z" message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.911933ms message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:13:47Z" - latency: 1.984437ms message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:12:47Z" - latency: 2.078363ms message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:11:47Z" - latency: 1.818332ms message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:10:47Z" - latency: 1.904896ms message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:09:47Z" - latency: 1.739775ms message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:08:47Z" - latency: 2.026631ms message: 'network-check-target-ip-10-0-142-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:07:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:06:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-39-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-39.ec2.internal uid: 2008f1e9-6e8a-49fe-8b72-0a0c93abc732 resourceVersion: "16180" uid: 7fd1871e-6f3a-4b3f-a57d-fb663264224b spec: sourcePod: network-check-source-7d88cb55d8-nlbz9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T15:12:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 973.327µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:18:47Z" - latency: 1.517578ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:18:47Z" - latency: 760.58µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:17:47Z" - latency: 1.617641ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:17:47Z" - latency: 1.125265ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:16:47Z" - latency: 1.594988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:16:47Z" - latency: 814.969µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:15:47Z" - latency: 1.795179ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:15:47Z" - latency: 791.077µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:14:47Z" - latency: 2.193275ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:14:47Z" kind: List metadata: resourceVersion: ""