apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:43:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-241-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-241.ec2.internal uid: 3309a306-1d01-4f9c-bb89-b029d5140f10 resourceVersion: "31578" uid: 87b692d8-d0b9-48d1-be00-ffcb2b9bd76f spec: sourcePod: network-check-source-7b678d77c7-gdtq9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T17:50:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.674311ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:25:51Z" - latency: 1.026659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:24:51Z" - latency: 1.435076ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:23:51Z" - latency: 825.688µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:22:51Z" - latency: 910.159µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:21:51Z" - latency: 835.107µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:20:51Z" - latency: 954.741µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:19:51Z" - latency: 937.638µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:18:51Z" - latency: 993.632µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:17:51Z" - latency: 1.258091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:16:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:43:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-241-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-241.ec2.internal uid: 3309a306-1d01-4f9c-bb89-b029d5140f10 resourceVersion: "31579" uid: 2208f447-7eab-4e91-a004-23dfb38504f3 spec: sourcePod: network-check-source-7b678d77c7-gdtq9 targetEndpoint: a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T17:49:51Z" message: 'load-balancer-api-external: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.794702ms message: 'load-balancer-api-external: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:25:51Z" - latency: 12.165415ms message: 'load-balancer-api-external: resolved host name a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:25:51Z" - latency: 5.261897ms message: 'load-balancer-api-external: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:24:51Z" - latency: 12.455591ms message: 'load-balancer-api-external: resolved host name a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:24:51Z" - latency: 4.857366ms message: 'load-balancer-api-external: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:23:51Z" - latency: 6.936987ms message: 'load-balancer-api-external: resolved host name a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:23:51Z" - latency: 5.517962ms message: 'load-balancer-api-external: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:22:51Z" - latency: 7.647851ms message: 'load-balancer-api-external: resolved host name a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:22:51Z" - latency: 5.554455ms message: 'load-balancer-api-external: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:21:51Z" - latency: 10.080993ms message: 'load-balancer-api-external: resolved host name a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:21:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:43:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-241-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-241.ec2.internal uid: 3309a306-1d01-4f9c-bb89-b029d5140f10 resourceVersion: "31580" uid: 718fc981-4e5d-4277-bb5c-130f7c48529d spec: sourcePod: network-check-source-7b678d77c7-gdtq9 targetEndpoint: a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T17:49:51Z" message: 'load-balancer-api-internal: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.779612ms message: 'load-balancer-api-internal: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:25:51Z" - latency: 12.199648ms message: 'load-balancer-api-internal: resolved host name a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:25:51Z" - latency: 5.295265ms message: 'load-balancer-api-internal: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:24:51Z" - latency: 12.335023ms message: 'load-balancer-api-internal: resolved host name a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:24:51Z" - latency: 4.925673ms message: 'load-balancer-api-internal: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:23:51Z" - latency: 6.893373ms message: 'load-balancer-api-internal: resolved host name a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:23:51Z" - latency: 5.506989ms message: 'load-balancer-api-internal: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:22:51Z" - latency: 7.659464ms message: 'load-balancer-api-internal: resolved host name a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:22:51Z" - latency: 5.567628ms message: 'load-balancer-api-internal: tcp connection to a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:21:51Z" - latency: 10.231764ms message: 'load-balancer-api-internal: resolved host name a5dbeb873bf5743b28c1f9608e26d001-3b59e0f94436e850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T18:21:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:43:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-241-to-network-check-target-ip-10-0-128-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-241.ec2.internal uid: 3309a306-1d01-4f9c-bb89-b029d5140f10 resourceVersion: "31574" uid: 3699a119-85aa-4b45-93ca-86c57d235a32 spec: sourcePod: network-check-source-7b678d77c7-gdtq9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:50:51Z" message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 764.815µs message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:25:51Z" - latency: 810.229µs message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:24:51Z" - latency: 801.853µs message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:23:51Z" - latency: 793.853µs message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:22:51Z" - latency: 1.126329ms message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:21:51Z" - latency: 812.626µs message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:20:51Z" - latency: 745.535µs message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:19:51Z" - latency: 1.285421ms message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:18:51Z" - latency: 852.09µs message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:17:51Z" - latency: 800.425µs message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:16:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:43:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-241-to-network-check-target-ip-10-0-133-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-241.ec2.internal uid: 3309a306-1d01-4f9c-bb89-b029d5140f10 resourceVersion: "31575" uid: ae6aac9a-a5f1-420f-9956-c6100fdcf0ab spec: sourcePod: network-check-source-7b678d77c7-gdtq9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:50:51Z" message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.902003ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:25:51Z" - latency: 1.865703ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:24:51Z" - latency: 1.668532ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:23:51Z" - latency: 1.996816ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:22:51Z" - latency: 1.854525ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:21:51Z" - latency: 1.933468ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:20:51Z" - latency: 1.80664ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:19:51Z" - latency: 1.599198ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:18:51Z" - latency: 1.814646ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:17:51Z" - latency: 1.816209ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:16:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:43:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-241-to-network-check-target-ip-10-0-134-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-241.ec2.internal uid: 3309a306-1d01-4f9c-bb89-b029d5140f10 resourceVersion: "31576" uid: 7dc42cb9-3958-4015-8014-c02c8cb6ae42 spec: sourcePod: network-check-source-7b678d77c7-gdtq9 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:50:51Z" message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.0791ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:25:51Z" - latency: 2.07003ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:24:51Z" - latency: 2.025838ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:23:51Z" - latency: 2.611589ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:22:51Z" - latency: 2.314088ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:21:51Z" - latency: 2.253958ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:20:51Z" - latency: 2.185201ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:19:51Z" - latency: 2.273862ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:18:51Z" - latency: 2.24223ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:17:51Z" - latency: 2.162955ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:16:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:43:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-241-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-241.ec2.internal uid: 3309a306-1d01-4f9c-bb89-b029d5140f10 resourceVersion: "31577" uid: fe6a240f-3b93-4ae2-82bf-800edd0376df spec: sourcePod: network-check-source-7b678d77c7-gdtq9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T17:49:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.162185ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:25:51Z" - latency: 1.853361ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:25:51Z" - latency: 1.305071ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:24:51Z" - latency: 1.703873ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:24:51Z" - latency: 1.06558ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:23:51Z" - latency: 1.75031ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:23:51Z" - latency: 1.306939ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:22:51Z" - latency: 1.651513ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:22:51Z" - latency: 993.364µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:21:51Z" - latency: 1.838855ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T18:21:51Z" kind: List metadata: resourceVersion: ""