apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:19:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-79-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-79.ec2.internal uid: 45cd8ac6-c24a-47d8-8896-8d0620ed00a6 resourceVersion: "47507" uid: 916bf0af-6f79-4e97-a9d2-e0053eb3a6fa spec: sourcePod: network-check-source-7bc5b6bf85-gt7rm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T21:26:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006146ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:47:36Z" - latency: 1.235466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:46:36Z" - latency: 976.272µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:45:36Z" - latency: 1.131167ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:44:36Z" - latency: 859.371µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:43:36Z" - latency: 1.013816ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:42:36Z" - latency: 835.504µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:41:36Z" - latency: 1.230465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:40:36Z" - latency: 868.621µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:39:36Z" - latency: 1.16019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:38:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:19:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-79-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-79.ec2.internal uid: 45cd8ac6-c24a-47d8-8896-8d0620ed00a6 resourceVersion: "49051" uid: 39a35593-90f9-4529-be38-a309c3d552ae spec: sourcePod: network-check-source-7bc5b6bf85-gt7rm targetEndpoint: a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T21:25:36Z" message: 'load-balancer-api-external: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.589275ms message: 'load-balancer-api-external: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:49:36Z" - latency: 7.473958ms message: 'load-balancer-api-external: resolved host name a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T21:49:36Z" - latency: 5.728121ms message: 'load-balancer-api-external: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:48:36Z" - latency: 10.102891ms message: 'load-balancer-api-external: resolved host name a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T21:48:36Z" - latency: 4.208514ms message: 'load-balancer-api-external: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:47:36Z" - latency: 7.741629ms message: 'load-balancer-api-external: resolved host name a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T21:47:36Z" - latency: 4.403692ms message: 'load-balancer-api-external: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:46:36Z" - latency: 6.811291ms message: 'load-balancer-api-external: resolved host name a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T21:46:36Z" - latency: 4.598225ms message: 'load-balancer-api-external: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:45:36Z" - latency: 7.453805ms message: 'load-balancer-api-external: resolved host name a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T21:45:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:19:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-79-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-79.ec2.internal uid: 45cd8ac6-c24a-47d8-8896-8d0620ed00a6 resourceVersion: "49050" uid: 954402e8-f978-4f6d-b723-a1fd8661cc65 spec: sourcePod: network-check-source-7bc5b6bf85-gt7rm targetEndpoint: a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T21:25:36Z" message: 'load-balancer-api-internal: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.572749ms message: 'load-balancer-api-internal: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:49:36Z" - latency: 7.518284ms message: 'load-balancer-api-internal: resolved host name a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T21:49:36Z" - latency: 5.767561ms message: 'load-balancer-api-internal: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:48:36Z" - latency: 10.06968ms message: 'load-balancer-api-internal: resolved host name a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T21:48:36Z" - latency: 4.184378ms message: 'load-balancer-api-internal: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:47:36Z" - latency: 7.816887ms message: 'load-balancer-api-internal: resolved host name a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T21:47:36Z" - latency: 4.396477ms message: 'load-balancer-api-internal: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:46:36Z" - latency: 6.872985ms message: 'load-balancer-api-internal: resolved host name a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T21:46:36Z" - latency: 5.330087ms message: 'load-balancer-api-internal: tcp connection to a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:45:36Z" - latency: 7.497008ms message: 'load-balancer-api-internal: resolved host name a26983e052ce5406f8efeb0eae5b85ab-dc2e98ed96445831.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T21:45:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:19:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-79-to-network-check-target-ip-10-0-133-67 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-79.ec2.internal uid: 45cd8ac6-c24a-47d8-8896-8d0620ed00a6 resourceVersion: "47505" uid: 391f9e0d-4ab2-4e56-bbdf-f5062f9d2196 spec: sourcePod: network-check-source-7bc5b6bf85-gt7rm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T21:26:36Z" message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.041975ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:47:36Z" - latency: 2.211126ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:46:36Z" - latency: 2.332867ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:45:36Z" - latency: 2.304735ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:44:36Z" - latency: 2.221544ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:43:36Z" - latency: 2.307059ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:42:36Z" - latency: 2.114054ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:41:36Z" - latency: 2.084034ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:40:36Z" - latency: 2.488225ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:39:36Z" - latency: 2.048474ms message: 'network-check-target-ip-10-0-133-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:38:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:19:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-79-to-network-check-target-ip-10-0-138-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-79.ec2.internal uid: 45cd8ac6-c24a-47d8-8896-8d0620ed00a6 resourceVersion: "47506" uid: 4d182934-0ddf-4291-9358-62ac96700874 spec: sourcePod: network-check-source-7bc5b6bf85-gt7rm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T21:26:36Z" message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.278838ms message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:47:36Z" - latency: 2.098544ms message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:46:36Z" - latency: 1.963142ms message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:45:36Z" - latency: 2.017792ms message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:44:36Z" - latency: 1.971513ms message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:43:36Z" - latency: 2.044164ms message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:42:36Z" - latency: 2.101531ms message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:41:36Z" - latency: 2.117292ms message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:40:36Z" - latency: 1.903425ms message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:39:36Z" - latency: 1.901469ms message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:38:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:19:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-79-to-network-check-target-ip-10-0-141-79 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-79.ec2.internal uid: 45cd8ac6-c24a-47d8-8896-8d0620ed00a6 resourceVersion: "47504" uid: 9db89769-7da7-4cc3-83b1-f00c3dc52cf6 spec: sourcePod: network-check-source-7bc5b6bf85-gt7rm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T21:26:36Z" message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 882.889µs message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:47:36Z" - latency: 833.315µs message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:46:36Z" - latency: 982.326µs message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:45:36Z" - latency: 1.483617ms message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:44:36Z" - latency: 1.571662ms message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:43:36Z" - latency: 1.025254ms message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:42:36Z" - latency: 1.072977ms message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:41:36Z" - latency: 1.158606ms message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:40:36Z" - latency: 806.537µs message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:39:36Z" - latency: 1.007666ms message: 'network-check-target-ip-10-0-141-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:38:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:19:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-79-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-79.ec2.internal uid: 45cd8ac6-c24a-47d8-8896-8d0620ed00a6 resourceVersion: "49048" uid: 37d67d61-d18e-4f01-8d3d-1d63610a6c4a spec: sourcePod: network-check-source-7bc5b6bf85-gt7rm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T21:25:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 995.595µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:49:36Z" - latency: 1.829969ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T21:49:36Z" - latency: 1.118628ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:48:36Z" - latency: 1.871948ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T21:48:36Z" - latency: 930.349µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:47:36Z" - latency: 1.904946ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T21:47:36Z" - latency: 912.85µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:46:36Z" - latency: 1.736235ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T21:46:36Z" - latency: 874.795µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:45:36Z" - latency: 1.922317ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T21:45:36Z" kind: List metadata: resourceVersion: ""