apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T21:12:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 69bb059c-e47c-47b0-96da-57a6da78455f resourceVersion: "64740" uid: c575a30b-eb40-417c-af88-27b67d82c0f1 spec: sourcePod: network-check-source-7bc5b6bf85-tlln9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T21:19:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.035476ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:54:12Z" - latency: 958.116µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:53:12Z" - latency: 1.020124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:52:12Z" - latency: 1.132326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:51:12Z" - latency: 1.096436ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:50:12Z" - latency: 811.079µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:49:12Z" - latency: 1.016031ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:48:12Z" - latency: 1.025574ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:47:12Z" - latency: 998.991µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:46:12Z" - latency: 872.293µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:45:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T21:12:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 69bb059c-e47c-47b0-96da-57a6da78455f resourceVersion: "64741" uid: d6495c0f-64c1-4ed5-888b-c7fc18c266ef spec: sourcePod: network-check-source-7bc5b6bf85-tlln9 targetEndpoint: ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T21:18:12Z" message: 'load-balancer-api-external: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.309777ms message: 'load-balancer-api-external: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:54:12Z" - latency: 12.684114ms message: 'load-balancer-api-external: resolved host name ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T21:54:12Z" - latency: 5.073272ms message: 'load-balancer-api-external: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:53:12Z" - latency: 8.657679ms message: 'load-balancer-api-external: resolved host name ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T21:53:12Z" - latency: 5.231586ms message: 'load-balancer-api-external: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:52:12Z" - latency: 13.500778ms message: 'load-balancer-api-external: resolved host name ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T21:52:12Z" - latency: 5.237995ms message: 'load-balancer-api-external: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:51:12Z" - latency: 7.357391ms message: 'load-balancer-api-external: resolved host name ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T21:51:12Z" - latency: 4.898407ms message: 'load-balancer-api-external: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:50:12Z" - latency: 14.772918ms message: 'load-balancer-api-external: resolved host name ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T21:50:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T21:12:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 69bb059c-e47c-47b0-96da-57a6da78455f resourceVersion: "64742" uid: 4f3386f9-c249-4db5-972d-b986e419f39e spec: sourcePod: network-check-source-7bc5b6bf85-tlln9 targetEndpoint: ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T21:18:12Z" message: 'load-balancer-api-internal: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.319893ms message: 'load-balancer-api-internal: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:54:12Z" - latency: 12.851922ms message: 'load-balancer-api-internal: resolved host name ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T21:54:12Z" - latency: 5.070357ms message: 'load-balancer-api-internal: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:53:12Z" - latency: 8.753866ms message: 'load-balancer-api-internal: resolved host name ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T21:53:12Z" - latency: 4.869456ms message: 'load-balancer-api-internal: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:52:12Z" - latency: 13.519454ms message: 'load-balancer-api-internal: resolved host name ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T21:52:12Z" - latency: 4.765375ms message: 'load-balancer-api-internal: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:51:12Z" - latency: 7.386561ms message: 'load-balancer-api-internal: resolved host name ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T21:51:12Z" - latency: 4.876937ms message: 'load-balancer-api-internal: tcp connection to ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:50:12Z" - latency: 14.828551ms message: 'load-balancer-api-internal: resolved host name ad6c99d8a435b40a6b0998d6a57e1460-b4c21136332fd664.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T21:50:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T21:12:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-network-check-target-ip-10-0-135-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 69bb059c-e47c-47b0-96da-57a6da78455f resourceVersion: "64738" uid: 14471b27-005a-4479-88b5-9f3747575c6e spec: sourcePod: network-check-source-7bc5b6bf85-tlln9 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T21:19:12Z" message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.489353ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:54:12Z" - latency: 2.341409ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:53:12Z" - latency: 2.809825ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:52:12Z" - latency: 2.175094ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:51:12Z" - latency: 2.086891ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:50:12Z" - latency: 1.822051ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:49:12Z" - latency: 2.243255ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:48:12Z" - latency: 2.102073ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:47:12Z" - latency: 2.339393ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:46:12Z" - latency: 1.969789ms message: 'network-check-target-ip-10-0-135-37: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:45:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T21:12:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-network-check-target-ip-10-0-137-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 69bb059c-e47c-47b0-96da-57a6da78455f resourceVersion: "64736" uid: c4d5b31f-95fe-4c3d-b400-3fa6a146186f spec: sourcePod: network-check-source-7bc5b6bf85-tlln9 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T21:19:12Z" message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 932.774µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:54:12Z" - latency: 1.08267ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:53:12Z" - latency: 1.035154ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:52:12Z" - latency: 881.562µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:51:12Z" - latency: 907.867µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:50:12Z" - latency: 847.369µs message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:49:12Z" - latency: 1.02349ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:48:12Z" - latency: 1.226697ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:47:12Z" - latency: 1.977107ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:46:12Z" - latency: 1.013807ms message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:45:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T21:12:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-network-check-target-ip-10-0-142-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 69bb059c-e47c-47b0-96da-57a6da78455f resourceVersion: "64739" uid: f411d663-4387-438c-9424-b3139a9228a5 spec: sourcePod: network-check-source-7bc5b6bf85-tlln9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T21:19:12Z" message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.292878ms message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:54:12Z" - latency: 2.320305ms message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:53:12Z" - latency: 2.461792ms message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:52:12Z" - latency: 2.652284ms message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:51:12Z" - latency: 2.129645ms message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:50:12Z" - latency: 2.372767ms message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:49:12Z" - latency: 2.270484ms message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:48:12Z" - latency: 2.119503ms message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:47:12Z" - latency: 2.01505ms message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:46:12Z" - latency: 2.175261ms message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:45:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T21:12:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-63-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-63.ec2.internal uid: 69bb059c-e47c-47b0-96da-57a6da78455f resourceVersion: "64737" uid: 9328c28b-3f28-4a4f-8dbc-df6a4c8a347b spec: sourcePod: network-check-source-7bc5b6bf85-tlln9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T21:18:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:54:12Z" - latency: 2.023996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T21:54:12Z" - latency: 810.612µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:53:12Z" - latency: 1.986966ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T21:53:12Z" - latency: 1.230012ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:52:12Z" - latency: 1.787488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T21:52:12Z" - latency: 1.088709ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:51:12Z" - latency: 1.998856ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T21:51:12Z" - latency: 868.772µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T21:50:12Z" - latency: 1.542275ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T21:50:12Z" kind: List metadata: resourceVersion: ""