apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:11:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-69-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-69.ec2.internal uid: 80c69e43-2300-4698-b3e4-58378c46a3bd resourceVersion: "43978" uid: 4f9abf6e-73a5-4070-8bae-5654ea1d247f spec: sourcePod: network-check-source-7f44b6dd87-xzqnw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T18:18:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 860.409µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:30Z" - latency: 1.107865ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:30Z" - latency: 1.300198ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:37:30Z" - latency: 962.056µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:36:30Z" - latency: 1.261125ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:35:30Z" - latency: 1.16269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:34:30Z" - latency: 817.073µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:33:30Z" - latency: 1.295676ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:32:30Z" - latency: 1.194597ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:31:30Z" - latency: 1.049033ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:30:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:11:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-69-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-69.ec2.internal uid: 80c69e43-2300-4698-b3e4-58378c46a3bd resourceVersion: "45982" uid: 8f87287a-e7cd-496b-9264-498326812038 spec: sourcePod: network-check-source-7f44b6dd87-xzqnw targetEndpoint: a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T18:17:30Z" message: 'load-balancer-api-external: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.829099ms message: 'load-balancer-api-external: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:41:30Z" - latency: 7.621962ms message: 'load-balancer-api-external: resolved host name a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:41:30Z" - latency: 5.402012ms message: 'load-balancer-api-external: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:40:30Z" - latency: 6.839853ms message: 'load-balancer-api-external: resolved host name a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:40:30Z" - latency: 5.046219ms message: 'load-balancer-api-external: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:30Z" - latency: 8.797293ms message: 'load-balancer-api-external: resolved host name a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:39:30Z" - latency: 3.59824ms message: 'load-balancer-api-external: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:30Z" - latency: 11.795802ms message: 'load-balancer-api-external: resolved host name a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:38:30Z" - latency: 4.809439ms message: 'load-balancer-api-external: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:37:30Z" - latency: 7.950547ms message: 'load-balancer-api-external: resolved host name a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:37:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:11:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-69-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-69.ec2.internal uid: 80c69e43-2300-4698-b3e4-58378c46a3bd resourceVersion: "45983" uid: dea04086-38d4-46d0-8b4d-8a33cebf8b48 spec: sourcePod: network-check-source-7f44b6dd87-xzqnw targetEndpoint: a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T18:17:30Z" message: 'load-balancer-api-internal: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.870251ms message: 'load-balancer-api-internal: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:41:30Z" - latency: 7.592592ms message: 'load-balancer-api-internal: resolved host name a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:41:30Z" - latency: 5.385929ms message: 'load-balancer-api-internal: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:40:30Z" - latency: 6.816758ms message: 'load-balancer-api-internal: resolved host name a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:40:30Z" - latency: 3.925784ms message: 'load-balancer-api-internal: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:30Z" - latency: 8.740426ms message: 'load-balancer-api-internal: resolved host name a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:39:30Z" - latency: 3.641517ms message: 'load-balancer-api-internal: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:30Z" - latency: 11.766176ms message: 'load-balancer-api-internal: resolved host name a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:38:30Z" - latency: 4.817603ms message: 'load-balancer-api-internal: tcp connection to a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:37:30Z" - latency: 7.908634ms message: 'load-balancer-api-internal: resolved host name a1c1b4c04762f4c0691d36b88c020a40-dbe9f43e9d793608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:37:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:11:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-69-to-network-check-target-ip-10-0-133-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-69.ec2.internal uid: 80c69e43-2300-4698-b3e4-58378c46a3bd resourceVersion: "43976" uid: 9f59cbef-0291-4994-8cf0-41797b186a98 spec: sourcePod: network-check-source-7f44b6dd87-xzqnw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:18:30Z" message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.285163ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:30Z" - latency: 2.036303ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:30Z" - latency: 2.123891ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:37:30Z" - latency: 2.239617ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:36:30Z" - latency: 2.354601ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:35:30Z" - latency: 2.19622ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:34:30Z" - latency: 2.25701ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:33:30Z" - latency: 2.212865ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:32:30Z" - latency: 2.352558ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:31:30Z" - latency: 2.197735ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:30:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:11:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-69-to-network-check-target-ip-10-0-133-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-69.ec2.internal uid: 80c69e43-2300-4698-b3e4-58378c46a3bd resourceVersion: "43977" uid: 13654253-712a-4d8e-96b6-ef832718b1f5 spec: sourcePod: network-check-source-7f44b6dd87-xzqnw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:18:30Z" message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.18186ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:30Z" - latency: 2.371819ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:30Z" - latency: 1.94062ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:37:30Z" - latency: 2.670582ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:36:30Z" - latency: 2.400345ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:35:30Z" - latency: 2.122115ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:34:30Z" - latency: 1.790957ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:33:30Z" - latency: 2.244019ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:32:30Z" - latency: 2.123368ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:31:30Z" - latency: 2.377312ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:30:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:11:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-69-to-network-check-target-ip-10-0-143-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-69.ec2.internal uid: 80c69e43-2300-4698-b3e4-58378c46a3bd resourceVersion: "43975" uid: aaf4bdd2-c0f4-442b-968d-87bb8454e0de spec: sourcePod: network-check-source-7f44b6dd87-xzqnw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:18:30Z" message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 729.914µs message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:30Z" - latency: 907.878µs message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:30Z" - latency: 764.574µs message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:37:30Z" - latency: 1.337274ms message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:36:30Z" - latency: 925.793µs message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:35:30Z" - latency: 874.846µs message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:34:30Z" - latency: 861.816µs message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:33:30Z" - latency: 903.787µs message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:32:30Z" - latency: 915.908µs message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:31:30Z" - latency: 876.001µs message: 'network-check-target-ip-10-0-143-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:30:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:11:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-69-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-69.ec2.internal uid: 80c69e43-2300-4698-b3e4-58378c46a3bd resourceVersion: "45981" uid: 75b93e39-9284-431a-ac88-1ec01517b5b8 spec: sourcePod: network-check-source-7f44b6dd87-xzqnw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T18:17:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 779.951µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:41:30Z" - latency: 1.655243ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:41:30Z" - latency: 872.737µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:40:30Z" - latency: 1.539251ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:40:30Z" - latency: 816.365µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:30Z" - latency: 1.575522ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:39:30Z" - latency: 865.951µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:30Z" - latency: 1.553425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:38:30Z" - latency: 818.57µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:37:30Z" - latency: 2.366322ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:37:30Z" kind: List metadata: resourceVersion: ""