apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:01:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-15-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-15.ec2.internal uid: f24ba576-b244-445a-9909-6c19c1b24f90 resourceVersion: "21161" uid: 06ed50a0-088d-40f5-834b-f64b3d27a021 spec: sourcePod: network-check-source-869dcfcdcd-jwkw4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T19:08:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 846.842µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:16Z" - latency: 929.423µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:16Z" - latency: 851.473µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:16Z" - latency: 933.071µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:16Z" - latency: 942.6µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:16Z" - latency: 887µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:16Z" - latency: 939.431µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:16Z" - latency: 888.072µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:16Z" - latency: 1.232537ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:14:16Z" - latency: 1.949873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:13:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:01:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-15-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-15.ec2.internal uid: f24ba576-b244-445a-9909-6c19c1b24f90 resourceVersion: "22570" uid: ee2909ac-3daa-4708-9e3a-83d1010fd8ab spec: sourcePod: network-check-source-869dcfcdcd-jwkw4 targetEndpoint: a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T19:07:16Z" message: 'load-balancer-api-external: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.467661ms message: 'load-balancer-api-external: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:25:16Z" - latency: 8.76333ms message: 'load-balancer-api-external: resolved host name a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:25:16Z" - latency: 4.576907ms message: 'load-balancer-api-external: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:16Z" - latency: 9.033257ms message: 'load-balancer-api-external: resolved host name a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:24:16Z" - latency: 4.930431ms message: 'load-balancer-api-external: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:16Z" - latency: 7.937761ms message: 'load-balancer-api-external: resolved host name a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:23:16Z" - latency: 5.099664ms message: 'load-balancer-api-external: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:16Z" - latency: 9.982272ms message: 'load-balancer-api-external: resolved host name a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:22:16Z" - latency: 4.791387ms message: 'load-balancer-api-external: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:16Z" - latency: 8.41305ms message: 'load-balancer-api-external: resolved host name a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:21:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:01:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-15-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-15.ec2.internal uid: f24ba576-b244-445a-9909-6c19c1b24f90 resourceVersion: "22571" uid: 6c51c677-2443-4f3b-afb5-8bb8b97db255 spec: sourcePod: network-check-source-869dcfcdcd-jwkw4 targetEndpoint: a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T19:07:16Z" message: 'load-balancer-api-internal: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.881726ms message: 'load-balancer-api-internal: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:25:16Z" - latency: 8.703974ms message: 'load-balancer-api-internal: resolved host name a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:25:16Z" - latency: 4.684187ms message: 'load-balancer-api-internal: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:16Z" - latency: 9.004542ms message: 'load-balancer-api-internal: resolved host name a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:24:16Z" - latency: 4.986592ms message: 'load-balancer-api-internal: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:16Z" - latency: 7.898633ms message: 'load-balancer-api-internal: resolved host name a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:23:16Z" - latency: 5.050772ms message: 'load-balancer-api-internal: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:16Z" - latency: 9.911784ms message: 'load-balancer-api-internal: resolved host name a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:22:16Z" - latency: 4.872219ms message: 'load-balancer-api-internal: tcp connection to a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:16Z" - latency: 8.397466ms message: 'load-balancer-api-internal: resolved host name a9cb403fabc0a4225a7f5b938ab93bfb-2dc7ccdd6e3340c8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:21:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:01:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-15-to-network-check-target-ip-10-0-130-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-15.ec2.internal uid: f24ba576-b244-445a-9909-6c19c1b24f90 resourceVersion: "21160" uid: 581e9f80-0c5b-499b-a795-f069d207389d spec: sourcePod: network-check-source-869dcfcdcd-jwkw4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:08:16Z" message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.13458ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:16Z" - latency: 2.123577ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:16Z" - latency: 1.88559ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:16Z" - latency: 2.01205ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:16Z" - latency: 2.177381ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:16Z" - latency: 1.932888ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:16Z" - latency: 2.296563ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:16Z" - latency: 2.025502ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:16Z" - latency: 2.235274ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:14:16Z" - latency: 2.346429ms message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:13:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:01:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-15-to-network-check-target-ip-10-0-136-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-15.ec2.internal uid: f24ba576-b244-445a-9909-6c19c1b24f90 resourceVersion: "21159" uid: 980c87bb-3823-4fc7-a1df-0711195a20ea spec: sourcePod: network-check-source-869dcfcdcd-jwkw4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:08:16Z" message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.041484ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:16Z" - latency: 1.985767ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:16Z" - latency: 1.699649ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:16Z" - latency: 1.792431ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:16Z" - latency: 1.939748ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:16Z" - latency: 2.394514ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:16Z" - latency: 2.37542ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:16Z" - latency: 1.569941ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:16Z" - latency: 2.108172ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:14:16Z" - latency: 2.008568ms message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:13:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:01:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-15-to-network-check-target-ip-10-0-143-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-15.ec2.internal uid: f24ba576-b244-445a-9909-6c19c1b24f90 resourceVersion: "21158" uid: dd78f44f-341c-4616-8c45-bd0092caa76d spec: sourcePod: network-check-source-869dcfcdcd-jwkw4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:08:16Z" message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.192792ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:16Z" - latency: 931.058µs message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:16Z" - latency: 902.789µs message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:16Z" - latency: 950.315µs message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:16Z" - latency: 1.013812ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:16Z" - latency: 942.237µs message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:16Z" - latency: 903.94µs message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:16Z" - latency: 848.737µs message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:16Z" - latency: 1.587505ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:14:16Z" - latency: 1.485953ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:13:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:01:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-15-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-15.ec2.internal uid: f24ba576-b244-445a-9909-6c19c1b24f90 resourceVersion: "22569" uid: d3ea77e7-8e34-407d-ba2e-647a457bed3d spec: sourcePod: network-check-source-869dcfcdcd-jwkw4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T19:07:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 879.126µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:25:16Z" - latency: 1.82273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:25:16Z" - latency: 1.038324ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:16Z" - latency: 2.108247ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:24:16Z" - latency: 824.583µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:16Z" - latency: 2.151457ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:23:16Z" - latency: 903.861µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:16Z" - latency: 1.918864ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:22:16Z" - latency: 1.22721ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:16Z" - latency: 1.852392ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:21:16Z" kind: List metadata: resourceVersion: ""