apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:09:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 3312f9d4-f0d1-42b7-9f10-1458c9cab835 resourceVersion: "19009" uid: 65dd707c-3bec-4963-834d-2a6276b2d8c6 spec: sourcePod: network-check-source-7b678d77c7-59cwx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T16:16:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 954.018µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:23:04Z" - latency: 965.276µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:22:04Z" - latency: 901.826µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:21:04Z" - latency: 1.048104ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:20:04Z" - latency: 1.022113ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:19:04Z" - latency: 947.566µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:18:04Z" - latency: 1.078251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:17:04Z" - latency: 978.207µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:16:04Z" - latency: 983.129µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:15:04Z" - latency: 1.256423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:14:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:09:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 3312f9d4-f0d1-42b7-9f10-1458c9cab835 resourceVersion: "21092" uid: 53d946f9-71ce-41c2-a391-ca66be3dca68 spec: sourcePod: network-check-source-7b678d77c7-59cwx targetEndpoint: a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:15:04Z" message: 'load-balancer-api-external: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.318339ms message: 'load-balancer-api-external: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:27:04Z" - latency: 6.47443ms message: 'load-balancer-api-external: resolved host name a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:27:04Z" - latency: 4.508598ms message: 'load-balancer-api-external: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:26:04Z" - latency: 7.184499ms message: 'load-balancer-api-external: resolved host name a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:26:04Z" - latency: 4.373263ms message: 'load-balancer-api-external: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:25:04Z" - latency: 7.628725ms message: 'load-balancer-api-external: resolved host name a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:25:04Z" - latency: 5.242548ms message: 'load-balancer-api-external: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:24:04Z" - latency: 7.440026ms message: 'load-balancer-api-external: resolved host name a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:24:04Z" - latency: 6.346652ms message: 'load-balancer-api-external: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:23:04Z" - latency: 6.925945ms message: 'load-balancer-api-external: resolved host name a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:23:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:09:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 3312f9d4-f0d1-42b7-9f10-1458c9cab835 resourceVersion: "21093" uid: 710b4ed2-1fdb-4639-8582-cd62145ce981 spec: sourcePod: network-check-source-7b678d77c7-59cwx targetEndpoint: a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:15:04Z" message: 'load-balancer-api-internal: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.318109ms message: 'load-balancer-api-internal: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:27:04Z" - latency: 6.465064ms message: 'load-balancer-api-internal: resolved host name a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:27:04Z" - latency: 4.638726ms message: 'load-balancer-api-internal: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:26:04Z" - latency: 7.215689ms message: 'load-balancer-api-internal: resolved host name a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:26:04Z" - latency: 4.379494ms message: 'load-balancer-api-internal: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:25:04Z" - latency: 7.671873ms message: 'load-balancer-api-internal: resolved host name a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:25:04Z" - latency: 4.153052ms message: 'load-balancer-api-internal: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:24:04Z" - latency: 7.462304ms message: 'load-balancer-api-internal: resolved host name a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:24:04Z" - latency: 6.325268ms message: 'load-balancer-api-internal: tcp connection to a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:23:04Z" - latency: 6.95347ms message: 'load-balancer-api-internal: resolved host name a59929d8ec9ec4cf8972d8de0a6d71db-3265ab7f513c5055.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:23:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:09:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-network-check-target-ip-10-0-129-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 3312f9d4-f0d1-42b7-9f10-1458c9cab835 resourceVersion: "19006" uid: 48d02d62-1873-4c88-a39a-ba5032de9061 spec: sourcePod: network-check-source-7b678d77c7-59cwx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:16:04Z" message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.220525ms message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:23:04Z" - latency: 2.202916ms message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:22:04Z" - latency: 2.11837ms message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:21:04Z" - latency: 2.170402ms message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:20:04Z" - latency: 2.240433ms message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:19:04Z" - latency: 2.255452ms message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:18:04Z" - latency: 2.052007ms message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:17:04Z" - latency: 2.249864ms message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:16:04Z" - latency: 2.229511ms message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:15:04Z" - latency: 2.333227ms message: 'network-check-target-ip-10-0-129-182: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:14:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:09:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-network-check-target-ip-10-0-135-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 3312f9d4-f0d1-42b7-9f10-1458c9cab835 resourceVersion: "19007" uid: d3043bd2-b756-447c-aa99-9fa433954702 spec: sourcePod: network-check-source-7b678d77c7-59cwx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:16:04Z" message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.197118ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:23:04Z" - latency: 2.227377ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:22:04Z" - latency: 2.128982ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:21:04Z" - latency: 2.09076ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:20:04Z" - latency: 2.071529ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:19:04Z" - latency: 2.299005ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:18:04Z" - latency: 2.102077ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:17:04Z" - latency: 2.333446ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:16:04Z" - latency: 2.756254ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:15:04Z" - latency: 2.374662ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:14:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:09:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-network-check-target-ip-10-0-136-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 3312f9d4-f0d1-42b7-9f10-1458c9cab835 resourceVersion: "19008" uid: 1ed69bbf-7022-4988-b070-329ae3bf0609 spec: sourcePod: network-check-source-7b678d77c7-59cwx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:16:04Z" message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 847.942µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:23:04Z" - latency: 727.078µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:22:04Z" - latency: 877.375µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:21:04Z" - latency: 1.184083ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:20:04Z" - latency: 896.318µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:19:04Z" - latency: 863.626µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:18:04Z" - latency: 1.029182ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:17:04Z" - latency: 839.396µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:16:04Z" - latency: 862.283µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:15:04Z" - latency: 894.336µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:14:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:09:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 3312f9d4-f0d1-42b7-9f10-1458c9cab835 resourceVersion: "21091" uid: c66b0020-fa62-4d4a-9475-1ef686c656c6 spec: sourcePod: network-check-source-7b678d77c7-59cwx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T16:15:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.586µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:27:04Z" - latency: 1.708047ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:27:04Z" - latency: 777.278µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:26:04Z" - latency: 2.089812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:26:04Z" - latency: 768.967µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:25:04Z" - latency: 1.816325ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:25:04Z" - latency: 746.918µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:24:04Z" - latency: 1.701304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:24:04Z" - latency: 896.601µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:23:04Z" - latency: 1.777639ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:23:04Z" kind: List metadata: resourceVersion: ""