apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: ea920dc2-6c0a-419c-b1c9-f656d196ad2d resourceVersion: "56417" uid: e7ab4a52-ddba-44f7-b764-8f863dfdca7f spec: sourcePod: network-check-source-989f8b8dc-zr2kl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T02:23:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.059465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:16Z" - latency: 1.018753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:16Z" - latency: 1.170502ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:16Z" - latency: 1.177824ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:16Z" - latency: 1.090857ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:47:16Z" - latency: 1.337114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:46:16Z" - latency: 1.070654ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:45:16Z" - latency: 1.155261ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:44:16Z" - latency: 938.601µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:43:16Z" - latency: 867.621µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:42:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: ea920dc2-6c0a-419c-b1c9-f656d196ad2d resourceVersion: "57298" uid: 2ac97069-27da-4ef3-8572-8eb3208a58b9 spec: sourcePod: network-check-source-989f8b8dc-zr2kl targetEndpoint: a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T02:22:16Z" message: 'load-balancer-api-external: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.811471ms message: 'load-balancer-api-external: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:52:16Z" - latency: 8.496674ms message: 'load-balancer-api-external: resolved host name a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:52:16Z" - latency: 3.940839ms message: 'load-balancer-api-external: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:16Z" - latency: 8.378501ms message: 'load-balancer-api-external: resolved host name a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:51:16Z" - latency: 4.540085ms message: 'load-balancer-api-external: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:16Z" - latency: 8.36368ms message: 'load-balancer-api-external: resolved host name a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:50:16Z" - latency: 5.173824ms message: 'load-balancer-api-external: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:16Z" - latency: 6.925602ms message: 'load-balancer-api-external: resolved host name a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:49:16Z" - latency: 4.929448ms message: 'load-balancer-api-external: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:16Z" - latency: 9.842588ms message: 'load-balancer-api-external: resolved host name a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:48:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: ea920dc2-6c0a-419c-b1c9-f656d196ad2d resourceVersion: "57300" uid: ba2546de-0ba1-4567-ada6-deb45ca16bc7 spec: sourcePod: network-check-source-989f8b8dc-zr2kl targetEndpoint: a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T02:22:16Z" message: 'load-balancer-api-internal: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.32366ms message: 'load-balancer-api-internal: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:52:16Z" - latency: 8.556183ms message: 'load-balancer-api-internal: resolved host name a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:52:16Z" - latency: 3.890859ms message: 'load-balancer-api-internal: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:16Z" - latency: 8.491248ms message: 'load-balancer-api-internal: resolved host name a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:51:16Z" - latency: 4.545488ms message: 'load-balancer-api-internal: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:16Z" - latency: 8.406195ms message: 'load-balancer-api-internal: resolved host name a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:50:16Z" - latency: 4.750142ms message: 'load-balancer-api-internal: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:16Z" - latency: 6.99972ms message: 'load-balancer-api-internal: resolved host name a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:49:16Z" - latency: 4.601195ms message: 'load-balancer-api-internal: tcp connection to a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:16Z" - latency: 9.884788ms message: 'load-balancer-api-internal: resolved host name a2c9e915a0d4e489aaf1bd89bfa160cd-589fd589b6fce124.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:48:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-network-check-target-ip-10-0-129-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: ea920dc2-6c0a-419c-b1c9-f656d196ad2d resourceVersion: "56416" uid: df46e5da-f971-4e9d-97f3-670e3ea143a2 spec: sourcePod: network-check-source-989f8b8dc-zr2kl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:23:16Z" message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.169151ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:16Z" - latency: 2.389131ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:16Z" - latency: 2.01731ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:16Z" - latency: 2.334673ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:16Z" - latency: 2.656406ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:47:16Z" - latency: 2.154385ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:46:16Z" - latency: 2.355855ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:45:16Z" - latency: 2.209097ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:44:16Z" - latency: 2.361775ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:43:16Z" - latency: 2.409737ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:42:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-network-check-target-ip-10-0-141-30 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: ea920dc2-6c0a-419c-b1c9-f656d196ad2d resourceVersion: "56415" uid: 2b0612ad-3d8d-4cff-b871-eacffb6fe7bb spec: sourcePod: network-check-source-989f8b8dc-zr2kl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:23:16Z" message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.729217ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:16Z" - latency: 2.393481ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:16Z" - latency: 2.306793ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:16Z" - latency: 2.317345ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:16Z" - latency: 2.476491ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:47:16Z" - latency: 2.377839ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:46:16Z" - latency: 2.565509ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:45:16Z" - latency: 2.226656ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:44:16Z" - latency: 2.352585ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:43:16Z" - latency: 2.41637ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:42:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-network-check-target-ip-10-0-143-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: ea920dc2-6c0a-419c-b1c9-f656d196ad2d resourceVersion: "56414" uid: a4db7ed8-f5f0-4e59-af03-c48356b559c7 spec: sourcePod: network-check-source-989f8b8dc-zr2kl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:23:16Z" message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.286662ms message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:16Z" - latency: 1.302977ms message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:16Z" - latency: 1.355405ms message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:16Z" - latency: 1.403958ms message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:16Z" - latency: 856.772µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:47:16Z" - latency: 1.510992ms message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:46:16Z" - latency: 869.089µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:45:16Z" - latency: 875.101µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:44:16Z" - latency: 889.227µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:43:16Z" - latency: 826.175µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:42:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:16:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: ea920dc2-6c0a-419c-b1c9-f656d196ad2d resourceVersion: "57293" uid: 6e98ff7f-dc32-4d68-aaa6-2c4df4a2430c spec: sourcePod: network-check-source-989f8b8dc-zr2kl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T02:22:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 839.686µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:52:16Z" - latency: 1.58839ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:52:16Z" - latency: 1.001341ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:16Z" - latency: 1.771531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:51:16Z" - latency: 803.273µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:16Z" - latency: 1.925038ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:50:16Z" - latency: 1.019436ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:16Z" - latency: 1.863446ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:49:16Z" - latency: 906.835µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:16Z" - latency: 2.067119ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:48:16Z" kind: List metadata: resourceVersion: ""