apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:15:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-161-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-161.ec2.internal uid: ff62e8dd-f02f-4412-951e-195b912bf7ca resourceVersion: "29289" uid: 58e87ba9-f909-46fc-8aa3-d5b9240f5d3b spec: sourcePod: network-check-source-dbd9cf844-8nfrp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T16:22:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 892.43µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:29:28Z" - latency: 1.270167ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:28:28Z" - latency: 1.184124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:27:28Z" - latency: 882.854µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:26:28Z" - latency: 849.722µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:25:28Z" - latency: 1.519858ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:24:28Z" - latency: 987.394µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:23:28Z" - latency: 1.349641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:22:28Z" - latency: 1.166476ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:21:28Z" - latency: 765.45µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:20:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:15:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-161-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-161.ec2.internal uid: ff62e8dd-f02f-4412-951e-195b912bf7ca resourceVersion: "31859" uid: 6168875c-faaa-4e3d-9330-e5fd47ff8495 spec: sourcePod: network-check-source-dbd9cf844-8nfrp targetEndpoint: acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T16:21:29Z" message: 'load-balancer-api-external: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.680543ms message: 'load-balancer-api-external: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:33:29Z" - latency: 6.329967ms message: 'load-balancer-api-external: resolved host name acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:33:28Z" - latency: 5.136775ms message: 'load-balancer-api-external: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:32:29Z" - latency: 6.783932ms message: 'load-balancer-api-external: resolved host name acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:32:28Z" - latency: 4.459896ms message: 'load-balancer-api-external: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:31:29Z" - latency: 6.507749ms message: 'load-balancer-api-external: resolved host name acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:31:28Z" - latency: 4.845664ms message: 'load-balancer-api-external: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:30:29Z" - latency: 6.925394ms message: 'load-balancer-api-external: resolved host name acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:30:28Z" - latency: 4.928213ms message: 'load-balancer-api-external: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:29:29Z" - latency: 7.227884ms message: 'load-balancer-api-external: resolved host name acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:29:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:15:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-161-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-161.ec2.internal uid: ff62e8dd-f02f-4412-951e-195b912bf7ca resourceVersion: "31860" uid: 09427d95-170f-413b-b6e0-c41f2b3fef87 spec: sourcePod: network-check-source-dbd9cf844-8nfrp targetEndpoint: acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T16:21:29Z" message: 'load-balancer-api-internal: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.852334ms message: 'load-balancer-api-internal: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:33:29Z" - latency: 6.257978ms message: 'load-balancer-api-internal: resolved host name acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:33:28Z" - latency: 5.147254ms message: 'load-balancer-api-internal: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:32:29Z" - latency: 6.685719ms message: 'load-balancer-api-internal: resolved host name acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:32:28Z" - latency: 4.475993ms message: 'load-balancer-api-internal: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:31:29Z" - latency: 6.360815ms message: 'load-balancer-api-internal: resolved host name acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:31:28Z" - latency: 4.797468ms message: 'load-balancer-api-internal: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:30:29Z" - latency: 6.857535ms message: 'load-balancer-api-internal: resolved host name acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:30:28Z" - latency: 4.957237ms message: 'load-balancer-api-internal: tcp connection to acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:29:29Z" - latency: 7.297561ms message: 'load-balancer-api-internal: resolved host name acd0c74b642504a459754eb7f7320dd1-88eae02659dfa024.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:29:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:15:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-161-to-network-check-target-ip-10-0-128-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-161.ec2.internal uid: ff62e8dd-f02f-4412-951e-195b912bf7ca resourceVersion: "29286" uid: 2464dfa2-4218-42b5-92d5-2c9eef4f4d51 spec: sourcePod: network-check-source-dbd9cf844-8nfrp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:22:29Z" message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 782.753µs message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:29:28Z" - latency: 1.066966ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:28:28Z" - latency: 1.251326ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:27:28Z" - latency: 1.456884ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:26:28Z" - latency: 1.44394ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:25:28Z" - latency: 1.219809ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:24:28Z" - latency: 1.386068ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:23:28Z" - latency: 809.883µs message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:22:28Z" - latency: 1.223063ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:21:28Z" - latency: 930.267µs message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:20:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:15:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-161-to-network-check-target-ip-10-0-138-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-161.ec2.internal uid: ff62e8dd-f02f-4412-951e-195b912bf7ca resourceVersion: "29287" uid: ced6f56a-e848-4498-9e49-6cfcb6c46d0c spec: sourcePod: network-check-source-dbd9cf844-8nfrp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:22:29Z" message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.327668ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:29:28Z" - latency: 2.389496ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:28:28Z" - latency: 2.027502ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:27:28Z" - latency: 2.294138ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:26:28Z" - latency: 2.19348ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:25:28Z" - latency: 2.224996ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:24:28Z" - latency: 2.321188ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:23:28Z" - latency: 2.31068ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:22:28Z" - latency: 2.127293ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:21:28Z" - latency: 2.483543ms message: 'network-check-target-ip-10-0-138-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:20:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:15:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-161-to-network-check-target-ip-10-0-140-111 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-161.ec2.internal uid: ff62e8dd-f02f-4412-951e-195b912bf7ca resourceVersion: "29288" uid: db8c0924-fc3d-4b76-a48c-628d33f326e1 spec: sourcePod: network-check-source-dbd9cf844-8nfrp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:22:29Z" message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.013295ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:29:28Z" - latency: 2.340765ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:28:28Z" - latency: 2.629511ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:27:28Z" - latency: 2.384573ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:26:28Z" - latency: 2.229777ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:25:28Z" - latency: 2.177332ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:24:28Z" - latency: 2.567935ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:23:28Z" - latency: 2.247817ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:22:28Z" - latency: 2.306122ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:21:28Z" - latency: 2.965761ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:20:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:15:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-161-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-161.ec2.internal uid: ff62e8dd-f02f-4412-951e-195b912bf7ca resourceVersion: "31858" uid: 44ba8dd0-83a4-42d4-8e2d-70f8da4f52d8 spec: sourcePod: network-check-source-dbd9cf844-8nfrp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T16:21:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 732.866µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:33:28Z" - latency: 1.599574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:33:28Z" - latency: 985.752µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:32:28Z" - latency: 1.964647ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:32:28Z" - latency: 820.775µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:31:28Z" - latency: 1.554725ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:31:28Z" - latency: 931.46µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:30:29Z" - latency: 1.788146ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:30:28Z" - latency: 949.821µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:29:29Z" - latency: 2.254445ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:29:28Z" kind: List metadata: resourceVersion: ""