apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-201-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-201.ec2.internal uid: 531a2879-9bfd-403b-b030-3379cfc0aa2b resourceVersion: "32772" uid: e53e5ee2-cf38-45dc-be89-16340440cfb0 spec: sourcePod: network-check-source-7d88cb55d8-gdgs7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T21:14:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.260024ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:57Z" - latency: 1.000017ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:57Z" - latency: 1.054045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:57Z" - latency: 1.00342ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:57Z" - latency: 996.022µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:57Z" - latency: 995.432µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:44:57Z" - latency: 1.320277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:43:57Z" - latency: 1.314231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:42:57Z" - latency: 1.246404ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:41:57Z" - latency: 1.235869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:40:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-201-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-201.ec2.internal uid: 531a2879-9bfd-403b-b030-3379cfc0aa2b resourceVersion: "32774" uid: 23d243c2-a188-4d0e-90f3-ce07fc0458fd spec: sourcePod: network-check-source-7d88cb55d8-gdgs7 targetEndpoint: aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T21:13:57Z" message: 'load-balancer-api-external: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.342511ms message: 'load-balancer-api-external: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:57Z" - latency: 9.062459ms message: 'load-balancer-api-external: resolved host name aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:49:57Z" - latency: 4.454913ms message: 'load-balancer-api-external: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:57Z" - latency: 8.355029ms message: 'load-balancer-api-external: resolved host name aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:48:57Z" - latency: 5.148408ms message: 'load-balancer-api-external: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:57Z" - latency: 8.662269ms message: 'load-balancer-api-external: resolved host name aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:47:57Z" - latency: 3.936792ms message: 'load-balancer-api-external: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:57Z" - latency: 10.051685ms message: 'load-balancer-api-external: resolved host name aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:46:57Z" - latency: 4.439806ms message: 'load-balancer-api-external: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:57Z" - latency: 8.273116ms message: 'load-balancer-api-external: resolved host name aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:45:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-201-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-201.ec2.internal uid: 531a2879-9bfd-403b-b030-3379cfc0aa2b resourceVersion: "32773" uid: 5cd470a6-82f0-40fd-98f8-cd2f704940b0 spec: sourcePod: network-check-source-7d88cb55d8-gdgs7 targetEndpoint: aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T21:13:57Z" message: 'load-balancer-api-internal: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.043168ms message: 'load-balancer-api-internal: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:57Z" - latency: 9.1243ms message: 'load-balancer-api-internal: resolved host name aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:49:57Z" - latency: 4.422476ms message: 'load-balancer-api-internal: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:57Z" - latency: 8.384188ms message: 'load-balancer-api-internal: resolved host name aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:48:57Z" - latency: 4.28089ms message: 'load-balancer-api-internal: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:57Z" - latency: 8.705109ms message: 'load-balancer-api-internal: resolved host name aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:47:57Z" - latency: 4.366262ms message: 'load-balancer-api-internal: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:57Z" - latency: 10.118852ms message: 'load-balancer-api-internal: resolved host name aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:46:57Z" - latency: 4.509961ms message: 'load-balancer-api-internal: tcp connection to aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:57Z" - latency: 8.295902ms message: 'load-balancer-api-internal: resolved host name aeea0322e359546f1ae4a031bec6e8a3-66c4ddbda9687d11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:45:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-201-to-network-check-target-ip-10-0-128-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-201.ec2.internal uid: 531a2879-9bfd-403b-b030-3379cfc0aa2b resourceVersion: "32767" uid: 08a2e0c1-6e32-48f6-bac8-0c96086de401 spec: sourcePod: network-check-source-7d88cb55d8-gdgs7 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:14:57Z" message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.256088ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:57Z" - latency: 794.927µs message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:57Z" - latency: 954.75µs message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:57Z" - latency: 1.053533ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:57Z" - latency: 939.775µs message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:57Z" - latency: 991.842µs message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:44:57Z" - latency: 843.819µs message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:43:57Z" - latency: 1.020724ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:42:57Z" - latency: 950.61µs message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:41:57Z" - latency: 1.642555ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:40:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-201-to-network-check-target-ip-10-0-135-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-201.ec2.internal uid: 531a2879-9bfd-403b-b030-3379cfc0aa2b resourceVersion: "32770" uid: 3f377292-6eef-41f4-9548-d95d9842abbf spec: sourcePod: network-check-source-7d88cb55d8-gdgs7 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:14:57Z" message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.525663ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:57Z" - latency: 2.090221ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:57Z" - latency: 2.143649ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:57Z" - latency: 2.121267ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:57Z" - latency: 2.241414ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:57Z" - latency: 2.660269ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:44:57Z" - latency: 1.999261ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:43:57Z" - latency: 2.114497ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:42:57Z" - latency: 2.033767ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:41:57Z" - latency: 2.255326ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:40:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-201-to-network-check-target-ip-10-0-138-50 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-201.ec2.internal uid: 531a2879-9bfd-403b-b030-3379cfc0aa2b resourceVersion: "32768" uid: cd32b970-4be7-4fbf-a802-cc2ef467d10b spec: sourcePod: network-check-source-7d88cb55d8-gdgs7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:14:57Z" message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.565179ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:57Z" - latency: 2.114328ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:57Z" - latency: 5.88686ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:57Z" - latency: 2.513905ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:57Z" - latency: 2.310492ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:57Z" - latency: 2.632529ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:44:57Z" - latency: 2.434648ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:43:57Z" - latency: 2.895572ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:42:57Z" - latency: 2.392392ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:41:57Z" - latency: 2.276197ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:40:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-201-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-201.ec2.internal uid: 531a2879-9bfd-403b-b030-3379cfc0aa2b resourceVersion: "32771" uid: 6485d5be-6c79-42f1-8d78-da9f88078524 spec: sourcePod: network-check-source-7d88cb55d8-gdgs7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T21:13:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.018861ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:49:57Z" - latency: 2.086299ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:49:57Z" - latency: 739.598µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:48:57Z" - latency: 2.043975ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:48:57Z" - latency: 1.041337ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:47:57Z" - latency: 1.902177ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:47:57Z" - latency: 936.653µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:46:57Z" - latency: 1.803779ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:46:57Z" - latency: 1.042598ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:45:57Z" - latency: 1.97309ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:45:57Z" kind: List metadata: resourceVersion: ""