apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:40:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-247-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-247.ec2.internal uid: 32e0c5f6-48d2-4f9a-813e-aa263c47eb35 resourceVersion: "43835" uid: d4a311f3-d1b7-4a91-8fba-db35d5c2ef50 spec: sourcePod: network-check-source-dbd9cf844-ng5tm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T12:47:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.044693ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:08:14Z" - latency: 778.027µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:07:14Z" - latency: 992.351µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:06:14Z" - latency: 1.144299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:05:14Z" - latency: 1.128675ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:04:14Z" - latency: 1.136384ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:03:14Z" - latency: 1.052511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:02:14Z" - latency: 1.235133ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:01:14Z" - latency: 1.157691ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:00:14Z" - latency: 1.110383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:59:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:40:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-247-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-247.ec2.internal uid: 32e0c5f6-48d2-4f9a-813e-aa263c47eb35 resourceVersion: "46224" uid: 465cbcf4-1932-472e-b261-08c80534697b spec: sourcePod: network-check-source-dbd9cf844-ng5tm targetEndpoint: a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T12:46:14Z" message: 'load-balancer-api-external: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.973721ms message: 'load-balancer-api-external: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:10:14Z" - latency: 7.88695ms message: 'load-balancer-api-external: resolved host name a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:10:14Z" - latency: 5.013997ms message: 'load-balancer-api-external: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:09:14Z" - latency: 12.976079ms message: 'load-balancer-api-external: resolved host name a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:09:14Z" - latency: 4.785633ms message: 'load-balancer-api-external: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:08:14Z" - latency: 12.072672ms message: 'load-balancer-api-external: resolved host name a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:08:14Z" - latency: 4.585929ms message: 'load-balancer-api-external: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:07:14Z" - latency: 12.720355ms message: 'load-balancer-api-external: resolved host name a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:07:14Z" - latency: 3.936078ms message: 'load-balancer-api-external: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:06:14Z" - latency: 13.345653ms message: 'load-balancer-api-external: resolved host name a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:06:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:40:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-247-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-247.ec2.internal uid: 32e0c5f6-48d2-4f9a-813e-aa263c47eb35 resourceVersion: "46225" uid: e6f07adc-7570-4a64-928b-3fc391054806 spec: sourcePod: network-check-source-dbd9cf844-ng5tm targetEndpoint: a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T12:46:14Z" message: 'load-balancer-api-internal: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.728512ms message: 'load-balancer-api-internal: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:10:14Z" - latency: 7.933662ms message: 'load-balancer-api-internal: resolved host name a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:10:14Z" - latency: 5.030958ms message: 'load-balancer-api-internal: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:09:14Z" - latency: 12.864338ms message: 'load-balancer-api-internal: resolved host name a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:09:14Z" - latency: 4.804365ms message: 'load-balancer-api-internal: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:08:14Z" - latency: 12.048544ms message: 'load-balancer-api-internal: resolved host name a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:08:14Z" - latency: 3.781685ms message: 'load-balancer-api-internal: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:07:14Z" - latency: 12.620363ms message: 'load-balancer-api-internal: resolved host name a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:07:14Z" - latency: 3.940586ms message: 'load-balancer-api-internal: tcp connection to a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:06:14Z" - latency: 13.416653ms message: 'load-balancer-api-internal: resolved host name a0ab0ca4a6538410f9bddf6dfeef52c9-86d3037745493a12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:06:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:40:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-247-to-network-check-target-ip-10-0-133-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-247.ec2.internal uid: 32e0c5f6-48d2-4f9a-813e-aa263c47eb35 resourceVersion: "43837" uid: b71ecb9f-97f5-475a-aa6e-3df92cd83681 spec: sourcePod: network-check-source-dbd9cf844-ng5tm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:47:14Z" message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.01707ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:08:14Z" - latency: 2.428385ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:07:14Z" - latency: 1.933668ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:06:14Z" - latency: 2.503008ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:05:14Z" - latency: 2.184519ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:04:14Z" - latency: 2.313191ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:03:14Z" - latency: 2.191003ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:02:14Z" - latency: 2.383344ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:01:14Z" - latency: 2.214129ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:00:14Z" - latency: 2.389896ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:59:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:40:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-247-to-network-check-target-ip-10-0-134-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-247.ec2.internal uid: 32e0c5f6-48d2-4f9a-813e-aa263c47eb35 resourceVersion: "43834" uid: dc3672e0-c5da-4cb0-8a6d-015b8b56435e spec: sourcePod: network-check-source-dbd9cf844-ng5tm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:47:14Z" message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.935653ms message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:08:14Z" - latency: 2.460352ms message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:07:14Z" - latency: 1.963939ms message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:06:14Z" - latency: 2.651357ms message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:05:14Z" - latency: 2.250013ms message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:04:14Z" - latency: 2.080395ms message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:03:14Z" - latency: 2.040626ms message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:02:14Z" - latency: 2.021137ms message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:01:14Z" - latency: 2.213108ms message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:00:14Z" - latency: 2.243566ms message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:59:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:40:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-247-to-network-check-target-ip-10-0-136-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-247.ec2.internal uid: 32e0c5f6-48d2-4f9a-813e-aa263c47eb35 resourceVersion: "43836" uid: 41dbc7a8-dda4-4da9-a871-c68021cc2980 spec: sourcePod: network-check-source-dbd9cf844-ng5tm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:47:14Z" message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.778µs message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:08:14Z" - latency: 801.12µs message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:07:14Z" - latency: 871.347µs message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:06:14Z" - latency: 912.925µs message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:05:14Z" - latency: 733.615µs message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:04:14Z" - latency: 941.9µs message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:03:14Z" - latency: 879.059µs message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:02:14Z" - latency: 884.543µs message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:01:14Z" - latency: 906.827µs message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:00:14Z" - latency: 896.067µs message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:59:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:40:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-247-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-247.ec2.internal uid: 32e0c5f6-48d2-4f9a-813e-aa263c47eb35 resourceVersion: "46223" uid: 9b8a0a89-cbf1-425a-8efd-4b7dde3528b9 spec: sourcePod: network-check-source-dbd9cf844-ng5tm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T12:46:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 793.139µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:10:14Z" - latency: 1.594105ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:10:14Z" - latency: 806.681µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:09:14Z" - latency: 1.922425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:09:14Z" - latency: 873.413µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:08:14Z" - latency: 1.970755ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:08:14Z" - latency: 1.003656ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:07:14Z" - latency: 1.5806ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:07:14Z" - latency: 1.074849ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:06:14Z" - latency: 1.766293ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:06:14Z" kind: List metadata: resourceVersion: ""