apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T06:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-62-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-62.ec2.internal uid: 227e67e1-6254-4e80-a965-32713df4612d resourceVersion: "38670" uid: 877ff8f8-3660-46bd-b4bf-9c368865cc09 spec: sourcePod: network-check-source-dbd9cf844-5jrzz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T06:17:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.406µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:38:19Z" - latency: 991.096µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:37:19Z" - latency: 969.527µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:36:19Z" - latency: 998.84µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:35:19Z" - latency: 1.444852ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:34:19Z" - latency: 947.428µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:33:19Z" - latency: 973.737µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:32:19Z" - latency: 1.405148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:31:19Z" - latency: 1.084443ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:30:19Z" - latency: 1.172332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:29:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T06:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-62-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-62.ec2.internal uid: 227e67e1-6254-4e80-a965-32713df4612d resourceVersion: "40837" uid: afbeb018-fec2-4f2f-b3d5-ea051ab94fc0 spec: sourcePod: network-check-source-dbd9cf844-5jrzz targetEndpoint: ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T06:16:19Z" message: 'load-balancer-api-external: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.646254ms message: 'load-balancer-api-external: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:40:19Z" - latency: 6.996852ms message: 'load-balancer-api-external: resolved host name ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T06:40:19Z" - latency: 3.70567ms message: 'load-balancer-api-external: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:39:19Z" - latency: 6.742568ms message: 'load-balancer-api-external: resolved host name ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T06:39:19Z" - latency: 4.769097ms message: 'load-balancer-api-external: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:38:19Z" - latency: 6.896962ms message: 'load-balancer-api-external: resolved host name ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T06:38:19Z" - latency: 5.407538ms message: 'load-balancer-api-external: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:37:19Z" - latency: 7.587398ms message: 'load-balancer-api-external: resolved host name ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T06:37:19Z" - latency: 4.759572ms message: 'load-balancer-api-external: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:36:19Z" - latency: 6.233307ms message: 'load-balancer-api-external: resolved host name ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T06:36:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T06:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-62-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-62.ec2.internal uid: 227e67e1-6254-4e80-a965-32713df4612d resourceVersion: "40838" uid: 136223b2-e4cf-47e6-a747-537a2c509ba1 spec: sourcePod: network-check-source-dbd9cf844-5jrzz targetEndpoint: ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T06:16:19Z" message: 'load-balancer-api-internal: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.988775ms message: 'load-balancer-api-internal: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:40:19Z" - latency: 6.983685ms message: 'load-balancer-api-internal: resolved host name ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T06:40:19Z" - latency: 3.686765ms message: 'load-balancer-api-internal: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:39:19Z" - latency: 6.794309ms message: 'load-balancer-api-internal: resolved host name ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T06:39:19Z" - latency: 5.234543ms message: 'load-balancer-api-internal: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:38:19Z" - latency: 6.992051ms message: 'load-balancer-api-internal: resolved host name ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T06:38:19Z" - latency: 5.422811ms message: 'load-balancer-api-internal: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:37:19Z" - latency: 7.631765ms message: 'load-balancer-api-internal: resolved host name ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T06:37:19Z" - latency: 4.696998ms message: 'load-balancer-api-internal: tcp connection to ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:36:19Z" - latency: 6.246226ms message: 'load-balancer-api-internal: resolved host name ac810bc3e17aa469ab478ad8e2eb99ea-d2caa6b51deb9ee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T06:36:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T06:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-62-to-network-check-target-ip-10-0-131-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-62.ec2.internal uid: 227e67e1-6254-4e80-a965-32713df4612d resourceVersion: "38668" uid: 80d9e54f-3ee7-446f-9c61-0d5349d59211 spec: sourcePod: network-check-source-dbd9cf844-5jrzz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T06:17:19Z" message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.876169ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:38:19Z" - latency: 2.224622ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:37:19Z" - latency: 2.044428ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:36:19Z" - latency: 2.261026ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:35:19Z" - latency: 2.062544ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:34:19Z" - latency: 1.967312ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:33:19Z" - latency: 2.308058ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:32:19Z" - latency: 2.251543ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:31:19Z" - latency: 2.139329ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:30:19Z" - latency: 2.145791ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:29:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T06:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-62-to-network-check-target-ip-10-0-132-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-62.ec2.internal uid: 227e67e1-6254-4e80-a965-32713df4612d resourceVersion: "38669" uid: 58066158-1f75-46c1-aa43-f07b1e2ae2be spec: sourcePod: network-check-source-dbd9cf844-5jrzz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T06:17:19Z" message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.42529ms message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:38:19Z" - latency: 2.438795ms message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:37:19Z" - latency: 2.158617ms message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:36:19Z" - latency: 2.25621ms message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:35:19Z" - latency: 2.14961ms message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:34:19Z" - latency: 2.451315ms message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:33:19Z" - latency: 2.338388ms message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:32:19Z" - latency: 2.466788ms message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:31:19Z" - latency: 2.305526ms message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:30:19Z" - latency: 2.615379ms message: 'network-check-target-ip-10-0-132-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:29:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T06:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-62-to-network-check-target-ip-10-0-135-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-62.ec2.internal uid: 227e67e1-6254-4e80-a965-32713df4612d resourceVersion: "38667" uid: 51d305ab-150d-4433-b09c-44a58f77b582 spec: sourcePod: network-check-source-dbd9cf844-5jrzz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T06:17:19Z" message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 953.283µs message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:38:19Z" - latency: 993.088µs message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:37:19Z" - latency: 822.861µs message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:36:19Z" - latency: 889.502µs message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:35:19Z" - latency: 900.625µs message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:34:19Z" - latency: 918.228µs message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:33:19Z" - latency: 906.9µs message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:32:19Z" - latency: 942.168µs message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:31:19Z" - latency: 939.308µs message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:30:19Z" - latency: 1.347639ms message: 'network-check-target-ip-10-0-135-62: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:29:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T06:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-62-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-62.ec2.internal uid: 227e67e1-6254-4e80-a965-32713df4612d resourceVersion: "40835" uid: 6a6bc714-0bd4-469c-8ae8-1f5f814a3fa1 spec: sourcePod: network-check-source-dbd9cf844-5jrzz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T06:16:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013534ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:40:19Z" - latency: 1.904178ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T06:40:19Z" - latency: 1.008596ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:39:19Z" - latency: 1.774729ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T06:39:19Z" - latency: 866.623µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:38:19Z" - latency: 1.987246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T06:38:19Z" - latency: 826.288µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:37:19Z" - latency: 2.340467ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T06:37:19Z" - latency: 1.030575ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T06:36:19Z" - latency: 1.702731ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T06:36:19Z" kind: List metadata: resourceVersion: ""