apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T21:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-18-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-18.ec2.internal uid: ea27412d-87b7-4f55-9413-0fa1a0f3c20e resourceVersion: "44067" uid: 92d04e8e-cef2-4954-bf39-7d8949011c79 spec: sourcePod: network-check-source-7f44b6dd87-pkhng targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T21:56:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.053953ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:17:23Z" - latency: 989.698µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:16:23Z" - latency: 1.095144ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:15:23Z" - latency: 854.585µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:14:23Z" - latency: 1.038841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:13:23Z" - latency: 893.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:12:23Z" - latency: 925.137µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:11:23Z" - latency: 814.894µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:10:23Z" - latency: 894.282µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:09:23Z" - latency: 746.266µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T21:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-18-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-18.ec2.internal uid: ea27412d-87b7-4f55-9413-0fa1a0f3c20e resourceVersion: "46353" uid: f1b14651-9844-4ec1-9e24-955c406c2e52 spec: sourcePod: network-check-source-7f44b6dd87-pkhng targetEndpoint: a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T21:55:23Z" message: 'load-balancer-api-external: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.346238ms message: 'load-balancer-api-external: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:19:23Z" - latency: 10.28045ms message: 'load-balancer-api-external: resolved host name a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T22:19:23Z" - latency: 5.846165ms message: 'load-balancer-api-external: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:18:23Z" - latency: 8.857645ms message: 'load-balancer-api-external: resolved host name a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T22:18:23Z" - latency: 5.191749ms message: 'load-balancer-api-external: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:17:23Z" - latency: 7.376178ms message: 'load-balancer-api-external: resolved host name a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T22:17:23Z" - latency: 4.726411ms message: 'load-balancer-api-external: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:16:23Z" - latency: 8.292811ms message: 'load-balancer-api-external: resolved host name a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T22:16:23Z" - latency: 5.106065ms message: 'load-balancer-api-external: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:15:23Z" - latency: 8.021364ms message: 'load-balancer-api-external: resolved host name a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T22:15:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T21:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-18-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-18.ec2.internal uid: ea27412d-87b7-4f55-9413-0fa1a0f3c20e resourceVersion: "46354" uid: fa73dc25-7b2b-4a0c-a199-9d457bbf60fa spec: sourcePod: network-check-source-7f44b6dd87-pkhng targetEndpoint: a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T21:55:23Z" message: 'load-balancer-api-internal: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.400372ms message: 'load-balancer-api-internal: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:19:23Z" - latency: 10.396728ms message: 'load-balancer-api-internal: resolved host name a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T22:19:23Z" - latency: 5.809313ms message: 'load-balancer-api-internal: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:18:23Z" - latency: 8.946023ms message: 'load-balancer-api-internal: resolved host name a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T22:18:23Z" - latency: 5.291606ms message: 'load-balancer-api-internal: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:17:23Z" - latency: 7.420953ms message: 'load-balancer-api-internal: resolved host name a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T22:17:23Z" - latency: 4.569418ms message: 'load-balancer-api-internal: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:16:23Z" - latency: 8.407368ms message: 'load-balancer-api-internal: resolved host name a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T22:16:23Z" - latency: 5.058014ms message: 'load-balancer-api-internal: tcp connection to a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:15:23Z" - latency: 8.0913ms message: 'load-balancer-api-internal: resolved host name a74b4723d15e9403b9c7fce039a33924-b91efa4ef671771f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T22:15:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T21:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-18-to-network-check-target-ip-10-0-128-18 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-18.ec2.internal uid: ea27412d-87b7-4f55-9413-0fa1a0f3c20e resourceVersion: "44064" uid: d02ab301-1c49-4ed5-8855-f378d6750362 spec: sourcePod: network-check-source-7f44b6dd87-pkhng targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T21:56:23Z" message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.109044ms message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:17:23Z" - latency: 793.006µs message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:16:23Z" - latency: 1.006669ms message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:15:23Z" - latency: 1.091496ms message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:14:23Z" - latency: 892.412µs message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:13:23Z" - latency: 866.659µs message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:12:23Z" - latency: 1.372017ms message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:11:23Z" - latency: 1.351431ms message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:10:23Z" - latency: 871.335µs message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:09:23Z" - latency: 984.188µs message: 'network-check-target-ip-10-0-128-18: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T21:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-18-to-network-check-target-ip-10-0-138-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-18.ec2.internal uid: ea27412d-87b7-4f55-9413-0fa1a0f3c20e resourceVersion: "44066" uid: a62e98d0-1da2-4e3e-90b1-a1e2b6d4f349 spec: sourcePod: network-check-source-7f44b6dd87-pkhng targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T21:56:23Z" message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.018549ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:17:23Z" - latency: 1.867214ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:16:23Z" - latency: 1.990637ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:15:23Z" - latency: 1.890544ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:14:23Z" - latency: 1.876151ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:13:23Z" - latency: 1.910052ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:12:23Z" - latency: 2.006696ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:11:23Z" - latency: 2.397211ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:10:23Z" - latency: 1.836512ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:09:23Z" - latency: 1.766893ms message: 'network-check-target-ip-10-0-138-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T21:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-18-to-network-check-target-ip-10-0-140-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-18.ec2.internal uid: ea27412d-87b7-4f55-9413-0fa1a0f3c20e resourceVersion: "44065" uid: 78a49b0b-c11c-4eb0-814c-a262d9176a06 spec: sourcePod: network-check-source-7f44b6dd87-pkhng targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T21:56:23Z" message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.039519ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:17:23Z" - latency: 2.145134ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:16:23Z" - latency: 2.300368ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:15:23Z" - latency: 1.478268ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:14:23Z" - latency: 2.099202ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:13:23Z" - latency: 2.076904ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:12:23Z" - latency: 2.06012ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:11:23Z" - latency: 1.931558ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:10:23Z" - latency: 1.857426ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:09:23Z" - latency: 2.174488ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T21:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-18-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-18.ec2.internal uid: ea27412d-87b7-4f55-9413-0fa1a0f3c20e resourceVersion: "46352" uid: e2514943-f4d0-4d27-b823-6f2d1412ff36 spec: sourcePod: network-check-source-7f44b6dd87-pkhng targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T21:55:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 828.566µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:19:23Z" - latency: 2.416165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T22:19:23Z" - latency: 834.58µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:18:23Z" - latency: 1.936049ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T22:18:23Z" - latency: 918.238µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:17:23Z" - latency: 2.008462ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T22:17:23Z" - latency: 938.945µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:16:23Z" - latency: 2.139551ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T22:16:23Z" - latency: 896.354µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T22:15:23Z" - latency: 1.810216ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T22:15:23Z" kind: List metadata: resourceVersion: ""