apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T16:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-95-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-95.ec2.internal uid: e9fb88ed-93da-40f8-b93e-05da69b81da5 resourceVersion: "53789" uid: 04b4c40a-a725-4eee-9637-54bf0169ee1c spec: sourcePod: network-check-source-869dcfcdcd-xt95b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T16:39:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.436495ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:07:59Z" - latency: 812.51µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:06:59Z" - latency: 1.32579ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:05:59Z" - latency: 967.063µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:04:59Z" - latency: 921.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:03:59Z" - latency: 1.204359ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:02:59Z" - latency: 1.16764ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:01:59Z" - latency: 1.280315ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:00:59Z" - latency: 1.295178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T16:59:59Z" - latency: 869.481µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T16:58:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T16:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-95-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-95.ec2.internal uid: e9fb88ed-93da-40f8-b93e-05da69b81da5 resourceVersion: "54678" uid: dd44735b-e353-46b2-b08c-8abd6f0d0d53 spec: sourcePod: network-check-source-869dcfcdcd-xt95b targetEndpoint: ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T16:38:59Z" message: 'load-balancer-api-external: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.210572ms message: 'load-balancer-api-external: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:08:59Z" - latency: 8.733763ms message: 'load-balancer-api-external: resolved host name ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:08:59Z" - latency: 8.590003ms message: 'load-balancer-api-external: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:07:59Z" - latency: 9.168003ms message: 'load-balancer-api-external: resolved host name ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:07:59Z" - latency: 5.612415ms message: 'load-balancer-api-external: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:06:59Z" - latency: 8.205472ms message: 'load-balancer-api-external: resolved host name ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:06:59Z" - latency: 4.896314ms message: 'load-balancer-api-external: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:05:59Z" - latency: 8.782713ms message: 'load-balancer-api-external: resolved host name ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:05:59Z" - latency: 5.184172ms message: 'load-balancer-api-external: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:04:59Z" - latency: 8.709922ms message: 'load-balancer-api-external: resolved host name ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:04:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T16:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-95-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-95.ec2.internal uid: e9fb88ed-93da-40f8-b93e-05da69b81da5 resourceVersion: "54679" uid: dbcfb2e0-50a5-4ad0-b91f-196a5ad033d2 spec: sourcePod: network-check-source-869dcfcdcd-xt95b targetEndpoint: ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T16:38:59Z" message: 'load-balancer-api-internal: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.218635ms message: 'load-balancer-api-internal: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:08:59Z" - latency: 8.696245ms message: 'load-balancer-api-internal: resolved host name ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:08:59Z" - latency: 6.081465ms message: 'load-balancer-api-internal: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:07:59Z" - latency: 9.115522ms message: 'load-balancer-api-internal: resolved host name ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:07:59Z" - latency: 5.489337ms message: 'load-balancer-api-internal: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:06:59Z" - latency: 8.181289ms message: 'load-balancer-api-internal: resolved host name ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:06:59Z" - latency: 4.914321ms message: 'load-balancer-api-internal: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:05:59Z" - latency: 8.741492ms message: 'load-balancer-api-internal: resolved host name ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:05:59Z" - latency: 5.205568ms message: 'load-balancer-api-internal: tcp connection to ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:04:59Z" - latency: 8.633006ms message: 'load-balancer-api-internal: resolved host name ae64c828da48240a095ffeb4b632e660-923f6a7410821d1a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:04:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T16:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-95-to-network-check-target-ip-10-0-135-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-95.ec2.internal uid: e9fb88ed-93da-40f8-b93e-05da69b81da5 resourceVersion: "53786" uid: a977249b-e049-4ac1-9f54-62fe755c63db spec: sourcePod: network-check-source-869dcfcdcd-xt95b targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T16:39:59Z" message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.303258ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:07:59Z" - latency: 2.067832ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:06:59Z" - latency: 2.155967ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:05:59Z" - latency: 2.105732ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:04:59Z" - latency: 2.33145ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:03:59Z" - latency: 2.28308ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:02:59Z" - latency: 2.247977ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:01:59Z" - latency: 2.20136ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:00:59Z" - latency: 2.1836ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T16:59:59Z" - latency: 2.372539ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T16:58:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T16:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-95-to-network-check-target-ip-10-0-138-95 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-95.ec2.internal uid: e9fb88ed-93da-40f8-b93e-05da69b81da5 resourceVersion: "53787" uid: ce84f8e6-842e-4b1a-ad04-df6403a69436 spec: sourcePod: network-check-source-869dcfcdcd-xt95b targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T16:39:59Z" message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.368195ms message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:07:59Z" - latency: 786.595µs message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:06:59Z" - latency: 906.737µs message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:05:59Z" - latency: 819.266µs message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:04:59Z" - latency: 905.835µs message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:03:59Z" - latency: 1.731985ms message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:02:59Z" - latency: 871.102µs message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:01:59Z" - latency: 1.157898ms message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:00:59Z" - latency: 1.473285ms message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T16:59:59Z" - latency: 979.563µs message: 'network-check-target-ip-10-0-138-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T16:58:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T16:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-95-to-network-check-target-ip-10-0-141-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-95.ec2.internal uid: e9fb88ed-93da-40f8-b93e-05da69b81da5 resourceVersion: "53788" uid: 931f00ae-a608-49d0-a519-22448a307c5e spec: sourcePod: network-check-source-869dcfcdcd-xt95b targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T16:39:59Z" message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.046993ms message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:07:59Z" - latency: 1.769442ms message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:06:59Z" - latency: 2.033562ms message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:05:59Z" - latency: 1.931828ms message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:04:59Z" - latency: 1.734734ms message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:03:59Z" - latency: 2.161149ms message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:02:59Z" - latency: 2.071477ms message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:01:59Z" - latency: 1.909413ms message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:00:59Z" - latency: 1.755754ms message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T16:59:59Z" - latency: 1.91529ms message: 'network-check-target-ip-10-0-141-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T16:58:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T16:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-95-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-95.ec2.internal uid: e9fb88ed-93da-40f8-b93e-05da69b81da5 resourceVersion: "54677" uid: fac0f584-4c8d-46da-9fac-0040403ef1dd spec: sourcePod: network-check-source-869dcfcdcd-xt95b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T16:38:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 896.8µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:08:59Z" - latency: 2.182717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T17:08:59Z" - latency: 1.114604ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:07:59Z" - latency: 2.328503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T17:07:59Z" - latency: 774.452µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:06:59Z" - latency: 1.796706ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T17:06:59Z" - latency: 1.045872ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:05:59Z" - latency: 2.138459ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T17:05:59Z" - latency: 969.03µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:04:59Z" - latency: 1.766933ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T17:04:59Z" kind: List metadata: resourceVersion: ""