apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-39-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-39.ec2.internal uid: 29503af7-8cbe-41bf-8fdc-c30a3ce6a8da resourceVersion: "55817" uid: cdeb3839-f816-4f08-a4f5-1cc9a62af79f spec: sourcePod: network-check-source-989f8b8dc-zh2m8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T15:14:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.053375ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:42:23Z" - latency: 830.085µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:41:23Z" - latency: 940.754µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:40:23Z" - latency: 1.347963ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:39:23Z" - latency: 1.238312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:38:23Z" - latency: 888.548µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:37:23Z" - latency: 1.127516ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:36:23Z" - latency: 824.951µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:35:23Z" - latency: 1.119377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:34:23Z" - latency: 1.133165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:33:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-39-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-39.ec2.internal uid: 29503af7-8cbe-41bf-8fdc-c30a3ce6a8da resourceVersion: "56868" uid: ff2c86d6-5cd3-4036-bd7e-7290e0c59270 spec: sourcePod: network-check-source-989f8b8dc-zh2m8 targetEndpoint: ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:13:23Z" message: 'load-balancer-api-external: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.329592ms message: 'load-balancer-api-external: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:43:23Z" - latency: 6.9605ms message: 'load-balancer-api-external: resolved host name ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:43:23Z" - latency: 3.778147ms message: 'load-balancer-api-external: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:42:23Z" - latency: 7.58041ms message: 'load-balancer-api-external: resolved host name ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:42:23Z" - latency: 4.899783ms message: 'load-balancer-api-external: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:41:23Z" - latency: 7.31323ms message: 'load-balancer-api-external: resolved host name ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:41:23Z" - latency: 5.949528ms message: 'load-balancer-api-external: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:40:23Z" - latency: 6.515083ms message: 'load-balancer-api-external: resolved host name ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:40:23Z" - latency: 4.405557ms message: 'load-balancer-api-external: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:39:23Z" - latency: 6.678102ms message: 'load-balancer-api-external: resolved host name ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:39:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-39-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-39.ec2.internal uid: 29503af7-8cbe-41bf-8fdc-c30a3ce6a8da resourceVersion: "56867" uid: f15bb2f7-7a63-4dee-a031-33354a7b14f4 spec: sourcePod: network-check-source-989f8b8dc-zh2m8 targetEndpoint: ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:13:23Z" message: 'load-balancer-api-internal: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.226204ms message: 'load-balancer-api-internal: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:43:23Z" - latency: 6.840277ms message: 'load-balancer-api-internal: resolved host name ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:43:23Z" - latency: 4.316481ms message: 'load-balancer-api-internal: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:42:23Z" - latency: 7.551047ms message: 'load-balancer-api-internal: resolved host name ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:42:23Z" - latency: 4.806099ms message: 'load-balancer-api-internal: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:41:23Z" - latency: 7.240324ms message: 'load-balancer-api-internal: resolved host name ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:41:23Z" - latency: 3.947336ms message: 'load-balancer-api-internal: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:40:23Z" - latency: 6.598071ms message: 'load-balancer-api-internal: resolved host name ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:40:23Z" - latency: 5.416052ms message: 'load-balancer-api-internal: tcp connection to ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:39:23Z" - latency: 6.600678ms message: 'load-balancer-api-internal: resolved host name ad2950fd2945049b5a3e3ff0d3f11dd8-e840889c1590e417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:39:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-39-to-network-check-target-ip-10-0-130-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-39.ec2.internal uid: 29503af7-8cbe-41bf-8fdc-c30a3ce6a8da resourceVersion: "55814" uid: e12eaa6a-f236-4512-9acf-1e16712a288f spec: sourcePod: network-check-source-989f8b8dc-zh2m8 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:14:23Z" message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.765413ms message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:42:23Z" - latency: 1.057922ms message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:41:23Z" - latency: 1.148916ms message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:40:23Z" - latency: 1.045795ms message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:39:23Z" - latency: 833.58µs message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:38:23Z" - latency: 947.882µs message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:37:23Z" - latency: 1.402765ms message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:36:23Z" - latency: 937.889µs message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:35:23Z" - latency: 1.439053ms message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:34:23Z" - latency: 928.111µs message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:33:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-39-to-network-check-target-ip-10-0-131-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-39.ec2.internal uid: 29503af7-8cbe-41bf-8fdc-c30a3ce6a8da resourceVersion: "55815" uid: e4ae0ea4-97b0-46d6-93eb-9b672b5f14e9 spec: sourcePod: network-check-source-989f8b8dc-zh2m8 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:14:23Z" message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.363986ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:42:23Z" - latency: 2.270878ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:41:23Z" - latency: 2.06564ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:40:23Z" - latency: 2.189083ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:39:23Z" - latency: 2.35739ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:38:23Z" - latency: 2.256894ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:37:23Z" - latency: 2.50529ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:36:23Z" - latency: 2.355021ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:35:23Z" - latency: 2.33453ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:34:23Z" - latency: 2.387849ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:33:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-39-to-network-check-target-ip-10-0-132-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-39.ec2.internal uid: 29503af7-8cbe-41bf-8fdc-c30a3ce6a8da resourceVersion: "55816" uid: 5425f505-94f5-4605-8ed9-466bc5aec20f spec: sourcePod: network-check-source-989f8b8dc-zh2m8 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:14:23Z" message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.388683ms message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:42:23Z" - latency: 2.277156ms message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:41:23Z" - latency: 2.42165ms message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:40:23Z" - latency: 2.524606ms message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:39:23Z" - latency: 2.432075ms message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:38:23Z" - latency: 2.399482ms message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:37:23Z" - latency: 2.475195ms message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:36:23Z" - latency: 2.360882ms message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:35:23Z" - latency: 2.313105ms message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:34:23Z" - latency: 2.87379ms message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:33:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-39-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-39.ec2.internal uid: 29503af7-8cbe-41bf-8fdc-c30a3ce6a8da resourceVersion: "56866" uid: c4d7bcc0-8f68-468a-9890-b57064e3869f spec: sourcePod: network-check-source-989f8b8dc-zh2m8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T15:13:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 924.871µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:43:23Z" - latency: 1.662795ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:43:23Z" - latency: 1.041031ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:42:23Z" - latency: 1.94569ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:42:23Z" - latency: 743.421µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:41:23Z" - latency: 1.635882ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:41:23Z" - latency: 948.444µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:40:23Z" - latency: 1.532957ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:40:23Z" - latency: 804.546µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:39:23Z" - latency: 1.799503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:39:23Z" kind: List metadata: resourceVersion: ""