apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: ec680ce9-cb5a-45dc-8f9f-c7d5c353743d resourceVersion: "22216" uid: 91594a9a-4706-4782-9d75-9c051dabd478 spec: sourcePod: network-check-source-869dcfcdcd-tt4pd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T19:10:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 835.198µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:31Z" - latency: 971.475µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:31Z" - latency: 825.988µ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:31Z" - latency: 949.752µ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:31Z" - latency: 1.361098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:31Z" - latency: 1.131739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:31Z" - latency: 864.75µ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:31Z" - latency: 944.787µ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:31Z" - latency: 846.307µ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:31Z" - latency: 1.035763ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: ec680ce9-cb5a-45dc-8f9f-c7d5c353743d resourceVersion: "20799" uid: 2a957598-a842-47bf-bd9a-85c5959600cf spec: sourcePod: network-check-source-869dcfcdcd-tt4pd targetEndpoint: ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T19:09:31Z" message: 'load-balancer-api-external: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.968137ms message: 'load-balancer-api-external: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:31Z" - latency: 8.759544ms message: 'load-balancer-api-external: resolved host name ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:21:31Z" - latency: 4.313642ms message: 'load-balancer-api-external: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:31Z" - latency: 11.182747ms message: 'load-balancer-api-external: resolved host name ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:20:31Z" - latency: 3.599867ms message: 'load-balancer-api-external: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:31Z" - latency: 8.070361ms message: 'load-balancer-api-external: resolved host name ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:19:31Z" - latency: 5.815689ms message: 'load-balancer-api-external: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:31Z" - latency: 8.146764ms message: 'load-balancer-api-external: resolved host name ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:18:31Z" - latency: 3.865186ms message: 'load-balancer-api-external: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:31Z" - latency: 8.590298ms message: 'load-balancer-api-external: resolved host name ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:17:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: ec680ce9-cb5a-45dc-8f9f-c7d5c353743d resourceVersion: "20800" uid: 22fc9bad-36ea-4f2f-9a78-1528ef72c2cd spec: sourcePod: network-check-source-869dcfcdcd-tt4pd targetEndpoint: ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T19:09:31Z" message: 'load-balancer-api-internal: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.973225ms message: 'load-balancer-api-internal: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:31Z" - latency: 8.677927ms message: 'load-balancer-api-internal: resolved host name ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:21:31Z" - latency: 4.319652ms message: 'load-balancer-api-internal: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:31Z" - latency: 11.080867ms message: 'load-balancer-api-internal: resolved host name ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:20:31Z" - latency: 4.154458ms message: 'load-balancer-api-internal: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:31Z" - latency: 7.925348ms message: 'load-balancer-api-internal: resolved host name ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:19:31Z" - latency: 5.815332ms message: 'load-balancer-api-internal: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:31Z" - latency: 8.060012ms message: 'load-balancer-api-internal: resolved host name ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:18:31Z" - latency: 5.076699ms message: 'load-balancer-api-internal: tcp connection to ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:31Z" - latency: 8.520335ms message: 'load-balancer-api-internal: resolved host name ab435f3d94ae04180b4d41766680d3b4-967e6434a954cf21.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:17:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-network-check-target-ip-10-0-131-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: ec680ce9-cb5a-45dc-8f9f-c7d5c353743d resourceVersion: "22213" uid: 7c421cc5-4fb7-4e46-b763-32b23385d38b spec: sourcePod: network-check-source-869dcfcdcd-tt4pd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:10:31Z" message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.478µs message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:31Z" - latency: 1.745171ms message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:31Z" - latency: 862.377µs message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:31Z" - latency: 808.858µs message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:31Z" - latency: 785.488µs message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:31Z" - latency: 1.271181ms message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:31Z" - latency: 969.179µs message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:31Z" - latency: 1.514484ms message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:31Z" - latency: 1.353894ms message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:31Z" - latency: 773.367µs message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-network-check-target-ip-10-0-134-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: ec680ce9-cb5a-45dc-8f9f-c7d5c353743d resourceVersion: "22215" uid: fca3d9fd-a924-4c8d-9c52-264491bf4704 spec: sourcePod: network-check-source-869dcfcdcd-tt4pd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:10:31Z" message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.394328ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:31Z" - latency: 2.755761ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:31Z" - latency: 2.472ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:31Z" - latency: 2.070389ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:31Z" - latency: 2.672765ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:31Z" - latency: 2.464095ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:31Z" - latency: 2.149806ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:31Z" - latency: 2.238369ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:31Z" - latency: 2.201931ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:31Z" - latency: 2.196319ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-network-check-target-ip-10-0-134-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: ec680ce9-cb5a-45dc-8f9f-c7d5c353743d resourceVersion: "22214" uid: a047de51-41d3-480e-bddf-fef29f694e92 spec: sourcePod: network-check-source-869dcfcdcd-tt4pd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:10:31Z" message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.012991ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:31Z" - latency: 2.353539ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:31Z" - latency: 2.145054ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:31Z" - latency: 1.937622ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:31Z" - latency: 2.216279ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:31Z" - latency: 2.542725ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:31Z" - latency: 2.156635ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:31Z" - latency: 2.4201ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:31Z" - latency: 1.9811ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:16:31Z" - latency: 2.262258ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:15:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:03:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-216-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-216.ec2.internal uid: ec680ce9-cb5a-45dc-8f9f-c7d5c353743d resourceVersion: "20798" uid: b3645db0-d542-4316-b66c-24273944e0bc spec: sourcePod: network-check-source-869dcfcdcd-tt4pd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T19:09:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 988.485µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:31Z" - latency: 1.619962ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:21:31Z" - latency: 746.208µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:31Z" - latency: 1.720036ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:20:31Z" - latency: 1.047726ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:31Z" - latency: 1.543821ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:19:31Z" - latency: 839.934µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:31Z" - latency: 1.865951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:18:31Z" - latency: 930.835µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:31Z" - latency: 1.66425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:17:31Z" kind: List metadata: resourceVersion: ""