apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:17:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-162-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-162.ec2.internal uid: bd1076f9-cb86-463c-ab28-1833a8feca12 resourceVersion: "64468" uid: dd3a0e4e-8dd7-46c9-90e4-e73cb34fd844 spec: sourcePod: network-check-source-7d88cb55d8-v47p6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T00:24:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.067614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:59:08Z" - latency: 2.263657ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:58:08Z" - latency: 980.859µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:57:08Z" - latency: 1.420345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:08Z" - latency: 863.307µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:08Z" - latency: 1.432878ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:08Z" - latency: 1.654189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:08Z" - latency: 1.27796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:08Z" - latency: 5.747664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:51:08Z" - latency: 1.169257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:50:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:17:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-162-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-162.ec2.internal uid: bd1076f9-cb86-463c-ab28-1833a8feca12 resourceVersion: "64469" uid: 278a8798-28c8-4266-8603-daceff661318 spec: sourcePod: network-check-source-7d88cb55d8-v47p6 targetEndpoint: a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T00:23:08Z" message: 'load-balancer-api-external: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.451812ms message: 'load-balancer-api-external: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:59:08Z" - latency: 8.440638ms message: 'load-balancer-api-external: resolved host name a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:59:08Z" - latency: 4.582873ms message: 'load-balancer-api-external: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:58:08Z" - latency: 9.224366ms message: 'load-balancer-api-external: resolved host name a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:58:08Z" - latency: 4.291794ms message: 'load-balancer-api-external: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:57:08Z" - latency: 7.618618ms message: 'load-balancer-api-external: resolved host name a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:57:08Z" - latency: 4.359085ms message: 'load-balancer-api-external: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:08Z" - latency: 9.543459ms message: 'load-balancer-api-external: resolved host name a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:56:08Z" - latency: 4.208858ms message: 'load-balancer-api-external: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:08Z" - latency: 15.792357ms message: 'load-balancer-api-external: resolved host name a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:55:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:17:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-162-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-162.ec2.internal uid: bd1076f9-cb86-463c-ab28-1833a8feca12 resourceVersion: "64470" uid: 61b1b7e6-dcb7-4491-b088-cc59fe75080d spec: sourcePod: network-check-source-7d88cb55d8-v47p6 targetEndpoint: a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T00:23:08Z" message: 'load-balancer-api-internal: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.577995ms message: 'load-balancer-api-internal: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:59:08Z" - latency: 8.465934ms message: 'load-balancer-api-internal: resolved host name a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:59:08Z" - latency: 4.585773ms message: 'load-balancer-api-internal: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:58:08Z" - latency: 9.242878ms message: 'load-balancer-api-internal: resolved host name a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:58:08Z" - latency: 4.261814ms message: 'load-balancer-api-internal: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:57:08Z" - latency: 7.652677ms message: 'load-balancer-api-internal: resolved host name a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:57:08Z" - latency: 4.350827ms message: 'load-balancer-api-internal: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:08Z" - latency: 9.479041ms message: 'load-balancer-api-internal: resolved host name a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:56:08Z" - latency: 5.481049ms message: 'load-balancer-api-internal: tcp connection to a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:08Z" - latency: 15.823273ms message: 'load-balancer-api-internal: resolved host name a99ec69f158174220955c5cb07015c93-bae0567f7b868eb6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:55:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:17:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-162-to-network-check-target-ip-10-0-130-20 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-162.ec2.internal uid: bd1076f9-cb86-463c-ab28-1833a8feca12 resourceVersion: "64465" uid: dbcae0a4-53ce-4e4c-9b43-b1107a33150e spec: sourcePod: network-check-source-7d88cb55d8-v47p6 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T00:24:08Z" message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.05913ms message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:59:08Z" - latency: 1.96387ms message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:58:08Z" - latency: 2.024913ms message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:57:08Z" - latency: 2.022989ms message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:08Z" - latency: 2.081506ms message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:08Z" - latency: 2.039987ms message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:08Z" - latency: 1.98968ms message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:08Z" - latency: 2.032819ms message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:08Z" - latency: 3.839697ms message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:51:08Z" - latency: 2.016439ms message: 'network-check-target-ip-10-0-130-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:50:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:17:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-162-to-network-check-target-ip-10-0-134-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-162.ec2.internal uid: bd1076f9-cb86-463c-ab28-1833a8feca12 resourceVersion: "64464" uid: e2a0ab38-1bee-4182-a6f7-5156a0b8e9b6 spec: sourcePod: network-check-source-7d88cb55d8-v47p6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T00:24:08Z" message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.533919ms message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:59:08Z" - latency: 1.377481ms message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:58:08Z" - latency: 1.01947ms message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:57:08Z" - latency: 1.655684ms message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:08Z" - latency: 1.325161ms message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:08Z" - latency: 1.235138ms message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:08Z" - latency: 1.147332ms message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:08Z" - latency: 1.051485ms message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:08Z" - latency: 1.374971ms message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:51:08Z" - latency: 1.39176ms message: 'network-check-target-ip-10-0-134-162: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:50:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:17:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-162-to-network-check-target-ip-10-0-135-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-162.ec2.internal uid: bd1076f9-cb86-463c-ab28-1833a8feca12 resourceVersion: "64467" uid: 171f5584-dcf9-47b9-8de9-49a0f863f969 spec: sourcePod: network-check-source-7d88cb55d8-v47p6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T00:24:08Z" message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.452107ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:59:08Z" - latency: 2.373541ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:58:08Z" - latency: 2.40502ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:57:08Z" - latency: 2.210573ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:08Z" - latency: 2.308151ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:08Z" - latency: 2.472595ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:08Z" - latency: 2.134384ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:08Z" - latency: 2.402872ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:08Z" - latency: 4.830202ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:51:08Z" - latency: 2.425263ms message: 'network-check-target-ip-10-0-135-176: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:50:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:17:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-162-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-162.ec2.internal uid: bd1076f9-cb86-463c-ab28-1833a8feca12 resourceVersion: "64466" uid: bb49c9b1-7cfb-4761-bc62-26bdc6942f79 spec: sourcePod: network-check-source-7d88cb55d8-v47p6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T00:23:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.879µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:59:08Z" - latency: 1.910029ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T00:59:08Z" - latency: 947.56µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:58:08Z" - latency: 2.861302ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T00:58:08Z" - latency: 1.109978ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:57:08Z" - latency: 2.222909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T00:57:08Z" - latency: 759.44µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:08Z" - latency: 2.4103ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T00:56:08Z" - latency: 845.265µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:08Z" - latency: 2.002406ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T00:55:08Z" kind: List metadata: resourceVersion: ""