apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:35:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-113-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-113.ec2.internal uid: dad64405-93a5-418f-90d7-d63a76a5326d resourceVersion: "60696" uid: fe290ccd-2ab9-43f0-8c8c-b0b0fbe76124 spec: sourcePod: network-check-source-869dcfcdcd-tjdkg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T17:42:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.331297ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:17:03Z" - latency: 864.016µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:16:03Z" - latency: 998.993µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:15:03Z" - latency: 882.999µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:14:03Z" - latency: 1.102292ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:13:03Z" - latency: 983.795µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:12:03Z" - latency: 886.699µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:11:03Z" - latency: 1.117303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:10:03Z" - latency: 1.148768ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:09:03Z" - latency: 981.35µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:08:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:35:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-113-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-113.ec2.internal uid: dad64405-93a5-418f-90d7-d63a76a5326d resourceVersion: "60697" uid: 3c6d3f94-d82d-4e65-b03a-369819e158d1 spec: sourcePod: network-check-source-869dcfcdcd-tjdkg targetEndpoint: a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T17:41:03Z" message: 'load-balancer-api-external: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.580414ms message: 'load-balancer-api-external: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:17:03Z" - latency: 8.426458ms message: 'load-balancer-api-external: resolved host name a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:17:03Z" - latency: 4.149731ms message: 'load-balancer-api-external: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:16:03Z" - latency: 8.391645ms message: 'load-balancer-api-external: resolved host name a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:16:03Z" - latency: 5.440604ms message: 'load-balancer-api-external: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:15:03Z" - latency: 9.147912ms message: 'load-balancer-api-external: resolved host name a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:15:03Z" - latency: 6.15253ms message: 'load-balancer-api-external: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:14:03Z" - latency: 8.562618ms message: 'load-balancer-api-external: resolved host name a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:14:03Z" - latency: 6.804529ms message: 'load-balancer-api-external: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:13:03Z" - latency: 7.676065ms message: 'load-balancer-api-external: resolved host name a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:13:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:35:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-113-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-113.ec2.internal uid: dad64405-93a5-418f-90d7-d63a76a5326d resourceVersion: "60698" uid: 2a68ee32-97a6-4145-8488-18853970050d spec: sourcePod: network-check-source-869dcfcdcd-tjdkg targetEndpoint: a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T17:41:03Z" message: 'load-balancer-api-internal: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.605497ms message: 'load-balancer-api-internal: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:17:03Z" - latency: 8.386086ms message: 'load-balancer-api-internal: resolved host name a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:17:03Z" - latency: 4.134966ms message: 'load-balancer-api-internal: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:16:03Z" - latency: 8.459377ms message: 'load-balancer-api-internal: resolved host name a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:16:03Z" - latency: 5.958165ms message: 'load-balancer-api-internal: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:15:03Z" - latency: 9.182638ms message: 'load-balancer-api-internal: resolved host name a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:15:03Z" - latency: 5.202638ms message: 'load-balancer-api-internal: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:14:03Z" - latency: 8.664505ms message: 'load-balancer-api-internal: resolved host name a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:14:03Z" - latency: 6.749705ms message: 'load-balancer-api-internal: tcp connection to a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:13:03Z" - latency: 7.568026ms message: 'load-balancer-api-internal: resolved host name a303e76cd4b7c412cb19f1824a2f2f6f-655eb6acb5b3b07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:13:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:35:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-113-to-network-check-target-ip-10-0-129-209 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-113.ec2.internal uid: dad64405-93a5-418f-90d7-d63a76a5326d resourceVersion: "60693" uid: e45321c1-d233-4b9b-8265-afb1d46145b1 spec: sourcePod: network-check-source-869dcfcdcd-tjdkg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T17:42:03Z" message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.654534ms message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:17:03Z" - latency: 2.287475ms message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:16:03Z" - latency: 2.259572ms message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:15:03Z" - latency: 1.984996ms message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:14:03Z" - latency: 2.568997ms message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:13:03Z" - latency: 2.329603ms message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:12:03Z" - latency: 2.488223ms message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:11:03Z" - latency: 2.724266ms message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:10:03Z" - latency: 2.330303ms message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:09:03Z" - latency: 1.974858ms message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:08:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:35:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-113-to-network-check-target-ip-10-0-135-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-113.ec2.internal uid: dad64405-93a5-418f-90d7-d63a76a5326d resourceVersion: "60694" uid: 7b5567de-f986-4491-9a49-098ce3613e25 spec: sourcePod: network-check-source-869dcfcdcd-tjdkg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T17:42:03Z" message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.785558ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:17:03Z" - latency: 2.033772ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:16:03Z" - latency: 2.214058ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:15:03Z" - latency: 2.595015ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:14:03Z" - latency: 2.707609ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:13:03Z" - latency: 2.733951ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:12:03Z" - latency: 2.581866ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:11:03Z" - latency: 3.052764ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:10:03Z" - latency: 2.545865ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:09:03Z" - latency: 2.505844ms message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:08:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:35:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-113-to-network-check-target-ip-10-0-138-113 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-113.ec2.internal uid: dad64405-93a5-418f-90d7-d63a76a5326d resourceVersion: "60692" uid: f6981754-96f4-496f-8a06-57980f0a0d4f spec: sourcePod: network-check-source-869dcfcdcd-tjdkg targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T17:42:03Z" message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.453203ms message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:17:03Z" - latency: 1.128111ms message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:16:03Z" - latency: 1.582219ms message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:15:03Z" - latency: 1.179364ms message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:14:03Z" - latency: 1.318615ms message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:13:03Z" - latency: 1.198904ms message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:12:03Z" - latency: 892.35µs message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:11:03Z" - latency: 1.406222ms message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:10:03Z" - latency: 927.822µs message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:09:03Z" - latency: 916.678µs message: 'network-check-target-ip-10-0-138-113: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:08:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:35:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-113-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-113.ec2.internal uid: dad64405-93a5-418f-90d7-d63a76a5326d resourceVersion: "60695" uid: 0bfc1787-c661-411f-800c-de5c16f5b6cc spec: sourcePod: network-check-source-869dcfcdcd-tjdkg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T17:41:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.059407ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:17:03Z" - latency: 2.193341ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:17:03Z" - latency: 1.356755ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:16:03Z" - latency: 1.781911ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:16:03Z" - latency: 1.046695ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:15:03Z" - latency: 2.202776ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:15:03Z" - latency: 914.984µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:14:03Z" - latency: 1.77085ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:14:03Z" - latency: 1.156985ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:13:03Z" - latency: 1.755267ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:13:03Z" kind: List metadata: resourceVersion: ""