apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-155-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-155.ec2.internal uid: ddb19e82-d531-4d9b-a48b-566b8367dcbd resourceVersion: "17761" uid: ce50e3f3-4b3b-4bba-be2f-804dcfcdd8b6 spec: sourcePod: network-check-source-dbd9cf844-ltkcm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T13:32:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 909.022µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:44Z" - latency: 811.829µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:44Z" - latency: 1.046554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:44Z" - latency: 793.617µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:44Z" - latency: 846.716µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:44Z" - latency: 866.497µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:44Z" - latency: 908.309µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:44Z" - latency: 1.339384ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:32:44Z" - latency: 1.008898ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:31:44Z" - latency: 1.245987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-155-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-155.ec2.internal uid: ddb19e82-d531-4d9b-a48b-566b8367dcbd resourceVersion: "17110" uid: 28de62ae-4501-4ad6-bacd-e36fc75fab15 spec: sourcePod: network-check-source-dbd9cf844-ltkcm targetEndpoint: ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T13:31:44Z" message: 'load-balancer-api-external: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.814701ms message: 'load-balancer-api-external: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:44Z" - latency: 6.93232ms message: 'load-balancer-api-external: resolved host name ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:37:44Z" - latency: 5.543681ms message: 'load-balancer-api-external: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:44Z" - latency: 6.896665ms message: 'load-balancer-api-external: resolved host name ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:36:44Z" - latency: 6.32688ms message: 'load-balancer-api-external: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:44Z" - latency: 6.800084ms message: 'load-balancer-api-external: resolved host name ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:35:44Z" - latency: 6.169592ms message: 'load-balancer-api-external: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:44Z" - latency: 6.446515ms message: 'load-balancer-api-external: resolved host name ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:34:44Z" - latency: 4.369009ms message: 'load-balancer-api-external: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:44Z" - latency: 6.194524ms message: 'load-balancer-api-external: resolved host name ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:33:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-155-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-155.ec2.internal uid: ddb19e82-d531-4d9b-a48b-566b8367dcbd resourceVersion: "17109" uid: 6aea5564-7fd5-4700-992c-98ab328f425c spec: sourcePod: network-check-source-dbd9cf844-ltkcm targetEndpoint: ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T13:31:44Z" message: 'load-balancer-api-internal: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.843754ms message: 'load-balancer-api-internal: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:44Z" - latency: 6.99122ms message: 'load-balancer-api-internal: resolved host name ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:37:44Z" - latency: 5.533493ms message: 'load-balancer-api-internal: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:44Z" - latency: 6.913899ms message: 'load-balancer-api-internal: resolved host name ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:36:44Z" - latency: 5.970645ms message: 'load-balancer-api-internal: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:44Z" - latency: 6.775727ms message: 'load-balancer-api-internal: resolved host name ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:35:44Z" - latency: 5.607908ms message: 'load-balancer-api-internal: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:44Z" - latency: 6.412837ms message: 'load-balancer-api-internal: resolved host name ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:34:44Z" - latency: 5.338677ms message: 'load-balancer-api-internal: tcp connection to ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:44Z" - latency: 6.1141ms message: 'load-balancer-api-internal: resolved host name ae5059820fdf449558e818f64fc4bdb3-fd7795654dd530ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:33:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-155-to-network-check-target-ip-10-0-128-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-155.ec2.internal uid: ddb19e82-d531-4d9b-a48b-566b8367dcbd resourceVersion: "17760" uid: 691d77c6-057d-462b-a705-912eb55115dd spec: sourcePod: network-check-source-dbd9cf844-ltkcm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:32:44Z" message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.523696ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:44Z" - latency: 2.143892ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:44Z" - latency: 2.095568ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:44Z" - latency: 2.249951ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:44Z" - latency: 1.929627ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:44Z" - latency: 2.145583ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:44Z" - latency: 2.455928ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:44Z" - latency: 2.754802ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:32:44Z" - latency: 2.319586ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:31:44Z" - latency: 2.372253ms message: 'network-check-target-ip-10-0-128-54: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-155-to-network-check-target-ip-10-0-139-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-155.ec2.internal uid: ddb19e82-d531-4d9b-a48b-566b8367dcbd resourceVersion: "17758" uid: ac01b825-8175-4ba8-8109-1526baae7c89 spec: sourcePod: network-check-source-dbd9cf844-ltkcm targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:32:44Z" message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.47µs message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:44Z" - latency: 1.100176ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:44Z" - latency: 929.543µs message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:44Z" - latency: 769.798µs message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:44Z" - latency: 956.537µs message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:44Z" - latency: 907.431µs message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:44Z" - latency: 961.267µs message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:44Z" - latency: 1.147414ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:32:44Z" - latency: 883.759µs message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:31:44Z" - latency: 819.851µs message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-155-to-network-check-target-ip-10-0-142-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-155.ec2.internal uid: ddb19e82-d531-4d9b-a48b-566b8367dcbd resourceVersion: "17759" uid: 7c0fe482-1f1d-482f-a505-9561c9ecdee2 spec: sourcePod: network-check-source-dbd9cf844-ltkcm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:32:44Z" message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.182437ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:44Z" - latency: 2.452387ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:44Z" - latency: 2.3065ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:44Z" - latency: 2.083776ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:44Z" - latency: 2.200843ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:44Z" - latency: 2.320461ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:44Z" - latency: 2.173647ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:44Z" - latency: 2.686597ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:32:44Z" - latency: 2.228877ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:31:44Z" - latency: 2.026343ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-155-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-155.ec2.internal uid: ddb19e82-d531-4d9b-a48b-566b8367dcbd resourceVersion: "17108" uid: 45d3120b-d770-4f90-9228-0b748ea1a203 spec: sourcePod: network-check-source-dbd9cf844-ltkcm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T13:31:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.092µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:44Z" - latency: 1.680094ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:37:44Z" - latency: 839.495µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:44Z" - latency: 1.644871ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:36:44Z" - latency: 759.258µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:44Z" - latency: 1.777658ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:35:44Z" - latency: 1.147107ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:44Z" - latency: 1.763311ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:34:44Z" - latency: 809.667µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:44Z" - latency: 1.770154ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:33:44Z" kind: List metadata: resourceVersion: ""