apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-74-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-74.ec2.internal uid: d03dec51-761c-4517-8cc6-636b2ba4ab49 resourceVersion: "146580" uid: f9d99616-affe-435c-8c2b-c38102379211 spec: sourcePod: network-check-source-6f78d59f99-p9ds4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-29T22:43:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.112467ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:32:45Z" - latency: 3.967784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:31:45Z" - latency: 982.914µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:30:45Z" - latency: 894.808µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:29:45Z" - latency: 1.422293ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:28:45Z" - latency: 1.882876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:27:45Z" - latency: 1.204626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:26:45Z" - latency: 1.482828ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:25:45Z" - latency: 1.660834ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:24:45Z" - latency: 1.61355ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:23:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-74-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-74.ec2.internal uid: d03dec51-761c-4517-8cc6-636b2ba4ab49 resourceVersion: "141530" uid: f2f57170-7137-4b61-9139-141e0dde65bb spec: sourcePod: network-check-source-6f78d59f99-p9ds4 targetEndpoint: ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-29T22:42:45Z" message: 'load-balancer-api-external: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.267643ms message: 'load-balancer-api-external: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:30:45Z" - latency: 7.514638ms message: 'load-balancer-api-external: resolved host name ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:30:45Z" - latency: 29.400378ms message: 'load-balancer-api-external: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:29:45Z" - latency: 7.109079ms message: 'load-balancer-api-external: resolved host name ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:29:45Z" - latency: 18.303396ms message: 'load-balancer-api-external: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:28:45Z" - latency: 14.600978ms message: 'load-balancer-api-external: resolved host name ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:28:45Z" - latency: 18.095343ms message: 'load-balancer-api-external: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:27:45Z" - latency: 9.423142ms message: 'load-balancer-api-external: resolved host name ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:27:45Z" - latency: 16.951498ms message: 'load-balancer-api-external: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:26:45Z" - latency: 8.173993ms message: 'load-balancer-api-external: resolved host name ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:26:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-74-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-74.ec2.internal uid: d03dec51-761c-4517-8cc6-636b2ba4ab49 resourceVersion: "141531" uid: dfb1ed70-3c58-4e97-95e0-048920c4f855 spec: sourcePod: network-check-source-6f78d59f99-p9ds4 targetEndpoint: ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-29T22:42:45Z" message: 'load-balancer-api-internal: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.314671ms message: 'load-balancer-api-internal: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:30:45Z" - latency: 7.481498ms message: 'load-balancer-api-internal: resolved host name ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:30:45Z" - latency: 18.520106ms message: 'load-balancer-api-internal: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:29:45Z" - latency: 6.941729ms message: 'load-balancer-api-internal: resolved host name ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:29:45Z" - latency: 18.303913ms message: 'load-balancer-api-internal: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:28:45Z" - latency: 14.641031ms message: 'load-balancer-api-internal: resolved host name ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:28:45Z" - latency: 16.81934ms message: 'load-balancer-api-internal: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:27:45Z" - latency: 9.348317ms message: 'load-balancer-api-internal: resolved host name ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:27:45Z" - latency: 17.981841ms message: 'load-balancer-api-internal: tcp connection to ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:26:45Z" - latency: 8.227495ms message: 'load-balancer-api-internal: resolved host name ad36bfb8bf7fc4009b69fd7356ecd9d4-fd4b1da3a6977550.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:26:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:43:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-74-to-network-check-target-ip-10-0-130-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-74.ec2.internal uid: d03dec51-761c-4517-8cc6-636b2ba4ab49 resourceVersion: "144383" uid: 4f2559e8-6f97-45c9-bfe2-b35a60d4da3e spec: sourcePod: network-check-source-6f78d59f99-p9ds4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-29T22:50:00Z" message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.798207ms message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:32:00Z" - latency: 3.215504ms message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:31:00Z" - latency: 3.259238ms message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:30:00Z" - latency: 3.188542ms message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:29:00Z" - latency: 2.115139ms message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:28:00Z" - latency: 3.28086ms message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:27:00Z" - latency: 2.115125ms message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:26:00Z" - latency: 2.277873ms message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:25:00Z" - latency: 21.169797ms message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:24:00Z" - latency: 7.966893ms message: 'network-check-target-ip-10-0-130-252: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:23:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:43:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-74-to-network-check-target-ip-10-0-134-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-74.ec2.internal uid: d03dec51-761c-4517-8cc6-636b2ba4ab49 resourceVersion: "145356" uid: 29555b6e-182b-4644-8294-c26f1792d788 spec: sourcePod: network-check-source-6f78d59f99-p9ds4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-29T22:50:17Z" message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.676035ms message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:32:17Z" - latency: 2.117858ms message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:31:17Z" - latency: 2.179039ms message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:30:17Z" - latency: 3.029951ms message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:29:17Z" - latency: 1.783138ms message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:28:17Z" - latency: 3.354443ms message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:27:17Z" - latency: 2.981323ms message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:26:17Z" - latency: 2.067262ms message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:25:17Z" - latency: 2.078335ms message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:24:17Z" - latency: 3.201587ms message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:23:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-74-to-network-check-target-ip-10-0-140-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-74.ec2.internal uid: d03dec51-761c-4517-8cc6-636b2ba4ab49 resourceVersion: "146576" uid: 1a341aa9-e971-48e4-a884-dcba34dc2e53 spec: sourcePod: network-check-source-6f78d59f99-p9ds4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-29T22:43:45Z" message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.031889ms message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:32:45Z" - latency: 3.954814ms message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:31:45Z" - latency: 1.021368ms message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:30:45Z" - latency: 1.286482ms message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:29:45Z" - latency: 1.092703ms message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:28:45Z" - latency: 1.011552ms message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:27:45Z" - latency: 3.068293ms message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:26:45Z" - latency: 1.064855ms message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:25:45Z" - latency: 1.206261ms message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:24:45Z" - latency: 2.184254ms message: 'network-check-target-ip-10-0-140-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:23:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T22:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-74-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-74.ec2.internal uid: d03dec51-761c-4517-8cc6-636b2ba4ab49 resourceVersion: "141528" uid: cc75e8fe-efc5-4e42-9fe1-ce73323cbb60 spec: sourcePod: network-check-source-6f78d59f99-p9ds4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-29T22:42:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.207031ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:30:45Z" - latency: 2.065897ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:30:45Z" - latency: 2.063423ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:29:45Z" - latency: 1.938673ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:29:45Z" - latency: 3.013756ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:28:45Z" - latency: 2.50205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:28:45Z" - latency: 2.352405ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:27:45Z" - latency: 3.487224ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:27:45Z" - latency: 2.395215ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:26:45Z" - latency: 2.68961ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:26:45Z" kind: List metadata: resourceVersion: ""