apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:15:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-19-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-19.ec2.internal uid: 82c74b58-72f0-4a1a-b543-b75872a76352 resourceVersion: "43849" uid: 06baddc2-0db0-4991-80d9-c1a8e04e0d22 spec: sourcePod: network-check-source-7f44b6dd87-hr9j4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-27T20:22:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.494517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:43:08Z" - latency: 1.084845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:08Z" - latency: 1.323309ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:08Z" - latency: 932.336µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:40:08Z" - latency: 920.032µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:39:08Z" - latency: 717.826µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:08Z" - latency: 1.020763ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:08Z" - latency: 1.056176ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:08Z" - latency: 850.159µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:08Z" - latency: 757.575µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:15:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-19-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-19.ec2.internal uid: 82c74b58-72f0-4a1a-b543-b75872a76352 resourceVersion: "45804" uid: 4f343651-d327-4bee-a058-5ffc145a66ce spec: sourcePod: network-check-source-7f44b6dd87-hr9j4 targetEndpoint: af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T20:21:08Z" message: 'load-balancer-api-external: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.283223ms message: 'load-balancer-api-external: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:45:08Z" - latency: 7.271651ms message: 'load-balancer-api-external: resolved host name af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:45:08Z" - latency: 3.782708ms message: 'load-balancer-api-external: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:44:08Z" - latency: 8.091071ms message: 'load-balancer-api-external: resolved host name af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:44:08Z" - latency: 3.254421ms message: 'load-balancer-api-external: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:43:08Z" - latency: 8.057802ms message: 'load-balancer-api-external: resolved host name af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:43:08Z" - latency: 3.458667ms message: 'load-balancer-api-external: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:08Z" - latency: 7.931258ms message: 'load-balancer-api-external: resolved host name af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:42:08Z" - latency: 4.397087ms message: 'load-balancer-api-external: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:08Z" - latency: 8.325651ms message: 'load-balancer-api-external: resolved host name af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:41:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:15:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-19-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-19.ec2.internal uid: 82c74b58-72f0-4a1a-b543-b75872a76352 resourceVersion: "45803" uid: b58c9f78-dda2-490e-a6ff-e5fe858305bc spec: sourcePod: network-check-source-7f44b6dd87-hr9j4 targetEndpoint: af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T20:21:08Z" message: 'load-balancer-api-internal: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.323441ms message: 'load-balancer-api-internal: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:45:08Z" - latency: 7.224447ms message: 'load-balancer-api-internal: resolved host name af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:45:08Z" - latency: 4.019507ms message: 'load-balancer-api-internal: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:44:08Z" - latency: 8.132523ms message: 'load-balancer-api-internal: resolved host name af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:44:08Z" - latency: 3.299902ms message: 'load-balancer-api-internal: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:43:08Z" - latency: 7.86745ms message: 'load-balancer-api-internal: resolved host name af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:43:08Z" - latency: 8.217607ms message: 'load-balancer-api-internal: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:08Z" - latency: 7.972103ms message: 'load-balancer-api-internal: resolved host name af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:42:08Z" - latency: 4.402006ms message: 'load-balancer-api-internal: tcp connection to af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:08Z" - latency: 8.27426ms message: 'load-balancer-api-internal: resolved host name af0ca249c46264d5eb4ce2293b93bc62-7535011dc1569f33.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:41:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:15:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-19-to-network-check-target-ip-10-0-129-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-19.ec2.internal uid: 82c74b58-72f0-4a1a-b543-b75872a76352 resourceVersion: "43847" uid: 006a13dd-f237-47aa-b1f6-280385fb2944 spec: sourcePod: network-check-source-7f44b6dd87-hr9j4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T20:22:08Z" message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 700.505µs message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:43:08Z" - latency: 791.232µs message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:08Z" - latency: 1.009544ms message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:08Z" - latency: 845.244µs message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:40:08Z" - latency: 820.497µs message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:39:08Z" - latency: 1.24598ms message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:08Z" - latency: 806.287µs message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:08Z" - latency: 772.499µs message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:08Z" - latency: 744.239µs message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:08Z" - latency: 863.985µs message: 'network-check-target-ip-10-0-129-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:15:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-19-to-network-check-target-ip-10-0-132-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-19.ec2.internal uid: 82c74b58-72f0-4a1a-b543-b75872a76352 resourceVersion: "43848" uid: 877c414b-47f2-4ed4-841a-3e854a3dad83 spec: sourcePod: network-check-source-7f44b6dd87-hr9j4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-27T20:22:08Z" message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.457698ms message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:43:08Z" - latency: 2.006863ms message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:08Z" - latency: 1.68489ms message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:08Z" - latency: 1.999581ms message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:40:08Z" - latency: 1.699905ms message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:39:08Z" - latency: 1.961537ms message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:08Z" - latency: 1.809342ms message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:08Z" - latency: 2.022553ms message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:08Z" - latency: 1.615803ms message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:08Z" - latency: 1.741781ms message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:15:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-19-to-network-check-target-ip-10-0-135-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-19.ec2.internal uid: 82c74b58-72f0-4a1a-b543-b75872a76352 resourceVersion: "43850" uid: 2331e5f8-2495-4fd7-b592-e621a2bd94ed spec: sourcePod: network-check-source-7f44b6dd87-hr9j4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T20:22:08Z" message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.550329ms message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:43:08Z" - latency: 1.734729ms message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:08Z" - latency: 1.69213ms message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:08Z" - latency: 1.687681ms message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:40:08Z" - latency: 1.613647ms message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:39:08Z" - latency: 1.708936ms message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:08Z" - latency: 1.409977ms message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:08Z" - latency: 1.718302ms message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:08Z" - latency: 1.656907ms message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:08Z" - latency: 1.576967ms message: 'network-check-target-ip-10-0-135-52: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:15:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-19-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-19.ec2.internal uid: 82c74b58-72f0-4a1a-b543-b75872a76352 resourceVersion: "45802" uid: d101dc4d-b095-4574-9789-d5410b4a25ae spec: sourcePod: network-check-source-7f44b6dd87-hr9j4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-27T20:21:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 904.038µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:45:08Z" - latency: 1.561614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T20:45:08Z" - latency: 961.884µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:44:08Z" - latency: 1.872393ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T20:44:08Z" - latency: 1.022487ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:43:08Z" - latency: 1.591214ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T20:43:08Z" - latency: 1.017458ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:08Z" - latency: 1.686236ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T20:42:08Z" - latency: 997.203µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:08Z" - latency: 2.02644ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T20:41:08Z" kind: List metadata: resourceVersion: ""