apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:25:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-192-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-192.ec2.internal uid: 1b51152a-5d14-4c8b-905f-3015cc65c2a0 resourceVersion: "55872" uid: f959afaa-2acd-43e4-9a13-c4cbd97c62e8 spec: sourcePod: network-check-source-869dcfcdcd-ksvnx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T02:32:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.196212ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:00:53Z" - latency: 707.723µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:59:53Z" - latency: 1.359048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:58:53Z" - latency: 986.142µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:57:53Z" - latency: 1.046378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:56:53Z" - latency: 955.269µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:55:53Z" - latency: 1.343707ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:54:53Z" - latency: 872.036µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:53:53Z" - latency: 2.650086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:53Z" - latency: 1.273562ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:25:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-192-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-192.ec2.internal uid: 1b51152a-5d14-4c8b-905f-3015cc65c2a0 resourceVersion: "50745" uid: 68b48eec-6ff1-4491-aa13-1797a0be0c0f spec: sourcePod: network-check-source-869dcfcdcd-ksvnx targetEndpoint: af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T02:31:53Z" message: 'load-balancer-api-external: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.902232ms message: 'load-balancer-api-external: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:55:53Z" - latency: 6.209674ms message: 'load-balancer-api-external: resolved host name af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:55:53Z" - latency: 5.320876ms message: 'load-balancer-api-external: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:54:53Z" - latency: 7.156475ms message: 'load-balancer-api-external: resolved host name af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:54:53Z" - latency: 4.468117ms message: 'load-balancer-api-external: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:53:53Z" - latency: 8.836406ms message: 'load-balancer-api-external: resolved host name af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:53:53Z" - latency: 3.673036ms message: 'load-balancer-api-external: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:53Z" - latency: 18.859084ms message: 'load-balancer-api-external: resolved host name af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:52:53Z" - latency: 3.3105ms message: 'load-balancer-api-external: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:53Z" - latency: 6.628828ms message: 'load-balancer-api-external: resolved host name af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:51:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:25:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-192-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-192.ec2.internal uid: 1b51152a-5d14-4c8b-905f-3015cc65c2a0 resourceVersion: "50744" uid: a8b06d2b-eef9-49b8-a3e3-8e8823da222f spec: sourcePod: network-check-source-869dcfcdcd-ksvnx targetEndpoint: af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T02:31:53Z" message: 'load-balancer-api-internal: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.882487ms message: 'load-balancer-api-internal: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:55:53Z" - latency: 6.266632ms message: 'load-balancer-api-internal: resolved host name af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:55:53Z" - latency: 5.263854ms message: 'load-balancer-api-internal: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:54:53Z" - latency: 7.194132ms message: 'load-balancer-api-internal: resolved host name af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:54:53Z" - latency: 3.700116ms message: 'load-balancer-api-internal: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:53:53Z" - latency: 8.871268ms message: 'load-balancer-api-internal: resolved host name af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:53:53Z" - latency: 3.639161ms message: 'load-balancer-api-internal: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:53Z" - latency: 16.84196ms message: 'load-balancer-api-internal: resolved host name af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:52:53Z" - latency: 3.281261ms message: 'load-balancer-api-internal: tcp connection to af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:53Z" - latency: 6.673878ms message: 'load-balancer-api-internal: resolved host name af3c4259be5984dc3b355f89efdda0c5-4eac27ba12f008f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T02:51:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:25:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-192-to-network-check-target-ip-10-0-128-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-192.ec2.internal uid: 1b51152a-5d14-4c8b-905f-3015cc65c2a0 resourceVersion: "55870" uid: 66e32f78-0e50-4640-ac6e-f2f28e92a49a spec: sourcePod: network-check-source-869dcfcdcd-ksvnx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:32:53Z" message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.312307ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:00:53Z" - latency: 1.855678ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:59:53Z" - latency: 2.171399ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:58:53Z" - latency: 2.12924ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:57:53Z" - latency: 2.281961ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:56:53Z" - latency: 2.293715ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:55:53Z" - latency: 2.339289ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:54:53Z" - latency: 2.1647ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:53:53Z" - latency: 3.023048ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:53Z" - latency: 2.007105ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:25:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-192-to-network-check-target-ip-10-0-130-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-192.ec2.internal uid: 1b51152a-5d14-4c8b-905f-3015cc65c2a0 resourceVersion: "55871" uid: 4a009cd9-bb16-4fdf-a44a-c187bdb23f73 spec: sourcePod: network-check-source-869dcfcdcd-ksvnx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:32:53Z" message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.277828ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:00:53Z" - latency: 1.789423ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:59:53Z" - latency: 1.655728ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:58:53Z" - latency: 1.742469ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:57:53Z" - latency: 2.062813ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:56:53Z" - latency: 2.006884ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:55:53Z" - latency: 1.895953ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:54:53Z" - latency: 2.069319ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:53:53Z" - latency: 5.432147ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:53Z" - latency: 2.502964ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:25:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-192-to-network-check-target-ip-10-0-133-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-192.ec2.internal uid: 1b51152a-5d14-4c8b-905f-3015cc65c2a0 resourceVersion: "55869" uid: 93dbae9c-2ce4-4745-8133-c5f812ef8c1e spec: sourcePod: network-check-source-869dcfcdcd-ksvnx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:32:53Z" message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.123983ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:00:53Z" - latency: 1.147818ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:59:53Z" - latency: 681.895µs message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:58:53Z" - latency: 779.764µs message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:57:53Z" - latency: 874.008µs message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:56:53Z" - latency: 1.174707ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:55:53Z" - latency: 949.407µs message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:54:53Z" - latency: 853.568µs message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:53:53Z" - latency: 976.04µs message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:53Z" - latency: 1.241734ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:25:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-192-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-192.ec2.internal uid: 1b51152a-5d14-4c8b-905f-3015cc65c2a0 resourceVersion: "50743" uid: dd76dbc6-b198-4d3e-9969-3f20f69fb420 spec: sourcePod: network-check-source-869dcfcdcd-ksvnx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T02:31:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 781.954µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:55:53Z" - latency: 1.817263ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T02:55:53Z" - latency: 773.774µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:54:53Z" - latency: 1.815022ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T02:54:53Z" - latency: 891.341µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:53:53Z" - latency: 1.686143ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T02:53:53Z" - latency: 2.379959ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:52:53Z" - latency: 4.951291ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T02:52:53Z" - latency: 782.607µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T02:51:53Z" - latency: 2.067354ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T02:51:53Z" kind: List metadata: resourceVersion: ""