apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:36:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-176-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-176.ec2.internal uid: 0b83419f-70c4-4737-b497-9267369744e4 resourceVersion: "71086" uid: e24c59c7-2987-49b4-a640-58bbb742e7b9 spec: sourcePod: network-check-source-7d88cb55d8-lsccn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T12:43:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.34457ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:25:54Z" - latency: 1.094046ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:24:54Z" - latency: 1.44126ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:23:54Z" - latency: 1.052381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:22:54Z" - latency: 1.091488ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:21:54Z" - latency: 1.057542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:20:54Z" - latency: 1.447359ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:19:54Z" - latency: 1.174747ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:18:54Z" - latency: 1.066344ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:17:54Z" - latency: 1.568586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:16:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:36:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-176-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-176.ec2.internal uid: 0b83419f-70c4-4737-b497-9267369744e4 resourceVersion: "69949" uid: 07b557cc-3ff3-4664-aaee-8cafd3f7c081 spec: sourcePod: network-check-source-7d88cb55d8-lsccn targetEndpoint: aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T12:42:54Z" message: 'load-balancer-api-external: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.044932ms message: 'load-balancer-api-external: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:24:54Z" - latency: 7.68776ms message: 'load-balancer-api-external: resolved host name aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:24:54Z" - latency: 4.109969ms message: 'load-balancer-api-external: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:23:54Z" - latency: 6.435524ms message: 'load-balancer-api-external: resolved host name aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:23:54Z" - latency: 5.490661ms message: 'load-balancer-api-external: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:22:54Z" - latency: 8.918565ms message: 'load-balancer-api-external: resolved host name aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:22:54Z" - latency: 5.003861ms message: 'load-balancer-api-external: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:21:54Z" - latency: 9.075525ms message: 'load-balancer-api-external: resolved host name aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:21:54Z" - latency: 4.845459ms message: 'load-balancer-api-external: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:20:54Z" - latency: 7.364155ms message: 'load-balancer-api-external: resolved host name aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:20:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:36:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-176-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-176.ec2.internal uid: 0b83419f-70c4-4737-b497-9267369744e4 resourceVersion: "69950" uid: aeda96f5-9e35-4f10-8eee-ee40f9af3cef spec: sourcePod: network-check-source-7d88cb55d8-lsccn targetEndpoint: aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T12:42:54Z" message: 'load-balancer-api-internal: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.051286ms message: 'load-balancer-api-internal: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:24:54Z" - latency: 7.65974ms message: 'load-balancer-api-internal: resolved host name aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:24:54Z" - latency: 4.128205ms message: 'load-balancer-api-internal: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:23:54Z" - latency: 6.39523ms message: 'load-balancer-api-internal: resolved host name aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:23:54Z" - latency: 5.09285ms message: 'load-balancer-api-internal: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:22:54Z" - latency: 8.866361ms message: 'load-balancer-api-internal: resolved host name aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:22:54Z" - latency: 5.018498ms message: 'load-balancer-api-internal: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:21:54Z" - latency: 9.012524ms message: 'load-balancer-api-internal: resolved host name aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:21:54Z" - latency: 4.880158ms message: 'load-balancer-api-internal: tcp connection to aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:20:54Z" - latency: 7.319607ms message: 'load-balancer-api-internal: resolved host name aae59723ec18a4f46a2fc07574c395a1-4a74fec8b773572c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:20:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:36:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-176-to-network-check-target-ip-10-0-128-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-176.ec2.internal uid: 0b83419f-70c4-4737-b497-9267369744e4 resourceVersion: "71083" uid: a88ddf2c-7e42-47e0-91a6-3a2a55df44d8 spec: sourcePod: network-check-source-7d88cb55d8-lsccn targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T12:43:54Z" message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.699989ms message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:25:54Z" - latency: 1.156428ms message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:24:54Z" - latency: 1.826044ms message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:23:54Z" - latency: 1.126534ms message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:22:54Z" - latency: 1.456755ms message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:21:54Z" - latency: 1.011353ms message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:20:54Z" - latency: 1.060448ms message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:19:54Z" - latency: 1.114664ms message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:18:54Z" - latency: 1.410497ms message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:17:54Z" - latency: 1.01193ms message: 'network-check-target-ip-10-0-128-176: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:16:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:36:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-176-to-network-check-target-ip-10-0-132-90 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-176.ec2.internal uid: 0b83419f-70c4-4737-b497-9267369744e4 resourceVersion: "71085" uid: f1192b1d-d313-44d2-9543-176383a54fa1 spec: sourcePod: network-check-source-7d88cb55d8-lsccn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T12:43:54Z" message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.504718ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:25:54Z" - latency: 2.333256ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:24:54Z" - latency: 2.479122ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:23:54Z" - latency: 2.595508ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:22:54Z" - latency: 2.369647ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:21:54Z" - latency: 2.237574ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:20:54Z" - latency: 2.135799ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:19:54Z" - latency: 2.584487ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:18:54Z" - latency: 2.43931ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:17:54Z" - latency: 2.363625ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:16:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:36:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-176-to-network-check-target-ip-10-0-136-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-176.ec2.internal uid: 0b83419f-70c4-4737-b497-9267369744e4 resourceVersion: "71084" uid: 3ce75a79-504a-47b3-a9d1-5935a9075e5d spec: sourcePod: network-check-source-7d88cb55d8-lsccn targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T12:43:54Z" message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.462631ms message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:25:54Z" - latency: 2.565628ms message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:24:54Z" - latency: 2.626603ms message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:23:54Z" - latency: 2.382933ms message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:22:54Z" - latency: 2.450666ms message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:21:54Z" - latency: 2.109902ms message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:20:54Z" - latency: 1.999517ms message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:19:54Z" - latency: 2.43969ms message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:18:54Z" - latency: 2.492152ms message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:17:54Z" - latency: 2.439189ms message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:16:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:36:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-176-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-176.ec2.internal uid: 0b83419f-70c4-4737-b497-9267369744e4 resourceVersion: "69948" uid: 8e07bed4-02c6-4994-8bd6-083b7a1b0d76 spec: sourcePod: network-check-source-7d88cb55d8-lsccn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T12:42:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.242774ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:24:54Z" - latency: 1.927633ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:24:54Z" - latency: 1.154413ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:23:54Z" - latency: 1.8142ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:23:54Z" - latency: 1.279844ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:22:54Z" - latency: 1.806974ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:22:54Z" - latency: 913.843µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:21:54Z" - latency: 1.639217ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:21:54Z" - latency: 1.415425ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:20:54Z" - latency: 1.764403ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:20:54Z" kind: List metadata: resourceVersion: ""