apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:54:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-223-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-223.ec2.internal uid: 61f55ccf-e2c9-421c-801a-4262a986d734 resourceVersion: "63174" uid: 566fc40b-14e6-41d7-b2bb-73fce11f7577 spec: sourcePod: network-check-source-7bc5b6bf85-nl4nv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T22:01:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 921.282µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:36:02Z" - latency: 1.176398ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:35:02Z" - latency: 1.394334ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:34:02Z" - latency: 1.705447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:33:02Z" - latency: 1.515781ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:32:02Z" - latency: 1.018659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:31:02Z" - latency: 971.623µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:30:02Z" - latency: 1.662307ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:29:02Z" - latency: 1.18478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:28:02Z" - latency: 1.179002ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:27:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:54:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-223-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-223.ec2.internal uid: 61f55ccf-e2c9-421c-801a-4262a986d734 resourceVersion: "63176" uid: 39ea1e14-0a22-4416-89d0-8c4b777e9f4e spec: sourcePod: network-check-source-7bc5b6bf85-nl4nv targetEndpoint: ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T22:00:02Z" message: 'load-balancer-api-external: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.342323ms message: 'load-balancer-api-external: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:36:02Z" - latency: 7.253554ms message: 'load-balancer-api-external: resolved host name ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T22:36:02Z" - latency: 4.210128ms message: 'load-balancer-api-external: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:35:02Z" - latency: 6.945343ms message: 'load-balancer-api-external: resolved host name ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T22:35:02Z" - latency: 4.381273ms message: 'load-balancer-api-external: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:34:02Z" - latency: 7.172762ms message: 'load-balancer-api-external: resolved host name ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T22:34:02Z" - latency: 5.031544ms message: 'load-balancer-api-external: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:33:02Z" - latency: 7.866028ms message: 'load-balancer-api-external: resolved host name ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T22:33:02Z" - latency: 4.029304ms message: 'load-balancer-api-external: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:32:02Z" - latency: 7.341119ms message: 'load-balancer-api-external: resolved host name ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T22:32:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:54:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-223-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-223.ec2.internal uid: 61f55ccf-e2c9-421c-801a-4262a986d734 resourceVersion: "63175" uid: 0a934006-2100-4090-8771-f09ae96de8a9 spec: sourcePod: network-check-source-7bc5b6bf85-nl4nv targetEndpoint: ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T22:00:02Z" message: 'load-balancer-api-internal: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.334005ms message: 'load-balancer-api-internal: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:36:02Z" - latency: 7.112898ms message: 'load-balancer-api-internal: resolved host name ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T22:36:02Z" - latency: 4.34123ms message: 'load-balancer-api-internal: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:35:02Z" - latency: 6.86257ms message: 'load-balancer-api-internal: resolved host name ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T22:35:02Z" - latency: 4.425194ms message: 'load-balancer-api-internal: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:34:02Z" - latency: 7.332111ms message: 'load-balancer-api-internal: resolved host name ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T22:34:02Z" - latency: 5.000916ms message: 'load-balancer-api-internal: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:33:02Z" - latency: 7.804068ms message: 'load-balancer-api-internal: resolved host name ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T22:33:02Z" - latency: 4.474734ms message: 'load-balancer-api-internal: tcp connection to ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:32:02Z" - latency: 7.190045ms message: 'load-balancer-api-internal: resolved host name ae3866217cd734c27a8fcb9377bcd0f9-c73286ddf73099c5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T22:32:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:54:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-223-to-network-check-target-ip-10-0-134-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-223.ec2.internal uid: 61f55ccf-e2c9-421c-801a-4262a986d734 resourceVersion: "63171" uid: 3e9dcf10-d3ef-4976-a337-ef57f1f0d320 spec: sourcePod: network-check-source-7bc5b6bf85-nl4nv targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T22:01:02Z" message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.466869ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:36:02Z" - latency: 2.337675ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:35:02Z" - latency: 2.382023ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:34:02Z" - latency: 2.244993ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:33:02Z" - latency: 2.25418ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:32:02Z" - latency: 2.289515ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:31:02Z" - latency: 1.938501ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:30:02Z" - latency: 2.322172ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:29:02Z" - latency: 2.477925ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:28:02Z" - latency: 2.444535ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:27:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:54:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-223-to-network-check-target-ip-10-0-142-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-223.ec2.internal uid: 61f55ccf-e2c9-421c-801a-4262a986d734 resourceVersion: "63172" uid: f35ed0f7-3b76-48e8-800b-1289b893a32f spec: sourcePod: network-check-source-7bc5b6bf85-nl4nv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T22:01:02Z" message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.91923ms message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:36:02Z" - latency: 1.994325ms message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:35:02Z" - latency: 1.790776ms message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:34:02Z" - latency: 1.928496ms message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:33:02Z" - latency: 2.005458ms message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:32:02Z" - latency: 1.892093ms message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:31:02Z" - latency: 1.927394ms message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:30:02Z" - latency: 1.987623ms message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:29:02Z" - latency: 2.036249ms message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:28:02Z" - latency: 2.014649ms message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:27:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:54:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-223-to-network-check-target-ip-10-0-143-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-223.ec2.internal uid: 61f55ccf-e2c9-421c-801a-4262a986d734 resourceVersion: "63170" uid: 855e036b-a100-42d1-8db3-11d176146eb7 spec: sourcePod: network-check-source-7bc5b6bf85-nl4nv targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T22:01:02Z" message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.664462ms message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:36:02Z" - latency: 1.574044ms message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:35:02Z" - latency: 1.07531ms message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:34:02Z" - latency: 936.031µs message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:33:02Z" - latency: 1.027458ms message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:32:02Z" - latency: 1.060563ms message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:31:02Z" - latency: 1.926915ms message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:30:02Z" - latency: 835.495µs message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:29:02Z" - latency: 1.841099ms message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:28:02Z" - latency: 934.763µs message: 'network-check-target-ip-10-0-143-223: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:27:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:54:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-223-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-223.ec2.internal uid: 61f55ccf-e2c9-421c-801a-4262a986d734 resourceVersion: "63173" uid: e57f58d1-7bbc-4b3c-926a-fd66dd391996 spec: sourcePod: network-check-source-7bc5b6bf85-nl4nv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T22:00:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.255333ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:36:02Z" - latency: 1.988443ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T22:36:02Z" - latency: 1.120933ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:35:02Z" - latency: 1.781014ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T22:35:02Z" - latency: 1.048779ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:34:02Z" - latency: 1.985553ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T22:34:02Z" - latency: 799.692µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:33:02Z" - latency: 2.126039ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T22:33:02Z" - latency: 818.633µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:32:02Z" - latency: 1.855105ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T22:32:02Z" kind: List metadata: resourceVersion: ""