apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:45:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-135-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-135.ec2.internal uid: 67d94752-c957-45df-bc7e-75a306db674d resourceVersion: "54684" uid: f12cdbd1-70d1-4866-bbd7-2497ef0219bf spec: sourcePod: network-check-source-989f8b8dc-cn42m targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T23:52:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.574573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:55Z" - latency: 845.167µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:55Z" - latency: 1.150791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:55Z" - latency: 953.743µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:55Z" - latency: 1.302873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:16:55Z" - latency: 1.300436ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:15:55Z" - latency: 1.084993ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:14:55Z" - latency: 890.986µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:13:55Z" - latency: 1.136289ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:12:55Z" - latency: 1.175648ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:11:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:45:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-135-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-135.ec2.internal uid: 67d94752-c957-45df-bc7e-75a306db674d resourceVersion: "55583" uid: 9da3f7d2-5e8a-4eee-8782-1e21563e390c spec: sourcePod: network-check-source-989f8b8dc-cn42m targetEndpoint: af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T23:51:55Z" message: 'load-balancer-api-external: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.030225ms message: 'load-balancer-api-external: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:55Z" - latency: 8.942608ms message: 'load-balancer-api-external: resolved host name af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:21:55Z" - latency: 5.476819ms message: 'load-balancer-api-external: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:55Z" - latency: 16.534456ms message: 'load-balancer-api-external: resolved host name af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:20:55Z" - latency: 4.641267ms message: 'load-balancer-api-external: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:55Z" - latency: 9.044072ms message: 'load-balancer-api-external: resolved host name af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:19:55Z" - latency: 4.865232ms message: 'load-balancer-api-external: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:55Z" - latency: 9.451867ms message: 'load-balancer-api-external: resolved host name af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:18:55Z" - latency: 4.090307ms message: 'load-balancer-api-external: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:55Z" - latency: 9.174078ms message: 'load-balancer-api-external: resolved host name af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:17:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:45:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-135-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-135.ec2.internal uid: 67d94752-c957-45df-bc7e-75a306db674d resourceVersion: "55582" uid: 41a83fc3-9d39-488e-ab11-a90669a48fbb spec: sourcePod: network-check-source-989f8b8dc-cn42m targetEndpoint: af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T23:51:55Z" message: 'load-balancer-api-internal: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.034519ms message: 'load-balancer-api-internal: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:55Z" - latency: 8.98479ms message: 'load-balancer-api-internal: resolved host name af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:21:55Z" - latency: 4.657304ms message: 'load-balancer-api-internal: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:55Z" - latency: 16.591435ms message: 'load-balancer-api-internal: resolved host name af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:20:55Z" - latency: 4.664907ms message: 'load-balancer-api-internal: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:55Z" - latency: 9.073092ms message: 'load-balancer-api-internal: resolved host name af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:19:55Z" - latency: 4.835027ms message: 'load-balancer-api-internal: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:55Z" - latency: 9.484378ms message: 'load-balancer-api-internal: resolved host name af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:18:55Z" - latency: 4.015208ms message: 'load-balancer-api-internal: tcp connection to af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:55Z" - latency: 9.23022ms message: 'load-balancer-api-internal: resolved host name af3f7ef01ad534a63940c232334fa90d-c223979a15332274.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:17:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:45:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-135-to-network-check-target-ip-10-0-132-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-135.ec2.internal uid: 67d94752-c957-45df-bc7e-75a306db674d resourceVersion: "54683" uid: d420d595-674e-4edf-9853-7b8fca07594f spec: sourcePod: network-check-source-989f8b8dc-cn42m targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:52:55Z" message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.299406ms message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:55Z" - latency: 2.732925ms message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:55Z" - latency: 1.87133ms message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:55Z" - latency: 2.35624ms message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:55Z" - latency: 2.445569ms message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:16:55Z" - latency: 2.461592ms message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:15:55Z" - latency: 2.258008ms message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:14:55Z" - latency: 2.67547ms message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:13:55Z" - latency: 2.407469ms message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:12:55Z" - latency: 2.139517ms message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:11:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:45:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-135-to-network-check-target-ip-10-0-135-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-135.ec2.internal uid: 67d94752-c957-45df-bc7e-75a306db674d resourceVersion: "54681" uid: b88c22d7-736c-43a8-815f-fe35b7faa696 spec: sourcePod: network-check-source-989f8b8dc-cn42m targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:52:55Z" message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.800984ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:55Z" - latency: 1.942026ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:55Z" - latency: 1.901195ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:55Z" - latency: 1.927792ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:55Z" - latency: 1.848961ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:16:55Z" - latency: 1.883761ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:15:55Z" - latency: 1.74406ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:14:55Z" - latency: 1.921193ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:13:55Z" - latency: 1.80382ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:12:55Z" - latency: 2.322093ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:11:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:45:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-135-to-network-check-target-ip-10-0-141-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-135.ec2.internal uid: 67d94752-c957-45df-bc7e-75a306db674d resourceVersion: "54682" uid: 2e1cc62a-8640-4888-a2e1-647b2d67e343 spec: sourcePod: network-check-source-989f8b8dc-cn42m targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:52:55Z" message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.613392ms message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:55Z" - latency: 1.176862ms message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:55Z" - latency: 1.05909ms message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:55Z" - latency: 1.228203ms message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:55Z" - latency: 942.815µs message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:16:55Z" - latency: 1.032261ms message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:15:55Z" - latency: 1.229389ms message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:14:55Z" - latency: 1.180766ms message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:13:55Z" - latency: 897.447µs message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:12:55Z" - latency: 925.442µs message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:11:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:45:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-135-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-135.ec2.internal uid: 67d94752-c957-45df-bc7e-75a306db674d resourceVersion: "55581" uid: 8c972264-39c6-4350-a0a2-2b1cf23cd541 spec: sourcePod: network-check-source-989f8b8dc-cn42m targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T23:51:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.225059ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:55Z" - latency: 1.914491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:21:55Z" - latency: 914.729µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:55Z" - latency: 2.11431ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:20:55Z" - latency: 976.773µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:55Z" - latency: 1.943883ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:19:55Z" - latency: 944.726µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:55Z" - latency: 1.925369ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:18:55Z" - latency: 1.168929ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:17:55Z" - latency: 1.867712ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:17:55Z" kind: List metadata: resourceVersion: ""