apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:41:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-38-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-38.ec2.internal uid: 99e1046c-4c3d-4437-a664-817bbaf61a58 resourceVersion: "54396" uid: eeffaaa5-0037-412c-afff-6141d6badc22 spec: sourcePod: network-check-source-989f8b8dc-dv6x4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T17:48:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.253802ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:16:56Z" - latency: 1.142259ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:15:56Z" - latency: 1.181484ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:14:56Z" - latency: 862.14µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:13:56Z" - latency: 898.595µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:12:56Z" - latency: 1.285723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:11:56Z" - latency: 1.093032ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:10:56Z" - latency: 1.903124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:09:56Z" - latency: 1.022691ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:08:56Z" - latency: 1.210384ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:07:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:41:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-38-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-38.ec2.internal uid: 99e1046c-4c3d-4437-a664-817bbaf61a58 resourceVersion: "49517" uid: 59ca121b-f3c8-4beb-81ad-d7501e0c7fc2 spec: sourcePod: network-check-source-989f8b8dc-dv6x4 targetEndpoint: a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T17:47:56Z" message: 'load-balancer-api-external: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.839212ms message: 'load-balancer-api-external: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:11:56Z" - latency: 8.550806ms message: 'load-balancer-api-external: resolved host name a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:11:56Z" - latency: 4.371909ms message: 'load-balancer-api-external: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:10:56Z" - latency: 7.093211ms message: 'load-balancer-api-external: resolved host name a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:10:56Z" - latency: 10.478065ms message: 'load-balancer-api-external: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:09:56Z" - latency: 8.059389ms message: 'load-balancer-api-external: resolved host name a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:09:56Z" - latency: 4.286397ms message: 'load-balancer-api-external: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:08:56Z" - latency: 6.871335ms message: 'load-balancer-api-external: resolved host name a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:08:56Z" - latency: 5.553674ms message: 'load-balancer-api-external: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:07:56Z" - latency: 7.007762ms message: 'load-balancer-api-external: resolved host name a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:07:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:41:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-38-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-38.ec2.internal uid: 99e1046c-4c3d-4437-a664-817bbaf61a58 resourceVersion: "49516" uid: eadbadcc-42a1-48a0-86fc-a97d36ed74d8 spec: sourcePod: network-check-source-989f8b8dc-dv6x4 targetEndpoint: a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T17:47:56Z" message: 'load-balancer-api-internal: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.876795ms message: 'load-balancer-api-internal: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:11:56Z" - latency: 8.53925ms message: 'load-balancer-api-internal: resolved host name a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:11:56Z" - latency: 4.347349ms message: 'load-balancer-api-internal: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:10:56Z" - latency: 7.137537ms message: 'load-balancer-api-internal: resolved host name a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:10:56Z" - latency: 5.090348ms message: 'load-balancer-api-internal: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:09:56Z" - latency: 8.004985ms message: 'load-balancer-api-internal: resolved host name a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:09:56Z" - latency: 5.283291ms message: 'load-balancer-api-internal: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:08:56Z" - latency: 6.814741ms message: 'load-balancer-api-internal: resolved host name a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:08:56Z" - latency: 5.867284ms message: 'load-balancer-api-internal: tcp connection to a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:07:56Z" - latency: 6.979245ms message: 'load-balancer-api-internal: resolved host name a743a6dfc86784bc280478e8df50b4c5-88cca94a2ec12da8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:07:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:41:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-38-to-network-check-target-ip-10-0-130-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-38.ec2.internal uid: 99e1046c-4c3d-4437-a664-817bbaf61a58 resourceVersion: "54393" uid: 14769a97-c5e9-488f-951f-be1c1ef00790 spec: sourcePod: network-check-source-989f8b8dc-dv6x4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T17:48:56Z" message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.405574ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:16:56Z" - latency: 808.867µs message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:15:56Z" - latency: 900.888µs message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:14:56Z" - latency: 1.08927ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:13:56Z" - latency: 994.367µs message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:12:56Z" - latency: 1.42838ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:11:56Z" - latency: 1.332015ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:10:56Z" - latency: 898.747µs message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:09:56Z" - latency: 1.041967ms message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:08:56Z" - latency: 971.239µs message: 'network-check-target-ip-10-0-130-38: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:07:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:41:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-38-to-network-check-target-ip-10-0-141-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-38.ec2.internal uid: 99e1046c-4c3d-4437-a664-817bbaf61a58 resourceVersion: "54395" uid: 81b7ae90-fad8-4d49-adf7-8ade6eca1b51 spec: sourcePod: network-check-source-989f8b8dc-dv6x4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T17:48:56Z" message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.245687ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:16:56Z" - latency: 2.419117ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:15:56Z" - latency: 2.126319ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:14:56Z" - latency: 2.08693ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:13:56Z" - latency: 2.161635ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:12:56Z" - latency: 1.987498ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:11:56Z" - latency: 2.059337ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:10:56Z" - latency: 2.363852ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:09:56Z" - latency: 2.19356ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:08:56Z" - latency: 1.995553ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:07:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:41:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-38-to-network-check-target-ip-10-0-142-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-38.ec2.internal uid: 99e1046c-4c3d-4437-a664-817bbaf61a58 resourceVersion: "54394" uid: d96b3874-562b-4740-b6ca-87ddeb252492 spec: sourcePod: network-check-source-989f8b8dc-dv6x4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T17:48:56Z" message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.341548ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:16:56Z" - latency: 1.669628ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:15:56Z" - latency: 1.887746ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:14:56Z" - latency: 1.740981ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:13:56Z" - latency: 2.177731ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:12:56Z" - latency: 3.289302ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:11:56Z" - latency: 2.042171ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:10:56Z" - latency: 1.998926ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:09:56Z" - latency: 1.77085ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:08:56Z" - latency: 1.944379ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:07:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T17:41:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-38-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-38.ec2.internal uid: 99e1046c-4c3d-4437-a664-817bbaf61a58 resourceVersion: "49515" uid: f4b1ad56-67b5-408e-8b27-b325259c2454 spec: sourcePod: network-check-source-989f8b8dc-dv6x4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T17:47:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.706913ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:11:56Z" - latency: 1.591882ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:11:56Z" - latency: 1.097777ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:10:56Z" - latency: 2.038727ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:10:56Z" - latency: 1.116205ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:09:56Z" - latency: 2.006333ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:09:56Z" - latency: 939.521µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:08:56Z" - latency: 1.800277ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:08:56Z" - latency: 838.565µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:07:56Z" - latency: 1.763756ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:07:56Z" kind: List metadata: resourceVersion: ""