apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:43:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-119-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-119.ec2.internal uid: e8d22586-daa5-429c-a28a-fa45891ad504 resourceVersion: "89328" uid: c0ea5176-8e92-4d11-8684-2376507e3370 spec: sourcePod: network-check-source-6f8b768455-99t6g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T18:50:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.035924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:58Z" - latency: 1.27057ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:58Z" - latency: 1.210239ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:58Z" - latency: 1.189882ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:50:58Z" - latency: 946.696µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:49:58Z" - latency: 983.631µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:48:58Z" - latency: 1.045955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:47:58Z" - latency: 959.162µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:46:58Z" - latency: 903.405µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:45:58Z" - latency: 1.1241ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:44:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:43:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-119-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-119.ec2.internal uid: e8d22586-daa5-429c-a28a-fa45891ad504 resourceVersion: "91219" uid: 573c4143-41ef-4034-becb-ff8cdc3403d3 spec: sourcePod: network-check-source-6f8b768455-99t6g targetEndpoint: a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T18:49:58Z" message: 'load-balancer-api-external: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.540376ms message: 'load-balancer-api-external: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:55:58Z" - latency: 6.43909ms message: 'load-balancer-api-external: resolved host name a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:55:58Z" - latency: 5.551807ms message: 'load-balancer-api-external: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:54:58Z" - latency: 7.014285ms message: 'load-balancer-api-external: resolved host name a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:54:58Z" - latency: 5.574752ms message: 'load-balancer-api-external: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:58Z" - latency: 7.440584ms message: 'load-balancer-api-external: resolved host name a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:53:58Z" - latency: 4.854689ms message: 'load-balancer-api-external: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:58Z" - latency: 6.887896ms message: 'load-balancer-api-external: resolved host name a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:52:58Z" - latency: 5.52631ms message: 'load-balancer-api-external: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:58Z" - latency: 7.325042ms message: 'load-balancer-api-external: resolved host name a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:51:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:43:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-119-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-119.ec2.internal uid: e8d22586-daa5-429c-a28a-fa45891ad504 resourceVersion: "91218" uid: 6e95f484-4295-44f8-87fb-f82e82d27324 spec: sourcePod: network-check-source-6f8b768455-99t6g targetEndpoint: a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T18:49:58Z" message: 'load-balancer-api-internal: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.250153ms message: 'load-balancer-api-internal: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:55:58Z" - latency: 6.47606ms message: 'load-balancer-api-internal: resolved host name a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:55:58Z" - latency: 5.586576ms message: 'load-balancer-api-internal: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:54:58Z" - latency: 7.072842ms message: 'load-balancer-api-internal: resolved host name a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:54:58Z" - latency: 5.613729ms message: 'load-balancer-api-internal: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:58Z" - latency: 7.354257ms message: 'load-balancer-api-internal: resolved host name a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:53:58Z" - latency: 4.865442ms message: 'load-balancer-api-internal: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:58Z" - latency: 6.900626ms message: 'load-balancer-api-internal: resolved host name a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:52:58Z" - latency: 5.538868ms message: 'load-balancer-api-internal: tcp connection to a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:58Z" - latency: 7.35516ms message: 'load-balancer-api-internal: resolved host name a23add5f4200d4bf99670287e1374dbf-c9d478d90f7df5d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:51:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:43:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-119-to-network-check-target-ip-10-0-128-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-119.ec2.internal uid: e8d22586-daa5-429c-a28a-fa45891ad504 resourceVersion: "89326" uid: fdef7e0f-e131-423f-9d10-921a230375db spec: sourcePod: network-check-source-6f8b768455-99t6g targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:50:58Z" message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.524613ms message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:58Z" - latency: 2.456684ms message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:58Z" - latency: 2.726535ms message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:58Z" - latency: 2.467756ms message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:50:58Z" - latency: 2.217047ms message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:49:58Z" - latency: 2.676858ms message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:48:58Z" - latency: 2.228813ms message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:47:58Z" - latency: 2.126433ms message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:46:58Z" - latency: 2.113022ms message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:45:58Z" - latency: 2.520026ms message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:44:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:43:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-119-to-network-check-target-ip-10-0-135-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-119.ec2.internal uid: e8d22586-daa5-429c-a28a-fa45891ad504 resourceVersion: "89325" uid: ad36df70-2346-410a-98b4-bedc91ed7823 spec: sourcePod: network-check-source-6f8b768455-99t6g targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:50:58Z" message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 912.135µs message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:58Z" - latency: 951.986µs message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:58Z" - latency: 1.081712ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:58Z" - latency: 896.887µs message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:50:58Z" - latency: 1.404452ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:49:58Z" - latency: 966.625µs message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:48:58Z" - latency: 1.418626ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:47:58Z" - latency: 1.169856ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:46:58Z" - latency: 1.000232ms message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:45:58Z" - latency: 943.87µs message: 'network-check-target-ip-10-0-135-119: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:44:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:43:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-119-to-network-check-target-ip-10-0-142-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-119.ec2.internal uid: e8d22586-daa5-429c-a28a-fa45891ad504 resourceVersion: "89327" uid: 52432f0e-88e6-4dec-823a-1d4d9306f65b spec: sourcePod: network-check-source-6f8b768455-99t6g targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:50:58Z" message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.524282ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:58Z" - latency: 2.50257ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:58Z" - latency: 2.140974ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:58Z" - latency: 2.482039ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:50:58Z" - latency: 2.29137ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:49:58Z" - latency: 2.486271ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:48:58Z" - latency: 2.124619ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:47:58Z" - latency: 2.370083ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:46:58Z" - latency: 2.250206ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:45:58Z" - latency: 2.573171ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:44:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:43:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-119-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-119.ec2.internal uid: e8d22586-daa5-429c-a28a-fa45891ad504 resourceVersion: "91217" uid: 18dce75e-6d48-406e-b52f-43787e0f97c4 spec: sourcePod: network-check-source-6f8b768455-99t6g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T18:49:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 807.711µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:55:58Z" - latency: 1.700407ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:55:58Z" - latency: 861.808µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:54:58Z" - latency: 1.728568ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:54:58Z" - latency: 783.621µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:58Z" - latency: 1.892385ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:53:58Z" - latency: 993.438µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:58Z" - latency: 1.832422ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:52:58Z" - latency: 1.172956ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:58Z" - latency: 1.701908ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:51:58Z" kind: List metadata: resourceVersion: ""