apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T01:22:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-145-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-145.us-east-2.compute.internal uid: c03818a7-e148-4087-8da2-5f670934eee1 resourceVersion: "172062" uid: c9d80cbf-9351-4e3a-b9f3-aa0324723adb spec: sourcePod: network-check-source-6f78d59f99-dgzjj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T01:29:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 912.391µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:18:35Z" - latency: 1.663077ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:17:35Z" - latency: 971.635µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:16:35Z" - latency: 1.551057ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:35Z" - latency: 1.662532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:35Z" - latency: 9.403775ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:35Z" - latency: 12.73752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:35Z" - latency: 2.245939ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:11:35Z" - latency: 1.634913ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:35Z" - latency: 3.057091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T01:22:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-145-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-145.us-east-2.compute.internal uid: c03818a7-e148-4087-8da2-5f670934eee1 resourceVersion: "163952" uid: 787dbc9a-732a-41d3-adbb-d3bc8527aefc spec: sourcePod: network-check-source-6f78d59f99-dgzjj targetEndpoint: ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T01:28:35Z" message: 'load-balancer-api-external: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.60796ms message: 'load-balancer-api-external: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:16:35Z" - latency: 9.315152ms message: 'load-balancer-api-external: resolved host name ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:16:35Z" - latency: 6.366621ms message: 'load-balancer-api-external: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:35Z" - latency: 7.363516ms message: 'load-balancer-api-external: resolved host name ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:15:35Z" - latency: 5.975246ms message: 'load-balancer-api-external: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:35Z" - latency: 7.736794ms message: 'load-balancer-api-external: resolved host name ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:14:35Z" - latency: 12.10375ms message: 'load-balancer-api-external: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:35Z" - latency: 57.439167ms message: 'load-balancer-api-external: resolved host name ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:13:35Z" - latency: 5.931761ms message: 'load-balancer-api-external: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:35Z" - latency: 21.926559ms message: 'load-balancer-api-external: resolved host name ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:12:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T01:22:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-145-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-145.us-east-2.compute.internal uid: c03818a7-e148-4087-8da2-5f670934eee1 resourceVersion: "163951" uid: 389dc3d5-9a88-4370-aad5-c56864cf9c0e spec: sourcePod: network-check-source-6f78d59f99-dgzjj targetEndpoint: ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T01:28:35Z" message: 'load-balancer-api-internal: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.647128ms message: 'load-balancer-api-internal: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:16:35Z" - latency: 9.280224ms message: 'load-balancer-api-internal: resolved host name ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:16:35Z" - latency: 6.235022ms message: 'load-balancer-api-internal: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:35Z" - latency: 7.341799ms message: 'load-balancer-api-internal: resolved host name ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:15:35Z" - latency: 6.015731ms message: 'load-balancer-api-internal: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:35Z" - latency: 7.605629ms message: 'load-balancer-api-internal: resolved host name ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:14:35Z" - latency: 10.547764ms message: 'load-balancer-api-internal: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:35Z" - latency: 57.117914ms message: 'load-balancer-api-internal: resolved host name ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:13:35Z" - latency: 6.500047ms message: 'load-balancer-api-internal: tcp connection to ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:35Z" - latency: 21.806371ms message: 'load-balancer-api-internal: resolved host name ad1e3fa6c9e6047848dc6376e2ea4e10-6cd3ffd6abfd966c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:12:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T01:22:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-145-to-network-check-target-ip-10-0-130-49 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-145.us-east-2.compute.internal uid: c03818a7-e148-4087-8da2-5f670934eee1 resourceVersion: "172060" uid: ca2a04d1-be22-4781-b18f-8a0f9095ac63 spec: sourcePod: network-check-source-6f78d59f99-dgzjj targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T01:29:35Z" message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.649752ms message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:18:35Z" - latency: 2.834803ms message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:17:35Z" - latency: 2.089953ms message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:16:35Z" - latency: 3.030588ms message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:35Z" - latency: 2.87668ms message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:35Z" - latency: 26.837661ms message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:35Z" - latency: 9.715103ms message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:35Z" - latency: 18.988546ms message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:11:35Z" - latency: 3.078621ms message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:35Z" - latency: 3.167426ms message: 'network-check-target-ip-10-0-130-49: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T01:22:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-145-to-network-check-target-ip-10-0-133-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-145.us-east-2.compute.internal uid: c03818a7-e148-4087-8da2-5f670934eee1 resourceVersion: "172061" uid: 98ceb07a-761b-46bc-a5fe-36c4341f3b07 spec: sourcePod: network-check-source-6f78d59f99-dgzjj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T01:29:35Z" message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.649277ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:18:35Z" - latency: 2.226902ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:17:35Z" - latency: 2.165797ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:16:35Z" - latency: 2.56175ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:35Z" - latency: 2.736965ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:35Z" - latency: 17.974531ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:35Z" - latency: 5.937516ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:35Z" - latency: 14.966144ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:11:35Z" - latency: 2.734819ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:35Z" - latency: 3.86066ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T01:22:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-145-to-network-check-target-ip-10-0-141-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-145.us-east-2.compute.internal uid: c03818a7-e148-4087-8da2-5f670934eee1 resourceVersion: "172059" uid: 57601124-36b7-474c-a319-302da577e2ca spec: sourcePod: network-check-source-6f78d59f99-dgzjj targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T01:29:35Z" message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.199369ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:18:35Z" - latency: 1.056363ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:17:35Z" - latency: 915.351µs message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:16:35Z" - latency: 1.068929ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:35Z" - latency: 1.688803ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:35Z" - latency: 26.340125ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:35Z" - latency: 13.756068ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:35Z" - latency: 15.120306ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:11:35Z" - latency: 1.171805ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:35Z" - latency: 989.741µs message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T01:22:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-145-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-145.us-east-2.compute.internal uid: c03818a7-e148-4087-8da2-5f670934eee1 resourceVersion: "163947" uid: 3a603bba-bdd4-4d62-af0f-07d1e53d87a5 spec: sourcePod: network-check-source-6f78d59f99-dgzjj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T01:28:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.943804ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:16:35Z" - latency: 2.211697ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T02:16:35Z" - latency: 1.127849ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:35Z" - latency: 2.442733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T02:15:35Z" - latency: 1.89152ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:35Z" - latency: 2.155775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T02:14:35Z" - latency: 4.875019ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:35Z" - latency: 26.963375ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T02:13:35Z" - latency: 1.318264ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:35Z" - latency: 16.394577ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T02:12:35Z" kind: List metadata: resourceVersion: ""