apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:56:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-8-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-8.ec2.internal uid: 9fa69cc0-55be-44d9-a7ba-c447c082d2bf resourceVersion: "33156" uid: 139edff5-4771-4bc2-8b11-da727ad278fb spec: sourcePod: network-check-source-8894fc9bd-6ldqm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T08:03:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.486302ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:17:23Z" - latency: 1.201299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:16:23Z" - latency: 1.146479ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:15:23Z" - latency: 1.090825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:14:23Z" - latency: 3.886751ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:23Z" - latency: 805.577µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:12:23Z" - latency: 835.221µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:11:23Z" - latency: 1.167949ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:10:23Z" - latency: 1.070535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:09:23Z" - latency: 934.529µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:56:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-8-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-8.ec2.internal uid: 9fa69cc0-55be-44d9-a7ba-c447c082d2bf resourceVersion: "35804" uid: e008b040-97f3-47fc-98c6-98078e04567e spec: sourcePod: network-check-source-8894fc9bd-6ldqm targetEndpoint: a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T08:02:23Z" message: 'load-balancer-api-external: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.183624ms message: 'load-balancer-api-external: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:20:23Z" - latency: 6.176367ms message: 'load-balancer-api-external: resolved host name a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:20:23Z" - latency: 5.157921ms message: 'load-balancer-api-external: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:19:23Z" - latency: 8.316786ms message: 'load-balancer-api-external: resolved host name a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:19:23Z" - latency: 4.578838ms message: 'load-balancer-api-external: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:18:23Z" - latency: 7.679184ms message: 'load-balancer-api-external: resolved host name a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:18:23Z" - latency: 4.729423ms message: 'load-balancer-api-external: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:17:23Z" - latency: 8.322692ms message: 'load-balancer-api-external: resolved host name a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:17:23Z" - latency: 6.050149ms message: 'load-balancer-api-external: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:16:23Z" - latency: 11.237936ms message: 'load-balancer-api-external: resolved host name a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:16:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:56:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-8-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-8.ec2.internal uid: 9fa69cc0-55be-44d9-a7ba-c447c082d2bf resourceVersion: "35805" uid: 9a11404c-731a-411a-8630-174f4869acf4 spec: sourcePod: network-check-source-8894fc9bd-6ldqm targetEndpoint: a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T08:02:23Z" message: 'load-balancer-api-internal: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.203954ms message: 'load-balancer-api-internal: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:20:23Z" - latency: 6.115812ms message: 'load-balancer-api-internal: resolved host name a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:20:23Z" - latency: 4.904523ms message: 'load-balancer-api-internal: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:19:23Z" - latency: 8.230469ms message: 'load-balancer-api-internal: resolved host name a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:19:23Z" - latency: 4.403992ms message: 'load-balancer-api-internal: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:18:23Z" - latency: 7.614076ms message: 'load-balancer-api-internal: resolved host name a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:18:23Z" - latency: 4.21947ms message: 'load-balancer-api-internal: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:17:23Z" - latency: 8.340236ms message: 'load-balancer-api-internal: resolved host name a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:17:23Z" - latency: 4.766207ms message: 'load-balancer-api-internal: tcp connection to a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:16:23Z" - latency: 12.434583ms message: 'load-balancer-api-internal: resolved host name a1383ff295c144a148ccfeb89def672e-97a09bad816491da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:16:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:56:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-8-to-network-check-target-ip-10-0-128-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-8.ec2.internal uid: 9fa69cc0-55be-44d9-a7ba-c447c082d2bf resourceVersion: "33155" uid: 443179e2-4eff-4967-b24a-63a72ebe2337 spec: sourcePod: network-check-source-8894fc9bd-6ldqm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T08:03:23Z" message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.958949ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:17:23Z" - latency: 4.187097ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:16:23Z" - latency: 2.324862ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:15:23Z" - latency: 2.192706ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:14:23Z" - latency: 2.297407ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:23Z" - latency: 2.055543ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:12:23Z" - latency: 2.535573ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:11:23Z" - latency: 2.646445ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:10:23Z" - latency: 2.184676ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:09:23Z" - latency: 2.246448ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:56:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-8-to-network-check-target-ip-10-0-137-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-8.ec2.internal uid: 9fa69cc0-55be-44d9-a7ba-c447c082d2bf resourceVersion: "33153" uid: 007e7e43-bfa9-4e04-a370-9228aa2bf565 spec: sourcePod: network-check-source-8894fc9bd-6ldqm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T08:03:23Z" message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.536997ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:17:23Z" - latency: 3.583966ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:16:23Z" - latency: 932.881µs message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:15:23Z" - latency: 892.016µs message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:14:23Z" - latency: 4.458108ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:23Z" - latency: 990.929µs message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:12:23Z" - latency: 1.158594ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:11:23Z" - latency: 956.853µs message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:10:23Z" - latency: 1.246369ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:09:23Z" - latency: 1.363377ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:56:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-8-to-network-check-target-ip-10-0-143-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-8.ec2.internal uid: 9fa69cc0-55be-44d9-a7ba-c447c082d2bf resourceVersion: "33154" uid: e888174f-c14f-4e88-8dcf-ee0a034e27c3 spec: sourcePod: network-check-source-8894fc9bd-6ldqm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T08:03:23Z" message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.363932ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:17:23Z" - latency: 3.688281ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:16:23Z" - latency: 2.244135ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:15:23Z" - latency: 2.691954ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:14:23Z" - latency: 5.9079ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:13:23Z" - latency: 2.28394ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:12:23Z" - latency: 2.516009ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:11:23Z" - latency: 2.56967ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:10:23Z" - latency: 2.179045ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:09:23Z" - latency: 2.361273ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:56:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-8-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-8.ec2.internal uid: 9fa69cc0-55be-44d9-a7ba-c447c082d2bf resourceVersion: "35801" uid: f8304f05-3c06-4256-9715-107ea8444acc spec: sourcePod: network-check-source-8894fc9bd-6ldqm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T08:02:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 813.867µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:20:23Z" - latency: 1.86955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:20:23Z" - latency: 1.22714ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:19:23Z" - latency: 1.835466ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:19:23Z" - latency: 944.171µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:18:23Z" - latency: 2.309739ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:18:23Z" - latency: 1.086071ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:17:23Z" - latency: 1.796177ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:17:23Z" - latency: 1.338814ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:16:23Z" - latency: 4.121062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:16:23Z" kind: List metadata: resourceVersion: ""