apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T22:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-131-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-131.ec2.internal uid: 4c154f2c-fa82-4e58-832c-bb5179a955af resourceVersion: "64010" uid: 734390a3-f7ff-4993-b8e6-d87b774f9aee spec: sourcePod: network-check-source-7bc5b6bf85-vv74w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T22:32:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.143464ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:07:44Z" - latency: 1.135951ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:06:44Z" - latency: 1.64573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:05:44Z" - latency: 1.221891ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:04:44Z" - latency: 1.452485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:03:44Z" - latency: 997.699µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:02:44Z" - latency: 853.634µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:01:44Z" - latency: 1.288079ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:00:44Z" - latency: 985.715µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:59:44Z" - latency: 981.336µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:58:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T22:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-131-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-131.ec2.internal uid: 4c154f2c-fa82-4e58-832c-bb5179a955af resourceVersion: "64011" uid: f4a88402-ef20-429d-897c-4fefc173b035 spec: sourcePod: network-check-source-7bc5b6bf85-vv74w targetEndpoint: a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T22:31:44Z" message: 'load-balancer-api-external: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.368544ms message: 'load-balancer-api-external: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:07:44Z" - latency: 12.097925ms message: 'load-balancer-api-external: resolved host name a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:07:44Z" - latency: 5.670245ms message: 'load-balancer-api-external: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:06:44Z" - latency: 8.708185ms message: 'load-balancer-api-external: resolved host name a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:06:44Z" - latency: 5.664405ms message: 'load-balancer-api-external: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:05:44Z" - latency: 11.942977ms message: 'load-balancer-api-external: resolved host name a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:05:44Z" - latency: 5.464581ms message: 'load-balancer-api-external: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:04:44Z" - latency: 8.925299ms message: 'load-balancer-api-external: resolved host name a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:04:44Z" - latency: 4.468573ms message: 'load-balancer-api-external: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:03:44Z" - latency: 8.827613ms message: 'load-balancer-api-external: resolved host name a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:03:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T22:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-131-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-131.ec2.internal uid: 4c154f2c-fa82-4e58-832c-bb5179a955af resourceVersion: "64012" uid: f473eda9-8162-444d-8907-2637465ce9f4 spec: sourcePod: network-check-source-7bc5b6bf85-vv74w targetEndpoint: a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T22:31:44Z" message: 'load-balancer-api-internal: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.486316ms message: 'load-balancer-api-internal: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:07:44Z" - latency: 12.027471ms message: 'load-balancer-api-internal: resolved host name a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:07:44Z" - latency: 5.745284ms message: 'load-balancer-api-internal: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:06:44Z" - latency: 8.776233ms message: 'load-balancer-api-internal: resolved host name a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:06:44Z" - latency: 4.52071ms message: 'load-balancer-api-internal: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:05:44Z" - latency: 11.923339ms message: 'load-balancer-api-internal: resolved host name a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:05:44Z" - latency: 5.478932ms message: 'load-balancer-api-internal: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:04:44Z" - latency: 8.964016ms message: 'load-balancer-api-internal: resolved host name a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:04:44Z" - latency: 4.477182ms message: 'load-balancer-api-internal: tcp connection to a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:03:44Z" - latency: 8.805231ms message: 'load-balancer-api-internal: resolved host name a66271a0cc0044421a47d2ce1695d94c-ccaa018fe60ef2f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T23:03:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T22:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-131-to-network-check-target-ip-10-0-133-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-131.ec2.internal uid: 4c154f2c-fa82-4e58-832c-bb5179a955af resourceVersion: "64006" uid: 5a3db6bc-c329-44e4-a676-d4e4eb451d8e spec: sourcePod: network-check-source-7bc5b6bf85-vv74w targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T22:32:44Z" message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 834.601µs message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:07:44Z" - latency: 875.744µs message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:06:44Z" - latency: 1.049869ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:05:44Z" - latency: 941.609µs message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:04:44Z" - latency: 1.409106ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:03:44Z" - latency: 1.927994ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:02:44Z" - latency: 1.268085ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:01:44Z" - latency: 891.108µs message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:00:44Z" - latency: 938.015µs message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:59:44Z" - latency: 1.465571ms message: 'network-check-target-ip-10-0-133-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:58:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T22:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-131-to-network-check-target-ip-10-0-133-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-131.ec2.internal uid: 4c154f2c-fa82-4e58-832c-bb5179a955af resourceVersion: "64007" uid: 9a5e3bba-5910-4bb5-b8ce-6e20036c5467 spec: sourcePod: network-check-source-7bc5b6bf85-vv74w targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T22:32:44Z" message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.232288ms message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:07:44Z" - latency: 2.243578ms message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:06:44Z" - latency: 2.240693ms message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:05:44Z" - latency: 2.204598ms message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:04:44Z" - latency: 2.29915ms message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:03:44Z" - latency: 2.330333ms message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:02:44Z" - latency: 1.895901ms message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:01:44Z" - latency: 2.500275ms message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:00:44Z" - latency: 2.138111ms message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:59:44Z" - latency: 2.195746ms message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:58:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T22:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-131-to-network-check-target-ip-10-0-134-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-131.ec2.internal uid: 4c154f2c-fa82-4e58-832c-bb5179a955af resourceVersion: "64008" uid: 3b08dcd3-ef79-466e-b07f-ca0f9ba07131 spec: sourcePod: network-check-source-7bc5b6bf85-vv74w targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-23T22:32:44Z" message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.199204ms message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:07:44Z" - latency: 2.288785ms message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:06:44Z" - latency: 2.237429ms message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:05:44Z" - latency: 1.973786ms message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:04:44Z" - latency: 2.096514ms message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:03:44Z" - latency: 2.875315ms message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:02:44Z" - latency: 1.996321ms message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:01:44Z" - latency: 1.879416ms message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:00:44Z" - latency: 1.788865ms message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:59:44Z" - latency: 1.937666ms message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T22:58:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T22:25:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-131-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-131.ec2.internal uid: 4c154f2c-fa82-4e58-832c-bb5179a955af resourceVersion: "64009" uid: 93a13925-25b2-47e5-99ac-d6abd99158b3 spec: sourcePod: network-check-source-7bc5b6bf85-vv74w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T22:31:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 999.917µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:07:44Z" - latency: 2.388981ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T23:07:44Z" - latency: 1.280662ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:06:44Z" - latency: 1.89013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T23:06:44Z" - latency: 1.193797ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:05:44Z" - latency: 2.177308ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T23:05:44Z" - latency: 1.058682ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:04:44Z" - latency: 1.87959ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T23:04:44Z" - latency: 1.018998ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T23:03:44Z" - latency: 1.856503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T23:03:44Z" kind: List metadata: resourceVersion: ""