apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:07:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-197-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-197.ec2.internal uid: a52fb527-a21f-432b-8846-282ae6cee558 resourceVersion: "55054" uid: ea28a43c-cd30-453a-9368-26d2f46b526c spec: sourcePod: network-check-source-989f8b8dc-r622v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T19:14:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 988.153µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:59Z" - latency: 946.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:59Z" - latency: 1.412046ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:59Z" - latency: 903.876µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:59Z" - latency: 1.048843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:59Z" - latency: 1.257632ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:59Z" - latency: 981.687µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:59Z" - latency: 1.007687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:59Z" - latency: 936.049µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:34:59Z" - latency: 859.096µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:33:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:07:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-197-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-197.ec2.internal uid: a52fb527-a21f-432b-8846-282ae6cee558 resourceVersion: "56046" uid: 5dcf1308-28be-4e0d-9a7e-68052e928956 spec: sourcePod: network-check-source-989f8b8dc-r622v targetEndpoint: ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T19:13:59Z" message: 'load-balancer-api-external: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.721942ms message: 'load-balancer-api-external: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:59Z" - latency: 9.640854ms message: 'load-balancer-api-external: resolved host name ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:43:59Z" - latency: 5.073599ms message: 'load-balancer-api-external: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:59Z" - latency: 8.389179ms message: 'load-balancer-api-external: resolved host name ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:42:59Z" - latency: 5.110944ms message: 'load-balancer-api-external: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:59Z" - latency: 8.836596ms message: 'load-balancer-api-external: resolved host name ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:41:59Z" - latency: 5.682779ms message: 'load-balancer-api-external: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:59Z" - latency: 8.924678ms message: 'load-balancer-api-external: resolved host name ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:40:59Z" - latency: 3.073303ms message: 'load-balancer-api-external: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:59Z" - latency: 8.239518ms message: 'load-balancer-api-external: resolved host name ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:39:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:07:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-197-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-197.ec2.internal uid: a52fb527-a21f-432b-8846-282ae6cee558 resourceVersion: "56047" uid: bc17c291-dee3-4a93-80fa-99ebbf51a8f7 spec: sourcePod: network-check-source-989f8b8dc-r622v targetEndpoint: ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T19:13:59Z" message: 'load-balancer-api-internal: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.732786ms message: 'load-balancer-api-internal: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:59Z" - latency: 9.791411ms message: 'load-balancer-api-internal: resolved host name ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:43:59Z" - latency: 3.702405ms message: 'load-balancer-api-internal: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:59Z" - latency: 8.427515ms message: 'load-balancer-api-internal: resolved host name ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:42:59Z" - latency: 5.083428ms message: 'load-balancer-api-internal: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:59Z" - latency: 8.875357ms message: 'load-balancer-api-internal: resolved host name ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:41:59Z" - latency: 5.454548ms message: 'load-balancer-api-internal: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:59Z" - latency: 8.990734ms message: 'load-balancer-api-internal: resolved host name ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:40:59Z" - latency: 3.073284ms message: 'load-balancer-api-internal: tcp connection to ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:59Z" - latency: 8.3445ms message: 'load-balancer-api-internal: resolved host name ad2832fa134de4d16bd7c97da82f7cb1-1210d9d8dd651f0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:39:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:07:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-197-to-network-check-target-ip-10-0-130-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-197.ec2.internal uid: a52fb527-a21f-432b-8846-282ae6cee558 resourceVersion: "55051" uid: 9f508770-57eb-4f59-905b-1b51160a3820 spec: sourcePod: network-check-source-989f8b8dc-r622v targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:14:59Z" message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 953.71µs message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:59Z" - latency: 886.855µs message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:59Z" - latency: 846.071µs message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:59Z" - latency: 869.259µs message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:59Z" - latency: 832.004µs message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:59Z" - latency: 1.292434ms message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:59Z" - latency: 846.393µs message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:59Z" - latency: 1.18117ms message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:59Z" - latency: 1.341301ms message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:34:59Z" - latency: 826.461µs message: 'network-check-target-ip-10-0-130-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:33:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:07:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-197-to-network-check-target-ip-10-0-134-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-197.ec2.internal uid: a52fb527-a21f-432b-8846-282ae6cee558 resourceVersion: "55053" uid: 7244b6ef-4fd3-4570-8706-311e435f83e2 spec: sourcePod: network-check-source-989f8b8dc-r622v targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:14:59Z" message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.221298ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:59Z" - latency: 2.22073ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:59Z" - latency: 2.545119ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:59Z" - latency: 2.497427ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:59Z" - latency: 2.549009ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:59Z" - latency: 2.481152ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:59Z" - latency: 2.362554ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:59Z" - latency: 2.302178ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:59Z" - latency: 2.475538ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:34:59Z" - latency: 2.377956ms message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:33:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:07:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-197-to-network-check-target-ip-10-0-141-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-197.ec2.internal uid: a52fb527-a21f-432b-8846-282ae6cee558 resourceVersion: "55052" uid: a598a840-ec16-4ee1-aa6f-e7807ee361dc spec: sourcePod: network-check-source-989f8b8dc-r622v targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:14:59Z" message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.283017ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:59Z" - latency: 1.970742ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:59Z" - latency: 2.210596ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:59Z" - latency: 2.244497ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:59Z" - latency: 2.135739ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:59Z" - latency: 2.206187ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:59Z" - latency: 2.305547ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:59Z" - latency: 1.739138ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:59Z" - latency: 2.081668ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:34:59Z" - latency: 2.457652ms message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:33:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:07:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-197-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-197.ec2.internal uid: a52fb527-a21f-432b-8846-282ae6cee558 resourceVersion: "56045" uid: 2ca3ab9b-b8bc-41d5-a949-815ea5435c5c spec: sourcePod: network-check-source-989f8b8dc-r622v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T19:13:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 686.23µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:59Z" - latency: 3.142309ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:43:59Z" - latency: 1.214745ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:59Z" - latency: 1.802176ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:42:59Z" - latency: 973.825µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:59Z" - latency: 1.798723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:41:59Z" - latency: 769.081µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:59Z" - latency: 2.109591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:40:59Z" - latency: 844.096µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:59Z" - latency: 1.817566ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:39:59Z" kind: List metadata: resourceVersion: ""