apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:19:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-127-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-127.ec2.internal uid: 41b9f9d2-9a3d-487b-b68e-bfa5205a1d0e resourceVersion: "63358" uid: 5f723ae3-ef71-4815-8f29-bea91c336f70 spec: sourcePod: network-check-source-7bc5b6bf85-qbgjz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T18:26:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.258µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:01:51Z" - latency: 884.496µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:00:51Z" - latency: 1.084879ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:59:51Z" - latency: 1.192231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:58:51Z" - latency: 1.178438ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:57:51Z" - latency: 1.145745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:56:51Z" - latency: 926.359µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:55:51Z" - latency: 859.631µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:54:51Z" - latency: 1.14742ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:53:51Z" - latency: 1.2284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:52:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:19:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-127-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-127.ec2.internal uid: 41b9f9d2-9a3d-487b-b68e-bfa5205a1d0e resourceVersion: "63360" uid: cb2795b2-9aef-49b6-a827-2c7995ca28ca spec: sourcePod: network-check-source-7bc5b6bf85-qbgjz targetEndpoint: a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T18:25:51Z" message: 'load-balancer-api-external: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.822944ms message: 'load-balancer-api-external: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:01:51Z" - latency: 6.668503ms message: 'load-balancer-api-external: resolved host name a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:01:51Z" - latency: 4.261448ms message: 'load-balancer-api-external: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:00:51Z" - latency: 6.80542ms message: 'load-balancer-api-external: resolved host name a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:00:51Z" - latency: 4.786183ms message: 'load-balancer-api-external: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:59:51Z" - latency: 5.965549ms message: 'load-balancer-api-external: resolved host name a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:59:51Z" - latency: 4.991797ms message: 'load-balancer-api-external: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:58:51Z" - latency: 7.299893ms message: 'load-balancer-api-external: resolved host name a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:58:51Z" - latency: 5.126742ms message: 'load-balancer-api-external: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:57:51Z" - latency: 6.565891ms message: 'load-balancer-api-external: resolved host name a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:57:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:19:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-127-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-127.ec2.internal uid: 41b9f9d2-9a3d-487b-b68e-bfa5205a1d0e resourceVersion: "63359" uid: 10526114-746e-4dc1-b15a-87be7f09c60c spec: sourcePod: network-check-source-7bc5b6bf85-qbgjz targetEndpoint: a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T18:25:51Z" message: 'load-balancer-api-internal: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.408014ms message: 'load-balancer-api-internal: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:01:51Z" - latency: 6.71505ms message: 'load-balancer-api-internal: resolved host name a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:01:51Z" - latency: 4.745351ms message: 'load-balancer-api-internal: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:00:51Z" - latency: 6.62802ms message: 'load-balancer-api-internal: resolved host name a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:00:51Z" - latency: 4.798307ms message: 'load-balancer-api-internal: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:59:51Z" - latency: 5.986357ms message: 'load-balancer-api-internal: resolved host name a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:59:51Z" - latency: 3.815637ms message: 'load-balancer-api-internal: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:58:51Z" - latency: 7.387687ms message: 'load-balancer-api-internal: resolved host name a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:58:51Z" - latency: 4.014541ms message: 'load-balancer-api-internal: tcp connection to a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:57:51Z" - latency: 6.519754ms message: 'load-balancer-api-internal: resolved host name a6b95183a635d4abe8aeaff4a9b7b874-632737c3bd8ecc40.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T18:57:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:19:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-127-to-network-check-target-ip-10-0-135-127 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-127.ec2.internal uid: 41b9f9d2-9a3d-487b-b68e-bfa5205a1d0e resourceVersion: "63354" uid: cef500da-c21d-42e2-a648-2b7b5338a6f8 spec: sourcePod: network-check-source-7bc5b6bf85-qbgjz targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-23T18:26:51Z" message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 751.719µs message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:01:51Z" - latency: 902.821µs message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:00:51Z" - latency: 883.056µs message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:59:51Z" - latency: 1.654411ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:58:51Z" - latency: 874.265µs message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:57:51Z" - latency: 1.170891ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:56:51Z" - latency: 1.270871ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:55:51Z" - latency: 2.065834ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:54:51Z" - latency: 993.222µs message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:53:51Z" - latency: 989.813µs message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:52:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:19:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-127-to-network-check-target-ip-10-0-137-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-127.ec2.internal uid: 41b9f9d2-9a3d-487b-b68e-bfa5205a1d0e resourceVersion: "63355" uid: e999f26f-c077-4eaa-935f-f017bfb2044f spec: sourcePod: network-check-source-7bc5b6bf85-qbgjz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T18:26:51Z" message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.874439ms message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:01:51Z" - latency: 1.978387ms message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:00:51Z" - latency: 2.421006ms message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:59:51Z" - latency: 2.406392ms message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:58:51Z" - latency: 2.393256ms message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:57:51Z" - latency: 2.245727ms message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:56:51Z" - latency: 2.195531ms message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:55:51Z" - latency: 2.182326ms message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:54:51Z" - latency: 2.266164ms message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:53:51Z" - latency: 2.234537ms message: 'network-check-target-ip-10-0-137-146: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:52:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:19:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-127-to-network-check-target-ip-10-0-140-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-127.ec2.internal uid: 41b9f9d2-9a3d-487b-b68e-bfa5205a1d0e resourceVersion: "63356" uid: 4d29589e-13c3-4941-b943-c95f3167098c spec: sourcePod: network-check-source-7bc5b6bf85-qbgjz targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T18:26:51Z" message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.596676ms message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:01:51Z" - latency: 1.510579ms message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:00:51Z" - latency: 1.602123ms message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:59:51Z" - latency: 1.663739ms message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:58:51Z" - latency: 1.65281ms message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:57:51Z" - latency: 1.686983ms message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:56:51Z" - latency: 1.747058ms message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:55:51Z" - latency: 1.804882ms message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:54:51Z" - latency: 1.75275ms message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:53:51Z" - latency: 1.756456ms message: 'network-check-target-ip-10-0-140-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:52:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T18:19:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-127-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-127.ec2.internal uid: 41b9f9d2-9a3d-487b-b68e-bfa5205a1d0e resourceVersion: "63357" uid: 6a18be59-4345-405b-be9e-a06b75daa03b spec: sourcePod: network-check-source-7bc5b6bf85-qbgjz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T18:25:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.11µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:01:51Z" - latency: 1.998329ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T19:01:51Z" - latency: 762.093µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:00:51Z" - latency: 1.746756ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T19:00:51Z" - latency: 905.649µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:59:51Z" - latency: 1.676718ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:59:51Z" - latency: 922.095µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:58:51Z" - latency: 1.908125ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:58:51Z" - latency: 795.544µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T18:57:51Z" - latency: 1.786187ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T18:57:51Z" kind: List metadata: resourceVersion: ""