apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:56:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-199-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-199.ec2.internal uid: 513327da-c69b-4866-857d-5dcba4978a3d resourceVersion: "61790" uid: aec7f853-aea8-40d0-8c34-7e40832f4492 spec: sourcePod: network-check-source-869dcfcdcd-5c7tv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T05:03:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.304274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:38:33Z" - latency: 944.741µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:37:33Z" - latency: 1.044331ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:36:33Z" - latency: 1.18664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:35:33Z" - latency: 1.184559ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:34:33Z" - latency: 921.604µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:33:33Z" - latency: 1.599868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:32:33Z" - latency: 909.508µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:31:33Z" - latency: 1.73061ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:30:33Z" - latency: 1.19165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:29:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:56:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-199-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-199.ec2.internal uid: 513327da-c69b-4866-857d-5dcba4978a3d resourceVersion: "61791" uid: 76c12036-7049-4a2d-bee8-3629a4fc3df6 spec: sourcePod: network-check-source-869dcfcdcd-5c7tv targetEndpoint: ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T05:02:33Z" message: 'load-balancer-api-external: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.411979ms message: 'load-balancer-api-external: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:38:33Z" - latency: 7.435043ms message: 'load-balancer-api-external: resolved host name ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:38:33Z" - latency: 5.094842ms message: 'load-balancer-api-external: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:37:33Z" - latency: 8.746919ms message: 'load-balancer-api-external: resolved host name ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:37:33Z" - latency: 4.958641ms message: 'load-balancer-api-external: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:36:33Z" - latency: 10.001211ms message: 'load-balancer-api-external: resolved host name ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:36:33Z" - latency: 4.14251ms message: 'load-balancer-api-external: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:35:33Z" - latency: 7.962933ms message: 'load-balancer-api-external: resolved host name ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:35:33Z" - latency: 3.652942ms message: 'load-balancer-api-external: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:34:33Z" - latency: 8.66921ms message: 'load-balancer-api-external: resolved host name ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:34:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:56:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-199-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-199.ec2.internal uid: 513327da-c69b-4866-857d-5dcba4978a3d resourceVersion: "61792" uid: e5cb77b9-b742-4f6c-aa98-f11181da873e spec: sourcePod: network-check-source-869dcfcdcd-5c7tv targetEndpoint: ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T05:02:33Z" message: 'load-balancer-api-internal: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.02437ms message: 'load-balancer-api-internal: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:38:33Z" - latency: 7.471043ms message: 'load-balancer-api-internal: resolved host name ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:38:33Z" - latency: 4.432859ms message: 'load-balancer-api-internal: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:37:33Z" - latency: 8.815259ms message: 'load-balancer-api-internal: resolved host name ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:37:33Z" - latency: 4.955167ms message: 'load-balancer-api-internal: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:36:33Z" - latency: 9.886992ms message: 'load-balancer-api-internal: resolved host name ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:36:33Z" - latency: 4.253229ms message: 'load-balancer-api-internal: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:35:33Z" - latency: 8.007642ms message: 'load-balancer-api-internal: resolved host name ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:35:33Z" - latency: 4.154869ms message: 'load-balancer-api-internal: tcp connection to ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:34:33Z" - latency: 8.557432ms message: 'load-balancer-api-internal: resolved host name ad75916b1d5e64c65bc85d4b265dfe2b-3518dbd60a9fb947.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T05:34:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:56:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-199-to-network-check-target-ip-10-0-135-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-199.ec2.internal uid: 513327da-c69b-4866-857d-5dcba4978a3d resourceVersion: "61787" uid: 5ba7a47a-da9c-4d27-9a10-42ba53dc0d85 spec: sourcePod: network-check-source-869dcfcdcd-5c7tv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T05:03:33Z" message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.084348ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:38:33Z" - latency: 2.128127ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:37:33Z" - latency: 2.351183ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:36:33Z" - latency: 2.29183ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:35:33Z" - latency: 2.27909ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:34:33Z" - latency: 1.882148ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:33:33Z" - latency: 2.309566ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:32:33Z" - latency: 2.01465ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:31:33Z" - latency: 2.156298ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:30:33Z" - latency: 2.066586ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:29:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:56:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-199-to-network-check-target-ip-10-0-138-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-199.ec2.internal uid: 513327da-c69b-4866-857d-5dcba4978a3d resourceVersion: "61786" uid: 1f7a2ca2-98f4-4837-85e5-7b0657e45ae5 spec: sourcePod: network-check-source-869dcfcdcd-5c7tv targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T05:03:33Z" message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.260125ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:38:33Z" - latency: 944.243µs message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:37:33Z" - latency: 884.981µs message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:36:33Z" - latency: 959.998µs message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:35:33Z" - latency: 1.020382ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:34:33Z" - latency: 914.801µs message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:33:33Z" - latency: 1.755941ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:32:33Z" - latency: 1.153872ms message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:31:33Z" - latency: 908.525µs message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:30:33Z" - latency: 832.984µs message: 'network-check-target-ip-10-0-138-199: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:29:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:56:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-199-to-network-check-target-ip-10-0-138-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-199.ec2.internal uid: 513327da-c69b-4866-857d-5dcba4978a3d resourceVersion: "61788" uid: ad224db0-5f95-448c-acc7-7aa77e8deaf4 spec: sourcePod: network-check-source-869dcfcdcd-5c7tv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T05:03:33Z" message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.91296ms message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:38:33Z" - latency: 2.243801ms message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:37:33Z" - latency: 2.205004ms message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:36:33Z" - latency: 1.874474ms message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:35:33Z" - latency: 1.969332ms message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:34:33Z" - latency: 1.833919ms message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:33:33Z" - latency: 2.094451ms message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:32:33Z" - latency: 2.185387ms message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:31:33Z" - latency: 2.201149ms message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:30:33Z" - latency: 2.228367ms message: 'network-check-target-ip-10-0-138-249: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:29:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T04:56:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-199-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-199.ec2.internal uid: 513327da-c69b-4866-857d-5dcba4978a3d resourceVersion: "61789" uid: 5fcfbd71-6e9d-4fb1-8c10-c4c0df309939 spec: sourcePod: network-check-source-869dcfcdcd-5c7tv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T05:02:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 847.974µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:38:33Z" - latency: 1.935556ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T05:38:33Z" - latency: 983.751µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:37:33Z" - latency: 2.096201ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T05:37:33Z" - latency: 889.658µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:36:33Z" - latency: 1.692624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T05:36:33Z" - latency: 1.079115ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:35:33Z" - latency: 1.798807ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T05:35:33Z" - latency: 955.627µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T05:34:33Z" - latency: 1.681692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T05:34:33Z" kind: List metadata: resourceVersion: ""