apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e36ecd4e-434d-4a5d-80e3-7df147e494fc resourceVersion: "101759" uid: 81dcfb99-c3a1-41f3-bb13-5c567b85bf0a spec: sourcePod: network-check-source-7d88cb55d8-kz24q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T10:39:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.067407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:10:22Z" - latency: 1.067141ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:09:22Z" - latency: 1.116792ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:08:22Z" - latency: 992.735µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:07:22Z" - latency: 931.164µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:06:22Z" - latency: 1.064341ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:05:22Z" - latency: 1.459206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:04:22Z" - latency: 996.51µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:03:22Z" - latency: 1.666777ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:02:22Z" - latency: 844.23µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:01:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e36ecd4e-434d-4a5d-80e3-7df147e494fc resourceVersion: "100533" uid: 75731220-f552-4c3f-be01-649ede3da1c7 spec: sourcePod: network-check-source-7d88cb55d8-kz24q targetEndpoint: a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T10:38:22Z" message: 'load-balancer-api-external: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.454159ms message: 'load-balancer-api-external: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:08:22Z" - latency: 8.885213ms message: 'load-balancer-api-external: resolved host name a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T12:08:22Z" - latency: 4.269863ms message: 'load-balancer-api-external: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:07:22Z" - latency: 8.523491ms message: 'load-balancer-api-external: resolved host name a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T12:07:22Z" - latency: 4.47609ms message: 'load-balancer-api-external: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:06:22Z" - latency: 8.431188ms message: 'load-balancer-api-external: resolved host name a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T12:06:22Z" - latency: 4.693234ms message: 'load-balancer-api-external: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:05:22Z" - latency: 9.230519ms message: 'load-balancer-api-external: resolved host name a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T12:05:22Z" - latency: 4.241163ms message: 'load-balancer-api-external: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:04:22Z" - latency: 13.915545ms message: 'load-balancer-api-external: resolved host name a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T12:04:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e36ecd4e-434d-4a5d-80e3-7df147e494fc resourceVersion: "100532" uid: 689fec53-f4b6-40c3-ba42-929aeb7a3067 spec: sourcePod: network-check-source-7d88cb55d8-kz24q targetEndpoint: a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T10:38:22Z" message: 'load-balancer-api-internal: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.357718ms message: 'load-balancer-api-internal: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:08:22Z" - latency: 8.983887ms message: 'load-balancer-api-internal: resolved host name a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T12:08:22Z" - latency: 4.519622ms message: 'load-balancer-api-internal: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:07:22Z" - latency: 8.428722ms message: 'load-balancer-api-internal: resolved host name a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T12:07:22Z" - latency: 6.02137ms message: 'load-balancer-api-internal: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:06:22Z" - latency: 8.449508ms message: 'load-balancer-api-internal: resolved host name a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T12:06:22Z" - latency: 4.389755ms message: 'load-balancer-api-internal: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:05:22Z" - latency: 9.198397ms message: 'load-balancer-api-internal: resolved host name a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T12:05:22Z" - latency: 4.324078ms message: 'load-balancer-api-internal: tcp connection to a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:04:22Z" - latency: 14.031263ms message: 'load-balancer-api-internal: resolved host name a174c630cae34426492dbdbea3d47329-b34d48c7d6f8c17a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T12:04:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-network-check-target-ip-10-0-129-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e36ecd4e-434d-4a5d-80e3-7df147e494fc resourceVersion: "101756" uid: f415ade8-3335-4f8a-a5f1-dd1120f64aba spec: sourcePod: network-check-source-7d88cb55d8-kz24q targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T10:39:22Z" message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.273038ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:10:22Z" - latency: 2.175187ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:09:22Z" - latency: 2.229723ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:08:22Z" - latency: 1.96148ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:07:22Z" - latency: 2.084209ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:06:22Z" - latency: 2.271154ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:05:22Z" - latency: 2.370228ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:04:22Z" - latency: 2.163572ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:03:22Z" - latency: 3.156238ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:02:22Z" - latency: 2.24519ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:01:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-network-check-target-ip-10-0-133-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e36ecd4e-434d-4a5d-80e3-7df147e494fc resourceVersion: "101757" uid: 7bdce176-df4d-4abc-bf57-f1390b4f774f spec: sourcePod: network-check-source-7d88cb55d8-kz24q targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T10:39:22Z" message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.445798ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:10:22Z" - latency: 875.473µs message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:09:22Z" - latency: 894.291µs message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:08:22Z" - latency: 945.015µs message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:07:22Z" - latency: 861.47µs message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:06:22Z" - latency: 902.956µs message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:05:22Z" - latency: 1.95222ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:04:22Z" - latency: 1.129387ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:03:22Z" - latency: 2.936212ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:02:22Z" - latency: 917.139µs message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:01:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-network-check-target-ip-10-0-140-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e36ecd4e-434d-4a5d-80e3-7df147e494fc resourceVersion: "101758" uid: ff6c2846-cdff-44b9-8a04-0d5e23cbd70d spec: sourcePod: network-check-source-7d88cb55d8-kz24q targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T10:39:22Z" message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.308983ms message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:10:22Z" - latency: 2.157065ms message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:09:22Z" - latency: 2.018947ms message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:08:22Z" - latency: 1.986206ms message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:07:22Z" - latency: 2.066178ms message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:06:22Z" - latency: 2.177247ms message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:05:22Z" - latency: 2.115543ms message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:04:22Z" - latency: 2.371221ms message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:03:22Z" - latency: 3.017205ms message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:02:22Z" - latency: 1.953866ms message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:01:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-86-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-86.ec2.internal uid: e36ecd4e-434d-4a5d-80e3-7df147e494fc resourceVersion: "100531" uid: f6807438-812b-4d59-b25d-67ded33f66de spec: sourcePod: network-check-source-7d88cb55d8-kz24q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T10:38:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.289659ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:08:22Z" - latency: 1.946567ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T12:08:22Z" - latency: 934.36µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:07:22Z" - latency: 1.81229ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T12:07:22Z" - latency: 1.04825ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:06:22Z" - latency: 1.833464ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T12:06:22Z" - latency: 1.026854ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:05:22Z" - latency: 1.871283ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T12:05:22Z" - latency: 872.963µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T12:04:22Z" - latency: 2.148472ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T12:04:22Z" kind: List metadata: resourceVersion: ""