apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:24:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.ec2.internal uid: c6f9b1a6-4324-4aad-a939-793b8d5729cb resourceVersion: "29806" uid: 185e4c41-0145-40b5-a352-84a3a986ed4a spec: sourcePod: network-check-source-56d84b9f44-g5vrm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T16:31:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.179988ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:38:04Z" - latency: 1.078215ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:37:04Z" - latency: 1.259747ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:36:04Z" - latency: 1.17503ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:35:04Z" - latency: 1.136796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:34:04Z" - latency: 971.558µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:33:04Z" - latency: 1.004628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:32:04Z" - latency: 1.429799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:31:04Z" - latency: 1.174629ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:30:04Z" - latency: 1.548324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:29:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:24:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.ec2.internal uid: c6f9b1a6-4324-4aad-a939-793b8d5729cb resourceVersion: "28264" uid: e25c85b1-a94a-4116-928c-060c85d3538b spec: sourcePod: network-check-source-56d84b9f44-g5vrm targetEndpoint: a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T16:30:04Z" message: 'load-balancer-api-external: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.557055ms message: 'load-balancer-api-external: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:36:04Z" - latency: 7.65085ms message: 'load-balancer-api-external: resolved host name a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:36:04Z" - latency: 5.226953ms message: 'load-balancer-api-external: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:35:04Z" - latency: 7.085212ms message: 'load-balancer-api-external: resolved host name a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:35:04Z" - latency: 4.996647ms message: 'load-balancer-api-external: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:34:04Z" - latency: 8.38222ms message: 'load-balancer-api-external: resolved host name a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:34:04Z" - latency: 6.1131ms message: 'load-balancer-api-external: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:33:04Z" - latency: 6.734314ms message: 'load-balancer-api-external: resolved host name a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:33:04Z" - latency: 6.02908ms message: 'load-balancer-api-external: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:32:04Z" - latency: 7.581955ms message: 'load-balancer-api-external: resolved host name a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:32:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:24:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.ec2.internal uid: c6f9b1a6-4324-4aad-a939-793b8d5729cb resourceVersion: "28263" uid: b7a7e0ed-d795-4a80-a18c-7ab5c8d40364 spec: sourcePod: network-check-source-56d84b9f44-g5vrm targetEndpoint: a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T16:30:04Z" message: 'load-balancer-api-internal: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.451654ms message: 'load-balancer-api-internal: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:36:04Z" - latency: 7.640486ms message: 'load-balancer-api-internal: resolved host name a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:36:04Z" - latency: 5.172636ms message: 'load-balancer-api-internal: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:35:04Z" - latency: 7.190493ms message: 'load-balancer-api-internal: resolved host name a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:35:04Z" - latency: 6.027163ms message: 'load-balancer-api-internal: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:34:04Z" - latency: 8.461834ms message: 'load-balancer-api-internal: resolved host name a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:34:04Z" - latency: 6.077524ms message: 'load-balancer-api-internal: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:33:04Z" - latency: 6.815031ms message: 'load-balancer-api-internal: resolved host name a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:33:04Z" - latency: 6.014421ms message: 'load-balancer-api-internal: tcp connection to a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:32:04Z" - latency: 7.566193ms message: 'load-balancer-api-internal: resolved host name a05f3fba995c44eada1096c771f038bf-0fbff206983cc039.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:32:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:24:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-network-check-target-ip-10-0-128-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.ec2.internal uid: c6f9b1a6-4324-4aad-a939-793b8d5729cb resourceVersion: "29804" uid: 596af8e8-ce87-4cae-a53a-a0fe6334a6d1 spec: sourcePod: network-check-source-56d84b9f44-g5vrm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T16:31:04Z" message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.19812ms message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:38:04Z" - latency: 1.950297ms message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:37:04Z" - latency: 2.257749ms message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:36:04Z" - latency: 2.163784ms message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:35:04Z" - latency: 1.915604ms message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:34:04Z" - latency: 2.076002ms message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:33:04Z" - latency: 2.122173ms message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:32:04Z" - latency: 2.438783ms message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:31:04Z" - latency: 2.027537ms message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:30:04Z" - latency: 2.125605ms message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:29:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:24:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-network-check-target-ip-10-0-139-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.ec2.internal uid: c6f9b1a6-4324-4aad-a939-793b8d5729cb resourceVersion: "29803" uid: 6e65f8a8-ef80-496f-b88c-a7b3f8218db2 spec: sourcePod: network-check-source-56d84b9f44-g5vrm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T16:31:04Z" message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.741µs message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:38:04Z" - latency: 1.265764ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:37:04Z" - latency: 897.988µs message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:36:04Z" - latency: 1.000132ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:35:04Z" - latency: 869.982µs message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:34:04Z" - latency: 1.212058ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:33:04Z" - latency: 962.142µs message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:32:04Z" - latency: 1.549526ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:31:04Z" - latency: 1.245639ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:30:04Z" - latency: 912.638µs message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:29:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:24:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-network-check-target-ip-10-0-143-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.ec2.internal uid: c6f9b1a6-4324-4aad-a939-793b8d5729cb resourceVersion: "29805" uid: bdc8f90a-dd2e-4540-93cb-fcd05bf907f2 spec: sourcePod: network-check-source-56d84b9f44-g5vrm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T16:31:04Z" message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.983503ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:38:04Z" - latency: 1.933007ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:37:04Z" - latency: 2.204579ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:36:04Z" - latency: 1.729852ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:35:04Z" - latency: 1.933994ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:34:04Z" - latency: 1.777413ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:33:04Z" - latency: 1.786146ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:32:04Z" - latency: 2.49397ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:31:04Z" - latency: 1.76862ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:30:04Z" - latency: 1.800912ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:29:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:24:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.ec2.internal uid: c6f9b1a6-4324-4aad-a939-793b8d5729cb resourceVersion: "28261" uid: bb07c8ff-9111-4bb9-8850-cce94166b3dd spec: sourcePod: network-check-source-56d84b9f44-g5vrm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T16:30:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.64µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:36:04Z" - latency: 2.04514ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T16:36:04Z" - latency: 898.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:35:04Z" - latency: 1.7239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T16:35:04Z" - latency: 888.333µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:34:04Z" - latency: 1.904627ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T16:34:04Z" - latency: 1.063654ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:33:04Z" - latency: 1.666878ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T16:33:04Z" - latency: 968.752µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:32:04Z" - latency: 1.763973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T16:32:04Z" kind: List metadata: resourceVersion: ""