apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:47:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 93000371-c4d3-4f29-a34c-7a70e85a1d27 resourceVersion: "55562" uid: 6441871d-5970-4cc5-abe7-95910ee8f882 spec: sourcePod: network-check-source-989f8b8dc-959wx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T17:54:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.010195ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:22:25Z" - latency: 1.035815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:21:25Z" - latency: 734.131µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:20:25Z" - latency: 864.162µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:19:25Z" - latency: 4.117248ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:18:25Z" - latency: 1.08892ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:25Z" - latency: 5.930474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:25Z" - latency: 916.933µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:25Z" - latency: 983.387µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:25Z" - latency: 1.501596ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:13:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:47:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 93000371-c4d3-4f29-a34c-7a70e85a1d27 resourceVersion: "56607" uid: 6ea6f9b1-3330-4511-b113-ebef843650be spec: sourcePod: network-check-source-989f8b8dc-959wx targetEndpoint: ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T17:53:25Z" message: 'load-balancer-api-external: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.692649ms message: 'load-balancer-api-external: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:23:25Z" - latency: 6.482827ms message: 'load-balancer-api-external: resolved host name ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:23:25Z" - latency: 5.18751ms message: 'load-balancer-api-external: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:22:25Z" - latency: 6.96438ms message: 'load-balancer-api-external: resolved host name ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:22:25Z" - latency: 4.083666ms message: 'load-balancer-api-external: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:21:25Z" - latency: 5.981361ms message: 'load-balancer-api-external: resolved host name ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:21:25Z" - latency: 4.643836ms message: 'load-balancer-api-external: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:20:25Z" - latency: 7.325437ms message: 'load-balancer-api-external: resolved host name ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:20:25Z" - latency: 5.227083ms message: 'load-balancer-api-external: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:19:25Z" - latency: 6.448632ms message: 'load-balancer-api-external: resolved host name ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:19:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:47:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 93000371-c4d3-4f29-a34c-7a70e85a1d27 resourceVersion: "56608" uid: 53a18e93-49fa-4b45-921e-c5b7a1ca2758 spec: sourcePod: network-check-source-989f8b8dc-959wx targetEndpoint: ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T17:53:25Z" message: 'load-balancer-api-internal: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.792612ms message: 'load-balancer-api-internal: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:23:25Z" - latency: 6.536361ms message: 'load-balancer-api-internal: resolved host name ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:23:25Z" - latency: 4.110628ms message: 'load-balancer-api-internal: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:22:25Z" - latency: 6.936814ms message: 'load-balancer-api-internal: resolved host name ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:22:25Z" - latency: 4.427128ms message: 'load-balancer-api-internal: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:21:25Z" - latency: 5.914435ms message: 'load-balancer-api-internal: resolved host name ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:21:25Z" - latency: 5.564092ms message: 'load-balancer-api-internal: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:20:25Z" - latency: 7.367129ms message: 'load-balancer-api-internal: resolved host name ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:20:25Z" - latency: 5.241529ms message: 'load-balancer-api-internal: tcp connection to ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:19:25Z" - latency: 6.391753ms message: 'load-balancer-api-internal: resolved host name ac46f68b0506c4826827af5c65d059d9-53e269ea6629757b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:19:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:47:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-network-check-target-ip-10-0-133-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 93000371-c4d3-4f29-a34c-7a70e85a1d27 resourceVersion: "55559" uid: 4810e9e8-3bd3-4261-b482-8162338c46f0 spec: sourcePod: network-check-source-989f8b8dc-959wx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T17:54:25Z" message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.169477ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:22:25Z" - latency: 2.11223ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:21:25Z" - latency: 1.790758ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:20:25Z" - latency: 2.285913ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:19:25Z" - latency: 4.201879ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:18:25Z" - latency: 2.377698ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:25Z" - latency: 4.463629ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:25Z" - latency: 2.046888ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:25Z" - latency: 2.405923ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:25Z" - latency: 2.621538ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:13:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:47:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-network-check-target-ip-10-0-133-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 93000371-c4d3-4f29-a34c-7a70e85a1d27 resourceVersion: "55560" uid: 6e472a34-9893-4e45-9a9e-ef82648a7f6c spec: sourcePod: network-check-source-989f8b8dc-959wx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T17:54:25Z" message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.71582ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:22:25Z" - latency: 2.431119ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:21:25Z" - latency: 2.394847ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:20:25Z" - latency: 2.293313ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:19:25Z" - latency: 4.73791ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:18:25Z" - latency: 2.6026ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:25Z" - latency: 4.531767ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:25Z" - latency: 1.944159ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:25Z" - latency: 2.176217ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:25Z" - latency: 3.174334ms message: 'network-check-target-ip-10-0-133-236: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:13:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:47:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-network-check-target-ip-10-0-140-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 93000371-c4d3-4f29-a34c-7a70e85a1d27 resourceVersion: "55558" uid: 9acd91f4-f9d5-4134-a6d3-50421ae85466 spec: sourcePod: network-check-source-989f8b8dc-959wx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T17:54:25Z" message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.196237ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:22:25Z" - latency: 907.489µs message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:21:25Z" - latency: 756.285µs message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:20:25Z" - latency: 854.505µs message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:19:25Z" - latency: 5.734775ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:18:25Z" - latency: 948.315µs message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:25Z" - latency: 6.046392ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:25Z" - latency: 1.219308ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:25Z" - latency: 836.347µs message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:25Z" - latency: 2.126361ms message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:13:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:47:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-115-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-115.ec2.internal uid: 93000371-c4d3-4f29-a34c-7a70e85a1d27 resourceVersion: "56606" uid: 99f59aab-19a4-4438-8343-fc9250d3ef58 spec: sourcePod: network-check-source-989f8b8dc-959wx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T17:53:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 865.435µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:23:25Z" - latency: 1.743374ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T18:23:25Z" - latency: 1.060999ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:22:25Z" - latency: 1.967158ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T18:22:25Z" - latency: 1.008777ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:21:25Z" - latency: 1.864552ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T18:21:25Z" - latency: 999.284µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:20:25Z" - latency: 1.758601ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T18:20:25Z" - latency: 1.021205ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:19:25Z" - latency: 2.108234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T18:19:25Z" kind: List metadata: resourceVersion: ""