apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T12:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-229-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-229.ec2.internal uid: 3e6d2622-4302-465d-a788-2cfa1c77e261 resourceVersion: "68357" uid: 99770625-b835-41d9-b5b8-30609199b2eb spec: sourcePod: network-check-source-6f8b768455-jt8jw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-15T12:13: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.429798ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:41:23Z" - latency: 1.140531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:40:23Z" - latency: 1.153701ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:39:23Z" - latency: 1.190155ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:38:23Z" - latency: 1.027498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:37:23Z" - latency: 1.306193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:36:23Z" - latency: 905.094µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:35:23Z" - latency: 997.256µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:34:23Z" - latency: 1.027758ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:33:23Z" - latency: 966.464µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:32:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T12:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-229-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-229.ec2.internal uid: 3e6d2622-4302-465d-a788-2cfa1c77e261 resourceVersion: "69207" uid: 80713a59-f08c-4cd2-bf0a-ace3dccd4a12 spec: sourcePod: network-check-source-6f8b768455-jt8jw targetEndpoint: ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T12:12:23Z" message: 'load-balancer-api-external: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.071375ms message: 'load-balancer-api-external: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:42:23Z" - latency: 8.364428ms message: 'load-balancer-api-external: resolved host name ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T12:42:23Z" - latency: 3.618935ms message: 'load-balancer-api-external: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:41:23Z" - latency: 8.417989ms message: 'load-balancer-api-external: resolved host name ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T12:41:23Z" - latency: 4.257657ms message: 'load-balancer-api-external: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:40:23Z" - latency: 8.276454ms message: 'load-balancer-api-external: resolved host name ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T12:40:23Z" - latency: 5.380388ms message: 'load-balancer-api-external: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:39:23Z" - latency: 8.514221ms message: 'load-balancer-api-external: resolved host name ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T12:39:23Z" - latency: 4.151665ms message: 'load-balancer-api-external: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:38:23Z" - latency: 9.20363ms message: 'load-balancer-api-external: resolved host name ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T12:38:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T12:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-229-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-229.ec2.internal uid: 3e6d2622-4302-465d-a788-2cfa1c77e261 resourceVersion: "69208" uid: 73d8c42b-6865-4149-924f-36a67d973e94 spec: sourcePod: network-check-source-6f8b768455-jt8jw targetEndpoint: ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T12:12:23Z" message: 'load-balancer-api-internal: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.060571ms message: 'load-balancer-api-internal: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:42:23Z" - latency: 8.412711ms message: 'load-balancer-api-internal: resolved host name ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T12:42:23Z" - latency: 3.613875ms message: 'load-balancer-api-internal: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:41:23Z" - latency: 8.537216ms message: 'load-balancer-api-internal: resolved host name ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T12:41:23Z" - latency: 4.162724ms message: 'load-balancer-api-internal: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:40:23Z" - latency: 8.381095ms message: 'load-balancer-api-internal: resolved host name ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T12:40:23Z" - latency: 4.960582ms message: 'load-balancer-api-internal: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:39:23Z" - latency: 8.454567ms message: 'load-balancer-api-internal: resolved host name ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T12:39:23Z" - latency: 4.78243ms message: 'load-balancer-api-internal: tcp connection to ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:38:23Z" - latency: 9.273056ms message: 'load-balancer-api-internal: resolved host name ad071a59b804d416788705bc124cc0d0-7b79b7d58ccd2a42.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T12:38:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T12:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-229-to-network-check-target-ip-10-0-130-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-229.ec2.internal uid: 3e6d2622-4302-465d-a788-2cfa1c77e261 resourceVersion: "68355" uid: 52312e02-e3db-43e0-a83e-9f02db871083 spec: sourcePod: network-check-source-6f8b768455-jt8jw targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-15T12:13:23Z" message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.963537ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:41:23Z" - latency: 2.262104ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:40:23Z" - latency: 1.953457ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:39:23Z" - latency: 2.195108ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:38:23Z" - latency: 2.095993ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:37:23Z" - latency: 2.097937ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:36:23Z" - latency: 2.24093ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:35:23Z" - latency: 1.956419ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:34:23Z" - latency: 2.189008ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:33:23Z" - latency: 2.17372ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:32:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T12:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-229-to-network-check-target-ip-10-0-140-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-229.ec2.internal uid: 3e6d2622-4302-465d-a788-2cfa1c77e261 resourceVersion: "68356" uid: 7fe310b7-5b3e-4555-917c-4b63c7e95cc1 spec: sourcePod: network-check-source-6f8b768455-jt8jw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-15T12:13:23Z" message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.411352ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:41:23Z" - latency: 2.69875ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:40:23Z" - latency: 2.099214ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:39:23Z" - latency: 2.545148ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:38:23Z" - latency: 2.142912ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:37:23Z" - latency: 2.319485ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:36:23Z" - latency: 2.302013ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:35:23Z" - latency: 2.286004ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:34:23Z" - latency: 2.512987ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:33:23Z" - latency: 2.35693ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:32:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T12:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-229-to-network-check-target-ip-10-0-140-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-229.ec2.internal uid: 3e6d2622-4302-465d-a788-2cfa1c77e261 resourceVersion: "68354" uid: 7250a7ff-a5b2-4d9e-b8ca-ba73f376c309 spec: sourcePod: network-check-source-6f8b768455-jt8jw targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T12:13:23Z" message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.161131ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:41:23Z" - latency: 953.795µs message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:40:23Z" - latency: 1.034192ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:39:23Z" - latency: 1.055493ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:38:23Z" - latency: 1.223761ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:37:23Z" - latency: 1.042963ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:36:23Z" - latency: 891.11µs message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:35:23Z" - latency: 1.098215ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:34:23Z" - latency: 1.158231ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:33:23Z" - latency: 1.089111ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:32:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T12:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-229-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-229.ec2.internal uid: 3e6d2622-4302-465d-a788-2cfa1c77e261 resourceVersion: "69206" uid: d7d29b4c-72ca-4022-a1f5-5ff84ea3aba8 spec: sourcePod: network-check-source-6f8b768455-jt8jw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-15T12:12:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.28µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:42:23Z" - latency: 1.876796ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T12:42:23Z" - latency: 1.234565ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:41:23Z" - latency: 1.844043ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T12:41:23Z" - latency: 1.073227ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:40:23Z" - latency: 1.728ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T12:40:23Z" - latency: 778.732µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:39:23Z" - latency: 1.896159ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T12:39:23Z" - latency: 1.216947ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T12:38:23Z" - latency: 1.816239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T12:38:23Z" kind: List metadata: resourceVersion: ""