apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-119-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-119.ec2.internal uid: 39fbeda6-6d80-46c9-b6ca-544659e93baa resourceVersion: "54707" uid: 4aeb6270-c024-43c0-8040-9ccc6ae79e8e spec: sourcePod: network-check-source-989f8b8dc-67485 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-05T13:30:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.040936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 1.27233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 1.080841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 1.098302ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 956.392µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:07Z" - latency: 1.189996ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:07Z" - latency: 1.087179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:07Z" - latency: 934.004µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:07Z" - latency: 1.103626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:07Z" - latency: 985.171µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-119-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-119.ec2.internal uid: 39fbeda6-6d80-46c9-b6ca-544659e93baa resourceVersion: "55643" uid: 10872f54-3987-4f45-a503-e11b146f6bb5 spec: sourcePod: network-check-source-989f8b8dc-67485 targetEndpoint: a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-05T13:29:07Z" message: 'load-balancer-api-external: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.404917ms message: 'load-balancer-api-external: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:59:07Z" - latency: 6.975404ms message: 'load-balancer-api-external: resolved host name a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:59:07Z" - latency: 5.116531ms message: 'load-balancer-api-external: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 6.904423ms message: 'load-balancer-api-external: resolved host name a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:58:07Z" - latency: 4.461835ms message: 'load-balancer-api-external: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 7.668284ms message: 'load-balancer-api-external: resolved host name a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:57:07Z" - latency: 5.424494ms message: 'load-balancer-api-external: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 6.567205ms message: 'load-balancer-api-external: resolved host name a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:56:07Z" - latency: 4.932287ms message: 'load-balancer-api-external: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 7.287115ms message: 'load-balancer-api-external: resolved host name a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:55:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-119-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-119.ec2.internal uid: 39fbeda6-6d80-46c9-b6ca-544659e93baa resourceVersion: "55642" uid: 95adfb9a-602d-45d8-9fe6-7f2115ba6430 spec: sourcePod: network-check-source-989f8b8dc-67485 targetEndpoint: a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-05T13:29:07Z" message: 'load-balancer-api-internal: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.427542ms message: 'load-balancer-api-internal: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:59:07Z" - latency: 6.966513ms message: 'load-balancer-api-internal: resolved host name a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:59:07Z" - latency: 4.462238ms message: 'load-balancer-api-internal: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 6.964616ms message: 'load-balancer-api-internal: resolved host name a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:58:07Z" - latency: 4.40911ms message: 'load-balancer-api-internal: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 7.642739ms message: 'load-balancer-api-internal: resolved host name a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:57:07Z" - latency: 5.440586ms message: 'load-balancer-api-internal: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 6.512407ms message: 'load-balancer-api-internal: resolved host name a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:56:07Z" - latency: 4.912176ms message: 'load-balancer-api-internal: tcp connection to a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 7.348333ms message: 'load-balancer-api-internal: resolved host name a49deaf9d4bcf4c4393823552cc952da-832560f9bb2274b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:55:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-119-to-network-check-target-ip-10-0-132-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-119.ec2.internal uid: 39fbeda6-6d80-46c9-b6ca-544659e93baa resourceVersion: "54705" uid: 914649d8-3e54-4a23-9728-bc8b1e523065 spec: sourcePod: network-check-source-989f8b8dc-67485 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-05T13:30:07Z" message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.199579ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 2.310156ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 2.31156ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 2.490013ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 2.198893ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:07Z" - latency: 2.393032ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:07Z" - latency: 2.682113ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:07Z" - latency: 2.236131ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:07Z" - latency: 2.357938ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:07Z" - latency: 2.459263ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-119-to-network-check-target-ip-10-0-139-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-119.ec2.internal uid: 39fbeda6-6d80-46c9-b6ca-544659e93baa resourceVersion: "54706" uid: 60e6b37b-85e0-4e7d-8ffd-449b4f89b5da spec: sourcePod: network-check-source-989f8b8dc-67485 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-05T13:30:07Z" message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.318569ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 2.389801ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 2.494121ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 2.501691ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 3.253091ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:07Z" - latency: 2.40027ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:07Z" - latency: 2.353966ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:07Z" - latency: 2.5012ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:07Z" - latency: 2.375319ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:07Z" - latency: 2.437493ms message: 'network-check-target-ip-10-0-139-155: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-119-to-network-check-target-ip-10-0-141-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-119.ec2.internal uid: 39fbeda6-6d80-46c9-b6ca-544659e93baa resourceVersion: "54704" uid: d84a0a26-2ec5-4a60-93f2-01f565ba64bb spec: sourcePod: network-check-source-989f8b8dc-67485 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-05T13:30:07Z" message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.214601ms message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 1.446476ms message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 925.597µs message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 1.18805ms message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 916.528µs message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:07Z" - latency: 895.623µs message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:07Z" - latency: 1.572991ms message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:07Z" - latency: 1.088219ms message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:07Z" - latency: 1.314725ms message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:07Z" - latency: 937.807µs message: 'network-check-target-ip-10-0-141-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-119-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-119.ec2.internal uid: 39fbeda6-6d80-46c9-b6ca-544659e93baa resourceVersion: "55641" uid: f0f30403-dd92-49ca-8fa0-a01edcd0ffba spec: sourcePod: network-check-source-989f8b8dc-67485 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-05T13:29:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.0085ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:59:07Z" - latency: 1.750138ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:59:07Z" - latency: 798.339µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 1.623797ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:58:07Z" - latency: 1.083463ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 1.860324ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:57:07Z" - latency: 1.086565ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 1.663935ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:56:07Z" - latency: 775.841µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 1.786881ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:55:07Z" kind: List metadata: resourceVersion: ""