apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T03:51:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-215-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-215.ec2.internal uid: 85e578fa-eb80-4815-bc28-e2c9c291e443 resourceVersion: "54158" uid: c74b51a8-5dd1-4bd0-a8af-8e0ad8f44c87 spec: sourcePod: network-check-source-685456655f-2srz4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-07T03:58:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 842.407µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:19:04Z" - latency: 995.217µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:18:04Z" - latency: 916.705µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:17:04Z" - latency: 867.043µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:16:04Z" - latency: 1.070784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:15:04Z" - latency: 1.142156ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:14:04Z" - latency: 1.174806ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:13:04Z" - latency: 1.236787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:12:04Z" - latency: 1.194303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:11:04Z" - latency: 1.411018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:10:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T03:51:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-215-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-215.ec2.internal uid: 85e578fa-eb80-4815-bc28-e2c9c291e443 resourceVersion: "55872" uid: 6d509047-a391-46b5-aaed-8a64e916446a spec: sourcePod: network-check-source-685456655f-2srz4 targetEndpoint: a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-07T03:57:04Z" message: 'load-balancer-api-external: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.991041ms message: 'load-balancer-api-external: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:21:04Z" - latency: 7.115221ms message: 'load-balancer-api-external: resolved host name a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:21:04Z" - latency: 5.188515ms message: 'load-balancer-api-external: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:20:04Z" - latency: 14.902669ms message: 'load-balancer-api-external: resolved host name a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:20:04Z" - latency: 4.085806ms message: 'load-balancer-api-external: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:19:04Z" - latency: 6.378828ms message: 'load-balancer-api-external: resolved host name a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:19:04Z" - latency: 3.121426ms message: 'load-balancer-api-external: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:18:04Z" - latency: 11.77869ms message: 'load-balancer-api-external: resolved host name a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:18:04Z" - latency: 5.45228ms message: 'load-balancer-api-external: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:17:04Z" - latency: 6.966077ms message: 'load-balancer-api-external: resolved host name a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:17:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T03:51:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-215-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-215.ec2.internal uid: 85e578fa-eb80-4815-bc28-e2c9c291e443 resourceVersion: "55873" uid: 8173e99f-70a7-405b-8044-dc2f94355414 spec: sourcePod: network-check-source-685456655f-2srz4 targetEndpoint: a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-07T03:57:04Z" message: 'load-balancer-api-internal: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.899493ms message: 'load-balancer-api-internal: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:21:04Z" - latency: 7.046161ms message: 'load-balancer-api-internal: resolved host name a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:21:04Z" - latency: 5.149525ms message: 'load-balancer-api-internal: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:20:04Z" - latency: 14.96476ms message: 'load-balancer-api-internal: resolved host name a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:20:04Z" - latency: 3.226218ms message: 'load-balancer-api-internal: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:19:04Z" - latency: 6.30249ms message: 'load-balancer-api-internal: resolved host name a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:19:04Z" - latency: 3.139551ms message: 'load-balancer-api-internal: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:18:04Z" - latency: 11.815832ms message: 'load-balancer-api-internal: resolved host name a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:18:04Z" - latency: 5.454157ms message: 'load-balancer-api-internal: tcp connection to a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:17:04Z" - latency: 7.052414ms message: 'load-balancer-api-internal: resolved host name a940e6a219a434c18a0159392a850b73-5b339249cce0e4ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:17:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T03:51:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-215-to-network-check-target-ip-10-0-131-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-215.ec2.internal uid: 85e578fa-eb80-4815-bc28-e2c9c291e443 resourceVersion: "54155" uid: bb39aa3f-a0a7-4d5f-92ea-dca0c35e5851 spec: sourcePod: network-check-source-685456655f-2srz4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-07T03:58:04Z" message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 804.251µs message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:19:04Z" - latency: 867.924µs message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:18:04Z" - latency: 857.89µs message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:17:04Z" - latency: 857.36µs message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:16:04Z" - latency: 1.209855ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:15:04Z" - latency: 873.917µs message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:14:04Z" - latency: 1.631088ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:13:04Z" - latency: 879.168µs message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:12:04Z" - latency: 1.012598ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:11:04Z" - latency: 1.271247ms message: 'network-check-target-ip-10-0-131-215: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:10:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T03:51:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-215-to-network-check-target-ip-10-0-132-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-215.ec2.internal uid: 85e578fa-eb80-4815-bc28-e2c9c291e443 resourceVersion: "54157" uid: 1cf00c2d-603f-4f09-8bf6-b324643abf31 spec: sourcePod: network-check-source-685456655f-2srz4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-07T03:58:04Z" message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.415416ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:19:04Z" - latency: 2.242468ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:18:04Z" - latency: 2.511643ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:17:04Z" - latency: 2.167768ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:16:04Z" - latency: 2.524426ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:15:04Z" - latency: 2.36373ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:14:04Z" - latency: 2.549843ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:13:04Z" - latency: 2.516082ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:12:04Z" - latency: 2.316224ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:11:04Z" - latency: 2.739933ms message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:10:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T03:51:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-215-to-network-check-target-ip-10-0-132-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-215.ec2.internal uid: 85e578fa-eb80-4815-bc28-e2c9c291e443 resourceVersion: "54156" uid: 88b4b3de-e26a-4721-804c-779c27ccd0e0 spec: sourcePod: network-check-source-685456655f-2srz4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-07T03:58:04Z" message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.411462ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:19:04Z" - latency: 2.380364ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:18:04Z" - latency: 1.964943ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:17:04Z" - latency: 2.350892ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:16:04Z" - latency: 2.081389ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:15:04Z" - latency: 1.88906ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:14:04Z" - latency: 2.81023ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:13:04Z" - latency: 2.492334ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:12:04Z" - latency: 1.996622ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:11:04Z" - latency: 1.957161ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:10:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T03:51:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-215-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-215.ec2.internal uid: 85e578fa-eb80-4815-bc28-e2c9c291e443 resourceVersion: "55871" uid: 45975c71-ac9e-4db3-9e61-34dd31fd85d4 spec: sourcePod: network-check-source-685456655f-2srz4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-07T03:57:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.086741ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:21:04Z" - latency: 1.698798ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T04:21:04Z" - latency: 805.416µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:20:04Z" - latency: 1.58273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T04:20:04Z" - latency: 856.321µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:19:04Z" - latency: 1.709826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T04:19:04Z" - latency: 768.43µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:18:04Z" - latency: 1.536531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T04:18:04Z" - latency: 991.267µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:17:04Z" - latency: 1.678407ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T04:17:04Z" kind: List metadata: resourceVersion: ""