apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:40:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-241-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-241.ec2.internal uid: 787ebfbf-27fe-4305-b897-4210b1d6cbcd resourceVersion: "64934" uid: a888a5ed-825c-4a4a-b44e-e5742c628352 spec: sourcePod: network-check-source-65bdbbff45-dl4sm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-31T21:47:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.001634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:29:19Z" - latency: 1.118468ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:28:19Z" - latency: 1.079616ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:27:19Z" - latency: 1.063448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:26:19Z" - latency: 1.029254ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:25:19Z" - latency: 1.063704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:24:19Z" - latency: 937.921µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:23:19Z" - latency: 930.648µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:22:19Z" - latency: 1.608353ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:21:19Z" - latency: 1.221336ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:20:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:40:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-241-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-241.ec2.internal uid: 787ebfbf-27fe-4305-b897-4210b1d6cbcd resourceVersion: "69515" uid: aa3aeb8a-07b4-430e-abec-1504304b561a spec: sourcePod: network-check-source-65bdbbff45-dl4sm targetEndpoint: a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T21:46:19Z" message: 'load-balancer-api-external: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.179659ms message: 'load-balancer-api-external: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:34:19Z" - latency: 7.808751ms message: 'load-balancer-api-external: resolved host name a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:34:19Z" - latency: 5.4294ms message: 'load-balancer-api-external: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:33:19Z" - latency: 8.385825ms message: 'load-balancer-api-external: resolved host name a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:33:19Z" - latency: 4.463464ms message: 'load-balancer-api-external: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:32:19Z" - latency: 6.903299ms message: 'load-balancer-api-external: resolved host name a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:32:19Z" - latency: 4.774925ms message: 'load-balancer-api-external: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:31:19Z" - latency: 7.618271ms message: 'load-balancer-api-external: resolved host name a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:31:19Z" - latency: 4.043222ms message: 'load-balancer-api-external: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:30:19Z" - latency: 6.870222ms message: 'load-balancer-api-external: resolved host name a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:30:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:40:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-241-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-241.ec2.internal uid: 787ebfbf-27fe-4305-b897-4210b1d6cbcd resourceVersion: "69516" uid: f8cfb894-f330-457c-8ac5-5c2f48ce04e4 spec: sourcePod: network-check-source-65bdbbff45-dl4sm targetEndpoint: a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T21:46:19Z" message: 'load-balancer-api-internal: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.123872ms message: 'load-balancer-api-internal: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:34:19Z" - latency: 7.859443ms message: 'load-balancer-api-internal: resolved host name a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:34:19Z" - latency: 5.480321ms message: 'load-balancer-api-internal: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:33:19Z" - latency: 8.443314ms message: 'load-balancer-api-internal: resolved host name a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:33:19Z" - latency: 4.6798ms message: 'load-balancer-api-internal: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:32:19Z" - latency: 6.974048ms message: 'load-balancer-api-internal: resolved host name a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:32:19Z" - latency: 4.750585ms message: 'load-balancer-api-internal: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:31:19Z" - latency: 7.511659ms message: 'load-balancer-api-internal: resolved host name a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:31:19Z" - latency: 4.043954ms message: 'load-balancer-api-internal: tcp connection to a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:30:19Z" - latency: 6.942182ms message: 'load-balancer-api-internal: resolved host name a86eae5e8bf054bfd99f293c64154f62-fd77ad87b1368d17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:30:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:40:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-241-to-network-check-target-ip-10-0-134-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-241.ec2.internal uid: 787ebfbf-27fe-4305-b897-4210b1d6cbcd resourceVersion: "64933" uid: 81d0ad8b-dfdc-4cb9-bf50-76cd551a4a88 spec: sourcePod: network-check-source-65bdbbff45-dl4sm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-31T21:47:19Z" message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.222115ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:29:19Z" - latency: 1.887068ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:28:19Z" - latency: 2.64585ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:27:19Z" - latency: 2.595274ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:26:19Z" - latency: 2.483915ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:25:19Z" - latency: 2.827457ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:24:19Z" - latency: 2.329551ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:23:19Z" - latency: 2.530161ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:22:19Z" - latency: 3.048149ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:21:19Z" - latency: 2.150788ms message: 'network-check-target-ip-10-0-134-210: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:20:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:40:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-241-to-network-check-target-ip-10-0-135-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-241.ec2.internal uid: 787ebfbf-27fe-4305-b897-4210b1d6cbcd resourceVersion: "64931" uid: 4a00ef95-0782-49c1-926e-55f65782fb1e spec: sourcePod: network-check-source-65bdbbff45-dl4sm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-31T21:47:19Z" message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.148737ms message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:29:19Z" - latency: 1.146457ms message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:28:19Z" - latency: 1.105154ms message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:27:19Z" - latency: 1.192986ms message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:26:19Z" - latency: 1.061387ms message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:25:19Z" - latency: 920.005µs message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:24:19Z" - latency: 1.013009ms message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:23:19Z" - latency: 1.599044ms message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:22:19Z" - latency: 1.423424ms message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:21:19Z" - latency: 1.146403ms message: 'network-check-target-ip-10-0-135-241: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:20:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:40:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-241-to-network-check-target-ip-10-0-142-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-241.ec2.internal uid: 787ebfbf-27fe-4305-b897-4210b1d6cbcd resourceVersion: "64932" uid: 204128f4-c0fa-4ec3-8739-aa53c6251a3a spec: sourcePod: network-check-source-65bdbbff45-dl4sm targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-31T21:47:19Z" message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.300802ms message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:29:19Z" - latency: 2.033756ms message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:28:19Z" - latency: 2.406191ms message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:27:19Z" - latency: 2.399376ms message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:26:19Z" - latency: 2.338125ms message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:25:19Z" - latency: 2.428201ms message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:24:19Z" - latency: 2.337573ms message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:23:19Z" - latency: 2.501032ms message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:22:19Z" - latency: 2.332051ms message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:21:19Z" - latency: 2.283232ms message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:20:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:40:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-241-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-241.ec2.internal uid: 787ebfbf-27fe-4305-b897-4210b1d6cbcd resourceVersion: "69514" uid: d3d89d0e-2292-4ab7-8449-8b28f9201dd0 spec: sourcePod: network-check-source-65bdbbff45-dl4sm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-31T21:46:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.022345ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:34:19Z" - latency: 1.963011ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T22:34:19Z" - latency: 954.311µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:33:19Z" - latency: 2.565634ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T22:33:19Z" - latency: 1.374433ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:32:19Z" - latency: 2.26429ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T22:32:19Z" - latency: 1.663563ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:31:19Z" - latency: 1.993004ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T22:31:19Z" - latency: 991.81µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:30:19Z" - latency: 1.944299ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T22:30:19Z" kind: List metadata: resourceVersion: ""