apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-28T19:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.ec2.internal uid: f51402ca-b56d-4609-988a-2aa319bba9a5 resourceVersion: "58730" uid: ea66ab82-e80e-4af2-8ee9-0ade709f3670 spec: sourcePod: network-check-source-8894fc9bd-9kcz9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-28T19:25:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 870.964µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:14:18Z" - latency: 1.470406ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:13:18Z" - latency: 964.839µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:12:18Z" - latency: 919.163µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:11:18Z" - latency: 843.178µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:10:18Z" - latency: 1.362657ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:09:18Z" - latency: 1.06795ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:08:18Z" - latency: 799.114µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:07:18Z" - latency: 1.553356ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:06:18Z" - latency: 1.112912ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:05:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-28T19:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.ec2.internal uid: f51402ca-b56d-4609-988a-2aa319bba9a5 resourceVersion: "62387" uid: ab1819aa-c135-4c9a-a6ae-4c81c08f3a7e spec: sourcePod: network-check-source-8894fc9bd-9kcz9 targetEndpoint: aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-28T19:24:19Z" message: 'load-balancer-api-external: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.380427ms message: 'load-balancer-api-external: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:18:18Z" - latency: 7.075925ms message: 'load-balancer-api-external: resolved host name aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-28T20:18:18Z" - latency: 3.925188ms message: 'load-balancer-api-external: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:17:18Z" - latency: 7.575613ms message: 'load-balancer-api-external: resolved host name aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-28T20:17:18Z" - latency: 4.007268ms message: 'load-balancer-api-external: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:16:18Z" - latency: 6.641046ms message: 'load-balancer-api-external: resolved host name aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-28T20:16:18Z" - latency: 4.310336ms message: 'load-balancer-api-external: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:15:18Z" - latency: 6.489159ms message: 'load-balancer-api-external: resolved host name aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-28T20:15:18Z" - latency: 4.709906ms message: 'load-balancer-api-external: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:14:18Z" - latency: 6.810153ms message: 'load-balancer-api-external: resolved host name aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-28T20:14:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-28T19:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.ec2.internal uid: f51402ca-b56d-4609-988a-2aa319bba9a5 resourceVersion: "62386" uid: 0decff4e-b034-4bae-9efe-3519d812a395 spec: sourcePod: network-check-source-8894fc9bd-9kcz9 targetEndpoint: aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-28T19:24:19Z" message: 'load-balancer-api-internal: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.356464ms message: 'load-balancer-api-internal: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:18:18Z" - latency: 7.10991ms message: 'load-balancer-api-internal: resolved host name aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-28T20:18:18Z" - latency: 3.958765ms message: 'load-balancer-api-internal: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:17:18Z" - latency: 7.523288ms message: 'load-balancer-api-internal: resolved host name aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-28T20:17:18Z" - latency: 3.987436ms message: 'load-balancer-api-internal: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:16:18Z" - latency: 6.722787ms message: 'load-balancer-api-internal: resolved host name aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-28T20:16:18Z" - latency: 4.334212ms message: 'load-balancer-api-internal: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:15:18Z" - latency: 6.567351ms message: 'load-balancer-api-internal: resolved host name aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-28T20:15:18Z" - latency: 4.719329ms message: 'load-balancer-api-internal: tcp connection to aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:14:18Z" - latency: 6.840297ms message: 'load-balancer-api-internal: resolved host name aaef9a840245e495a8d7c0dd4a53e956-c99837626b3b10b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-28T20:14:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-28T19:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-network-check-target-ip-10-0-133-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.ec2.internal uid: f51402ca-b56d-4609-988a-2aa319bba9a5 resourceVersion: "58728" uid: 4023a4e9-0d3b-4c3b-9444-f8c6b9628e91 spec: sourcePod: network-check-source-8894fc9bd-9kcz9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-28T19:25:18Z" message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.122718ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:14:18Z" - latency: 832.425µs message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:13:18Z" - latency: 761.967µs message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:12:18Z" - latency: 1.396429ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:11:18Z" - latency: 974.687µs message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:10:18Z" - latency: 636.003µs message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:09:18Z" - latency: 1.077869ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:08:18Z" - latency: 779.343µs message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:07:18Z" - latency: 1.164442ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:06:18Z" - latency: 1.3043ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:05:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-28T19:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-network-check-target-ip-10-0-139-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.ec2.internal uid: f51402ca-b56d-4609-988a-2aa319bba9a5 resourceVersion: "58727" uid: a822a3c3-f4ef-416c-b0b3-e643ed1b4243 spec: sourcePod: network-check-source-8894fc9bd-9kcz9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-28T19:25:18Z" message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.792474ms message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:14:18Z" - latency: 1.966635ms message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:13:18Z" - latency: 2.083553ms message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:12:18Z" - latency: 2.043604ms message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:11:18Z" - latency: 2.086784ms message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:10:18Z" - latency: 1.828854ms message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:09:18Z" - latency: 2.228719ms message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:08:18Z" - latency: 1.968344ms message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:07:18Z" - latency: 2.172976ms message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:06:18Z" - latency: 2.13374ms message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:05:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-28T19:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-network-check-target-ip-10-0-143-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.ec2.internal uid: f51402ca-b56d-4609-988a-2aa319bba9a5 resourceVersion: "58729" uid: b5eb804f-7275-4bf2-8b94-78b119be5e6f spec: sourcePod: network-check-source-8894fc9bd-9kcz9 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-28T19:25:18Z" message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.099634ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:14:18Z" - latency: 1.886122ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:13:18Z" - latency: 1.888653ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:12:18Z" - latency: 1.762171ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:11:18Z" - latency: 1.694119ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:10:18Z" - latency: 1.882029ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:09:18Z" - latency: 1.708511ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:08:18Z" - latency: 1.883806ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:07:18Z" - latency: 1.989349ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:06:18Z" - latency: 2.159125ms message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:05:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-28T19:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-121-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-121.ec2.internal uid: f51402ca-b56d-4609-988a-2aa319bba9a5 resourceVersion: "62385" uid: ac97878f-1365-4ee5-b5e2-629b5725b244 spec: sourcePod: network-check-source-8894fc9bd-9kcz9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-28T19:24:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 950.254µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:18:18Z" - latency: 1.83717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-28T20:18:18Z" - latency: 951.153µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:17:18Z" - latency: 2.042467ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-28T20:17:18Z" - latency: 830.425µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:16:18Z" - latency: 1.545651ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-28T20:16:18Z" - latency: 969.127µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:15:18Z" - latency: 1.877361ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-28T20:15:18Z" - latency: 842.539µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-28T20:14:18Z" - latency: 1.568792ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-28T20:14:18Z" kind: List metadata: resourceVersion: ""