apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T19:46:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-191-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-191.ec2.internal uid: ba090137-d17f-4a90-8048-4bef96ca066f resourceVersion: "36525" uid: 5cbe73e9-2299-4bb9-90ee-158df33cc919 spec: sourcePod: network-check-source-7f44b6dd87-7fmqd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T19:53:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.180781ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:14:07Z" - latency: 999.176µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:13:07Z" - latency: 1.273634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:12:07Z" - latency: 1.089051ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:11:07Z" - latency: 1.411335ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:10:07Z" - latency: 1.470187ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:09:07Z" - latency: 1.019854ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:08:07Z" - latency: 1.123789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:07:07Z" - latency: 888.308µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:06:07Z" - latency: 925.403µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T19:46:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-191-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-191.ec2.internal uid: ba090137-d17f-4a90-8048-4bef96ca066f resourceVersion: "32995" uid: 6d9eda77-739f-44d5-90ea-22d4379ee6d2 spec: sourcePod: network-check-source-7f44b6dd87-7fmqd targetEndpoint: a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T19:52:07Z" message: 'load-balancer-api-external: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.94461ms message: 'load-balancer-api-external: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:10:07Z" - latency: 8.070745ms message: 'load-balancer-api-external: resolved host name a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T20:10:07Z" - latency: 4.78798ms message: 'load-balancer-api-external: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:09:07Z" - latency: 8.016756ms message: 'load-balancer-api-external: resolved host name a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T20:09:07Z" - latency: 4.082501ms message: 'load-balancer-api-external: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:08:07Z" - latency: 8.661507ms message: 'load-balancer-api-external: resolved host name a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T20:08:07Z" - latency: 4.243832ms message: 'load-balancer-api-external: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:07:07Z" - latency: 7.691535ms message: 'load-balancer-api-external: resolved host name a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T20:07:07Z" - latency: 4.857511ms message: 'load-balancer-api-external: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:06:07Z" - latency: 8.22736ms message: 'load-balancer-api-external: resolved host name a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T20:06:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T19:46:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-191-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-191.ec2.internal uid: ba090137-d17f-4a90-8048-4bef96ca066f resourceVersion: "32996" uid: 34d6c880-aace-4b4a-8334-21f7a654bc17 spec: sourcePod: network-check-source-7f44b6dd87-7fmqd targetEndpoint: a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T19:52:07Z" message: 'load-balancer-api-internal: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.717365ms message: 'load-balancer-api-internal: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:10:07Z" - latency: 8.03217ms message: 'load-balancer-api-internal: resolved host name a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T20:10:07Z" - latency: 7.006527ms message: 'load-balancer-api-internal: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:09:07Z" - latency: 8.09056ms message: 'load-balancer-api-internal: resolved host name a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T20:09:07Z" - latency: 4.529976ms message: 'load-balancer-api-internal: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:08:07Z" - latency: 8.630435ms message: 'load-balancer-api-internal: resolved host name a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T20:08:07Z" - latency: 5.305244ms message: 'load-balancer-api-internal: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:07:07Z" - latency: 7.654574ms message: 'load-balancer-api-internal: resolved host name a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T20:07:07Z" - latency: 6.336028ms message: 'load-balancer-api-internal: tcp connection to a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:06:07Z" - latency: 8.306825ms message: 'load-balancer-api-internal: resolved host name a730c49b7089646ac8c20812d55283bc-7a32bca44a8767d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T20:06:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T19:46:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-191-to-network-check-target-ip-10-0-135-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-191.ec2.internal uid: ba090137-d17f-4a90-8048-4bef96ca066f resourceVersion: "36522" uid: 76365ba1-c0f3-44d7-931a-476bb5cc8dcd spec: sourcePod: network-check-source-7f44b6dd87-7fmqd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T19:53:07Z" message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.418756ms message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:14:07Z" - latency: 1.513521ms message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:13:07Z" - latency: 1.227391ms message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:12:07Z" - latency: 1.021261ms message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:11:07Z" - latency: 809.198µs message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:10:07Z" - latency: 834.956µs message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:09:07Z" - latency: 915.765µs message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:08:07Z" - latency: 926.362µs message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:07:07Z" - latency: 1.274902ms message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:06:07Z" - latency: 1.373449ms message: 'network-check-target-ip-10-0-135-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T19:46:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-191-to-network-check-target-ip-10-0-138-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-191.ec2.internal uid: ba090137-d17f-4a90-8048-4bef96ca066f resourceVersion: "36523" uid: 91342ec3-2814-4772-814d-94b6c2fefdeb spec: sourcePod: network-check-source-7f44b6dd87-7fmqd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T19:53:07Z" message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.369123ms message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:14:07Z" - latency: 2.460715ms message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:13:07Z" - latency: 2.42769ms message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:12:07Z" - latency: 2.034927ms message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:11:07Z" - latency: 2.329133ms message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:10:07Z" - latency: 1.98303ms message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:09:07Z" - latency: 2.256583ms message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:08:07Z" - latency: 2.358951ms message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:07:07Z" - latency: 2.14671ms message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:06:07Z" - latency: 1.797013ms message: 'network-check-target-ip-10-0-138-195: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T19:46:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-191-to-network-check-target-ip-10-0-138-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-191.ec2.internal uid: ba090137-d17f-4a90-8048-4bef96ca066f resourceVersion: "36524" uid: 50b0fe64-21bc-41d1-858f-1a12bf16fa67 spec: sourcePod: network-check-source-7f44b6dd87-7fmqd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T19:53:07Z" message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.296946ms message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:14:07Z" - latency: 2.306476ms message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:13:07Z" - latency: 3.488052ms message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:12:07Z" - latency: 1.94126ms message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:11:07Z" - latency: 2.617503ms message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:10:07Z" - latency: 2.046231ms message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:09:07Z" - latency: 2.233066ms message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:08:07Z" - latency: 2.259963ms message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:07:07Z" - latency: 2.205169ms message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:06:07Z" - latency: 2.297536ms message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T19:46:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-191-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-191.ec2.internal uid: ba090137-d17f-4a90-8048-4bef96ca066f resourceVersion: "32994" uid: 5351080f-2924-4766-a35a-e437a1a0762b spec: sourcePod: network-check-source-7f44b6dd87-7fmqd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T19:52:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 677.827µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:10:07Z" - latency: 1.773857ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T20:10:07Z" - latency: 800.079µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:09:07Z" - latency: 1.766122ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T20:09:07Z" - latency: 905.496µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:08:07Z" - latency: 1.671983ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T20:08:07Z" - latency: 980.209µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:07:07Z" - latency: 1.70384ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T20:07:07Z" - latency: 880.703µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T20:06:07Z" - latency: 1.58677ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T20:06:07Z" kind: List metadata: resourceVersion: ""