apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:41:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-47-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-47.ec2.internal uid: 5291cce6-b3ff-454d-b1f5-f0e326ec4ed2 resourceVersion: "31371" uid: 26774b8c-2c3a-4ea5-b7d0-b6912da339dc spec: sourcePod: network-check-source-8894fc9bd-xx69l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T16:48:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 924.606µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:23:36Z" - latency: 813.758µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:22:36Z" - latency: 954.806µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:21:36Z" - latency: 1.035295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:20:36Z" - latency: 1.097024ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:19:36Z" - latency: 904.936µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:18:36Z" - latency: 1.165731ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:17:36Z" - latency: 1.139957ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:16:36Z" - latency: 795.86µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:15:36Z" - latency: 943.327µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:14:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:41:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-47-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-47.ec2.internal uid: 5291cce6-b3ff-454d-b1f5-f0e326ec4ed2 resourceVersion: "31373" uid: 1cd19e92-7ef4-494f-a5ca-6793e3b42d07 spec: sourcePod: network-check-source-8894fc9bd-xx69l targetEndpoint: ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T16:47:36Z" message: 'load-balancer-api-external: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.343329ms message: 'load-balancer-api-external: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:23:36Z" - latency: 8.308436ms message: 'load-balancer-api-external: resolved host name ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:23:36Z" - latency: 3.926886ms message: 'load-balancer-api-external: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:22:36Z" - latency: 7.683047ms message: 'load-balancer-api-external: resolved host name ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:22:36Z" - latency: 4.103517ms message: 'load-balancer-api-external: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:21:36Z" - latency: 8.006831ms message: 'load-balancer-api-external: resolved host name ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:21:36Z" - latency: 4.499613ms message: 'load-balancer-api-external: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:20:36Z" - latency: 10.581044ms message: 'load-balancer-api-external: resolved host name ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:20:36Z" - latency: 4.632476ms message: 'load-balancer-api-external: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:19:36Z" - latency: 7.988011ms message: 'load-balancer-api-external: resolved host name ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:19:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:41:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-47-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-47.ec2.internal uid: 5291cce6-b3ff-454d-b1f5-f0e326ec4ed2 resourceVersion: "31372" uid: 299d1d01-a0ea-4421-91f3-43e7b466568c spec: sourcePod: network-check-source-8894fc9bd-xx69l targetEndpoint: ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T16:47:36Z" message: 'load-balancer-api-internal: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.230637ms message: 'load-balancer-api-internal: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:23:36Z" - latency: 8.383248ms message: 'load-balancer-api-internal: resolved host name ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:23:36Z" - latency: 4.027234ms message: 'load-balancer-api-internal: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:22:36Z" - latency: 7.753716ms message: 'load-balancer-api-internal: resolved host name ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:22:36Z" - latency: 3.431204ms message: 'load-balancer-api-internal: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:21:36Z" - latency: 8.040571ms message: 'load-balancer-api-internal: resolved host name ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:21:36Z" - latency: 4.440944ms message: 'load-balancer-api-internal: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:20:36Z" - latency: 10.615802ms message: 'load-balancer-api-internal: resolved host name ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:20:36Z" - latency: 4.65293ms message: 'load-balancer-api-internal: tcp connection to ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:19:36Z" - latency: 8.047826ms message: 'load-balancer-api-internal: resolved host name ad5a83301898545a2a4b6f9fcd26aa85-e35855ac38ca2517.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:19:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:41:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-47-to-network-check-target-ip-10-0-128-44 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-47.ec2.internal uid: 5291cce6-b3ff-454d-b1f5-f0e326ec4ed2 resourceVersion: "31368" uid: 65fec818-d793-42dd-a791-72fd92e6568e spec: sourcePod: network-check-source-8894fc9bd-xx69l targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T16:48:36Z" message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.180109ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:23:36Z" - latency: 1.803513ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:22:36Z" - latency: 1.713164ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:21:36Z" - latency: 2.047126ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:20:36Z" - latency: 2.287135ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:19:36Z" - latency: 2.099256ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:18:36Z" - latency: 1.70122ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:17:36Z" - latency: 1.902205ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:16:36Z" - latency: 1.92724ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:15:36Z" - latency: 1.778512ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:14:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:41:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-47-to-network-check-target-ip-10-0-131-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-47.ec2.internal uid: 5291cce6-b3ff-454d-b1f5-f0e326ec4ed2 resourceVersion: "31367" uid: 4b69da6a-f73d-4626-b35f-34f668903c9e spec: sourcePod: network-check-source-8894fc9bd-xx69l targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T16:48:36Z" message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 873.514µs message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:23:36Z" - latency: 831.884µs message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:22:36Z" - latency: 980.91µs message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:21:36Z" - latency: 1.055384ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:20:36Z" - latency: 862.07µs message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:19:36Z" - latency: 908.359µs message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:18:36Z" - latency: 855.536µs message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:17:36Z" - latency: 782.226µs message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:16:36Z" - latency: 664.987µs message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:15:36Z" - latency: 891.495µs message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:14:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:41:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-47-to-network-check-target-ip-10-0-143-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-47.ec2.internal uid: 5291cce6-b3ff-454d-b1f5-f0e326ec4ed2 resourceVersion: "31370" uid: b8e57f9c-2974-4da3-a35e-d6a4b331aa08 spec: sourcePod: network-check-source-8894fc9bd-xx69l targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T16:48:36Z" message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.962071ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:23:36Z" - latency: 1.933074ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:22:36Z" - latency: 1.944861ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:21:36Z" - latency: 2.205779ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:20:36Z" - latency: 2.719151ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:19:36Z" - latency: 2.150702ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:18:36Z" - latency: 2.163935ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:17:36Z" - latency: 2.00922ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:16:36Z" - latency: 1.771969ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:15:36Z" - latency: 2.095338ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:14:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:41:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-47-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-47.ec2.internal uid: 5291cce6-b3ff-454d-b1f5-f0e326ec4ed2 resourceVersion: "31369" uid: a9422351-1585-4429-a903-74c74e383773 spec: sourcePod: network-check-source-8894fc9bd-xx69l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T16:47:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 802.636µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:23:36Z" - latency: 1.669425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T17:23:36Z" - latency: 823.167µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:22:36Z" - latency: 1.650483ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T17:22:36Z" - latency: 872.802µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:21:36Z" - latency: 1.663848ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T17:21:36Z" - latency: 933.626µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:20:36Z" - latency: 1.895459ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T17:20:36Z" - latency: 890.401µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:19:36Z" - latency: 1.987842ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T17:19:36Z" kind: List metadata: resourceVersion: ""