apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:48:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 06215108-395f-4b5f-9f30-8eac0d7e0aef resourceVersion: "48813" uid: 5e6cbbc5-1553-4cfe-b2fd-6c8a03b96fba spec: sourcePod: network-check-source-869dcfcdcd-n48nt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T14:55:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.125109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:23:05Z" - latency: 1.38228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:22:05Z" - latency: 947.691µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:21:05Z" - latency: 715.955µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:20:05Z" - latency: 1.085527ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:19:05Z" - latency: 1.094701ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:18:05Z" - latency: 877.697µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:17:05Z" - latency: 1.152377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:16:05Z" - latency: 1.660244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:15:05Z" - latency: 1.052541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:14:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:48:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 06215108-395f-4b5f-9f30-8eac0d7e0aef resourceVersion: "49414" uid: 520c7d93-fc68-4b29-8c00-815dfe903624 spec: sourcePod: network-check-source-869dcfcdcd-n48nt targetEndpoint: af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T14:54:05Z" message: 'load-balancer-api-external: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.641309ms message: 'load-balancer-api-external: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:24:05Z" - latency: 7.197128ms message: 'load-balancer-api-external: resolved host name af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:24:05Z" - latency: 5.846019ms message: 'load-balancer-api-external: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:23:05Z" - latency: 6.94661ms message: 'load-balancer-api-external: resolved host name af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:23:05Z" - latency: 6.79497ms message: 'load-balancer-api-external: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:22:05Z" - latency: 8.00312ms message: 'load-balancer-api-external: resolved host name af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:22:05Z" - latency: 5.692259ms message: 'load-balancer-api-external: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:21:05Z" - latency: 6.880738ms message: 'load-balancer-api-external: resolved host name af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:21:05Z" - latency: 7.485124ms message: 'load-balancer-api-external: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:20:05Z" - latency: 6.538624ms message: 'load-balancer-api-external: resolved host name af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:20:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:48:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 06215108-395f-4b5f-9f30-8eac0d7e0aef resourceVersion: "49415" uid: 178e427c-e6c1-479a-9cab-15894c50d768 spec: sourcePod: network-check-source-869dcfcdcd-n48nt targetEndpoint: af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T14:54:05Z" message: 'load-balancer-api-internal: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.637623ms message: 'load-balancer-api-internal: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:24:05Z" - latency: 7.180444ms message: 'load-balancer-api-internal: resolved host name af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:24:05Z" - latency: 5.96821ms message: 'load-balancer-api-internal: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:23:05Z" - latency: 6.991434ms message: 'load-balancer-api-internal: resolved host name af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:23:05Z" - latency: 6.80779ms message: 'load-balancer-api-internal: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:22:05Z" - latency: 8.059839ms message: 'load-balancer-api-internal: resolved host name af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:22:05Z" - latency: 4.755625ms message: 'load-balancer-api-internal: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:21:05Z" - latency: 6.929526ms message: 'load-balancer-api-internal: resolved host name af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:21:05Z" - latency: 7.43122ms message: 'load-balancer-api-internal: tcp connection to af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:20:05Z" - latency: 6.514411ms message: 'load-balancer-api-internal: resolved host name af950f7e80c3f4b2daf745e8ba699ac6-1f750ef4e03b20ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T15:20:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:48:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-network-check-target-ip-10-0-133-29 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 06215108-395f-4b5f-9f30-8eac0d7e0aef resourceVersion: "48810" uid: df7a5e6a-765c-4acc-854b-a30a5bb06cd4 spec: sourcePod: network-check-source-869dcfcdcd-n48nt targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T14:55:05Z" message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.526µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:23:05Z" - latency: 1.554232ms message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:22:05Z" - latency: 1.184917ms message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:21:05Z" - latency: 1.468558ms message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:20:05Z" - latency: 947.88µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:19:05Z" - latency: 1.37091ms message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:18:05Z" - latency: 817.618µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:17:05Z" - latency: 823.704µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:16:05Z" - latency: 1.808227ms message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:15:05Z" - latency: 1.148526ms message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:14:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:48:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-network-check-target-ip-10-0-135-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 06215108-395f-4b5f-9f30-8eac0d7e0aef resourceVersion: "48811" uid: 4daed56f-5bb0-4791-9570-c1e3eb4a36db spec: sourcePod: network-check-source-869dcfcdcd-n48nt targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T14:55:05Z" message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.363156ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:23:05Z" - latency: 2.092419ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:22:05Z" - latency: 1.814641ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:21:05Z" - latency: 2.124545ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:20:05Z" - latency: 2.338921ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:19:05Z" - latency: 2.163333ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:18:05Z" - latency: 2.213265ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:17:05Z" - latency: 2.153898ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:16:05Z" - latency: 2.194104ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:15:05Z" - latency: 2.121427ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:14:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:48:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-network-check-target-ip-10-0-143-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 06215108-395f-4b5f-9f30-8eac0d7e0aef resourceVersion: "48812" uid: 0b0f1920-dfee-4196-91e1-cd1a8d9f7b27 spec: sourcePod: network-check-source-869dcfcdcd-n48nt targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T14:55:05Z" message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.845079ms message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:23:05Z" - latency: 1.725175ms message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:22:05Z" - latency: 1.836213ms message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:21:05Z" - latency: 1.693033ms message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:20:05Z" - latency: 2.016729ms message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:19:05Z" - latency: 1.986538ms message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:18:05Z" - latency: 1.707653ms message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:17:05Z" - latency: 1.937113ms message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:16:05Z" - latency: 1.672787ms message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:15:05Z" - latency: 1.818773ms message: 'network-check-target-ip-10-0-143-151: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:14:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:48:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 06215108-395f-4b5f-9f30-8eac0d7e0aef resourceVersion: "49413" uid: 86d0a5ee-79d5-4223-82a2-4591f4b3babb spec: sourcePod: network-check-source-869dcfcdcd-n48nt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T14:54:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 992.618µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:24:05Z" - latency: 1.704583ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T15:24:05Z" - latency: 924.008µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:23:05Z" - latency: 1.879112ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T15:23:05Z" - latency: 1.032204ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:22:05Z" - latency: 1.863701ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T15:22:05Z" - latency: 924.234µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:21:05Z" - latency: 1.644378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T15:21:05Z" - latency: 818.742µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T15:20:05Z" - latency: 2.255939ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T15:20:05Z" kind: List metadata: resourceVersion: ""