apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 6094f7fc-72c2-42d4-96c1-f1944f7cb335 resourceVersion: "18204" uid: 085d1281-eb57-48d1-8eeb-9db9a37dbd5c spec: sourcePod: network-check-source-7f44b6dd87-dgg47 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T16:11:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.039198ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:18:06Z" - latency: 1.053026ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:17:06Z" - latency: 787.953µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:16:06Z" - latency: 1.019366ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:15:06Z" - latency: 935.492µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:14:06Z" - latency: 943.754µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:13:06Z" - latency: 867.718µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:12:06Z" - latency: 1.219407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:11:06Z" - latency: 1.183695ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:10:06Z" - latency: 903.193µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:09:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 6094f7fc-72c2-42d4-96c1-f1944f7cb335 resourceVersion: "20289" uid: 10434385-76a0-4a7a-a656-00f26d22f419 spec: sourcePod: network-check-source-7f44b6dd87-dgg47 targetEndpoint: a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T16:10:06Z" message: 'load-balancer-api-external: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.688861ms message: 'load-balancer-api-external: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:22:06Z" - latency: 10.687621ms message: 'load-balancer-api-external: resolved host name a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:22:06Z" - latency: 4.816993ms message: 'load-balancer-api-external: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:21:06Z" - latency: 9.285621ms message: 'load-balancer-api-external: resolved host name a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:21:06Z" - latency: 4.465481ms message: 'load-balancer-api-external: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:20:06Z" - latency: 8.741262ms message: 'load-balancer-api-external: resolved host name a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:20:06Z" - latency: 5.402909ms message: 'load-balancer-api-external: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:19:06Z" - latency: 9.790058ms message: 'load-balancer-api-external: resolved host name a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:19:06Z" - latency: 5.970442ms message: 'load-balancer-api-external: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:18:06Z" - latency: 8.188553ms message: 'load-balancer-api-external: resolved host name a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:18:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 6094f7fc-72c2-42d4-96c1-f1944f7cb335 resourceVersion: "20290" uid: a05762d8-7f79-4d7b-bf4c-06a617a47ecc spec: sourcePod: network-check-source-7f44b6dd87-dgg47 targetEndpoint: a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T16:10:06Z" message: 'load-balancer-api-internal: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.777882ms message: 'load-balancer-api-internal: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:22:06Z" - latency: 10.737911ms message: 'load-balancer-api-internal: resolved host name a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:22:06Z" - latency: 4.928064ms message: 'load-balancer-api-internal: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:21:06Z" - latency: 9.356877ms message: 'load-balancer-api-internal: resolved host name a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:21:06Z" - latency: 4.454836ms message: 'load-balancer-api-internal: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:20:06Z" - latency: 8.765634ms message: 'load-balancer-api-internal: resolved host name a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:20:06Z" - latency: 5.458279ms message: 'load-balancer-api-internal: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:19:06Z" - latency: 9.842712ms message: 'load-balancer-api-internal: resolved host name a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:19:06Z" - latency: 5.902618ms message: 'load-balancer-api-internal: tcp connection to a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:18:06Z" - latency: 8.214401ms message: 'load-balancer-api-internal: resolved host name a97ea45f572df4bea8a75da64fb2e1f4-db5333036e93f844.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:18:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-ip-10-0-134-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 6094f7fc-72c2-42d4-96c1-f1944f7cb335 resourceVersion: "18202" uid: ad212a81-bc14-4e57-bcbf-0cb664b7b313 spec: sourcePod: network-check-source-7f44b6dd87-dgg47 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T16:11:06Z" message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.984775ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:18:06Z" - latency: 2.209307ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:17:06Z" - latency: 1.989533ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:16:06Z" - latency: 2.117237ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:15:06Z" - latency: 2.149064ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:14:06Z" - latency: 1.811337ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:13:06Z" - latency: 2.0049ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:12:06Z" - latency: 2.244745ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:11:06Z" - latency: 2.003898ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:10:06Z" - latency: 2.150268ms message: 'network-check-target-ip-10-0-134-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:09:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-ip-10-0-137-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 6094f7fc-72c2-42d4-96c1-f1944f7cb335 resourceVersion: "18203" uid: d30ff90b-ac39-4919-9ff4-e3912e563ad7 spec: sourcePod: network-check-source-7f44b6dd87-dgg47 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T16:11:06Z" message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.903034ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:18:06Z" - latency: 1.963737ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:17:06Z" - latency: 1.916769ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:16:06Z" - latency: 1.902925ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:15:06Z" - latency: 1.847915ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:14:06Z" - latency: 1.727593ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:13:06Z" - latency: 1.774588ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:12:06Z" - latency: 1.851782ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:11:06Z" - latency: 1.81626ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:10:06Z" - latency: 1.909566ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:09:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-ip-10-0-141-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 6094f7fc-72c2-42d4-96c1-f1944f7cb335 resourceVersion: "18201" uid: a14b330a-bc66-4321-884d-deca2e3f76e3 spec: sourcePod: network-check-source-7f44b6dd87-dgg47 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T16:11:06Z" message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 841.538µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:18:06Z" - latency: 828.965µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:17:06Z" - latency: 736.97µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:16:06Z" - latency: 770.741µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:15:06Z" - latency: 893.102µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:14:06Z" - latency: 817.434µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:13:06Z" - latency: 1.271616ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:12:06Z" - latency: 1.046407ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:11:06Z" - latency: 760.553µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:10:06Z" - latency: 1.122135ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:09:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:04:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 6094f7fc-72c2-42d4-96c1-f1944f7cb335 resourceVersion: "20288" uid: 78902194-8d0b-4f4e-bb6b-fd46fb0ebe9f spec: sourcePod: network-check-source-7f44b6dd87-dgg47 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T16:10:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.384µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:22:06Z" - latency: 1.732063ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:22:06Z" - latency: 780.242µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:21:06Z" - latency: 1.722646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:21:06Z" - latency: 779.559µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:20:06Z" - latency: 1.749893ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:20:06Z" - latency: 969.302µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:19:06Z" - latency: 1.879205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:19:06Z" - latency: 1.289263ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:18:06Z" - latency: 1.645096ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:18:06Z" kind: List metadata: resourceVersion: ""