apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T09:34:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-139-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-139.ec2.internal uid: 911d995c-fb6c-4586-a63e-aae58fbaab3a resourceVersion: "18948" uid: c3ecb1c5-6a71-4811-ac1a-3f7969a65177 spec: sourcePod: network-check-source-7f44b6dd87-fwztx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T09:41:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013375ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:55:11Z" - latency: 759.063µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:54:11Z" - latency: 1.154063ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:53:11Z" - latency: 1.259539ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:52:11Z" - latency: 911.382µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:51:11Z" - latency: 964.189µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:50:11Z" - latency: 803.311µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:49:11Z" - latency: 1.101071ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:48:11Z" - latency: 877.71µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:47:11Z" - latency: 845.896µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:46:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T09:34:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-139-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-139.ec2.internal uid: 911d995c-fb6c-4586-a63e-aae58fbaab3a resourceVersion: "20109" uid: bdadb9f1-ad7b-4fbc-9147-026d05c7eb2b spec: sourcePod: network-check-source-7f44b6dd87-fwztx targetEndpoint: a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T09:40:11Z" message: 'load-balancer-api-external: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.106315ms message: 'load-balancer-api-external: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:58:11Z" - latency: 7.853808ms message: 'load-balancer-api-external: resolved host name a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T09:58:11Z" - latency: 6.847728ms message: 'load-balancer-api-external: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:57:11Z" - latency: 8.578263ms message: 'load-balancer-api-external: resolved host name a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T09:57:11Z" - latency: 5.494675ms message: 'load-balancer-api-external: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:56:11Z" - latency: 8.891813ms message: 'load-balancer-api-external: resolved host name a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T09:56:11Z" - latency: 4.397595ms message: 'load-balancer-api-external: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:55:11Z" - latency: 8.43992ms message: 'load-balancer-api-external: resolved host name a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T09:55:11Z" - latency: 3.627822ms message: 'load-balancer-api-external: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:54:11Z" - latency: 7.748959ms message: 'load-balancer-api-external: resolved host name a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T09:54:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T09:34:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-139-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-139.ec2.internal uid: 911d995c-fb6c-4586-a63e-aae58fbaab3a resourceVersion: "20108" uid: 55544905-3e23-4c9d-bf4e-aec635cef488 spec: sourcePod: network-check-source-7f44b6dd87-fwztx targetEndpoint: a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T09:40:11Z" message: 'load-balancer-api-internal: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.053957ms message: 'load-balancer-api-internal: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:58:11Z" - latency: 7.906931ms message: 'load-balancer-api-internal: resolved host name a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T09:58:11Z" - latency: 6.925254ms message: 'load-balancer-api-internal: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:57:11Z" - latency: 8.531571ms message: 'load-balancer-api-internal: resolved host name a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T09:57:11Z" - latency: 3.785391ms message: 'load-balancer-api-internal: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:56:11Z" - latency: 8.861544ms message: 'load-balancer-api-internal: resolved host name a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T09:56:11Z" - latency: 5.193035ms message: 'load-balancer-api-internal: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:55:11Z" - latency: 8.353655ms message: 'load-balancer-api-internal: resolved host name a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T09:55:11Z" - latency: 5.610853ms message: 'load-balancer-api-internal: tcp connection to a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:54:11Z" - latency: 7.714611ms message: 'load-balancer-api-internal: resolved host name a365d6ff3e4764c58b50b3bbba276c9d-612db99dbd1676ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T09:54:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T09:34:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-139-to-network-check-target-ip-10-0-128-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-139.ec2.internal uid: 911d995c-fb6c-4586-a63e-aae58fbaab3a resourceVersion: "18946" uid: a3e7cf0b-8133-4891-990c-10f7df3c5a18 spec: sourcePod: network-check-source-7f44b6dd87-fwztx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T09:41:11Z" message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.108051ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:55:11Z" - latency: 2.097596ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:54:11Z" - latency: 1.987608ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:53:11Z" - latency: 2.141322ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:52:11Z" - latency: 2.032516ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:51:11Z" - latency: 2.071227ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:50:11Z" - latency: 1.925367ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:49:11Z" - latency: 2.146363ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:48:11Z" - latency: 2.385786ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:47:11Z" - latency: 2.057362ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:46:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T09:34:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-139-to-network-check-target-ip-10-0-129-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-139.ec2.internal uid: 911d995c-fb6c-4586-a63e-aae58fbaab3a resourceVersion: "18945" uid: 1282ab7f-932e-4669-b38e-8536a11606cc spec: sourcePod: network-check-source-7f44b6dd87-fwztx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T09:41:11Z" message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.213132ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:55:11Z" - latency: 1.468437ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:54:11Z" - latency: 1.127107ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:53:11Z" - latency: 825.924µs message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:52:11Z" - latency: 888.412µs message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:51:11Z" - latency: 929.132µs message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:50:11Z" - latency: 885.776µs message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:49:11Z" - latency: 1.294048ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:48:11Z" - latency: 854.215µs message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:47:11Z" - latency: 798.382µs message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:46:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T09:34:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-139-to-network-check-target-ip-10-0-139-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-139.ec2.internal uid: 911d995c-fb6c-4586-a63e-aae58fbaab3a resourceVersion: "18947" uid: f2249081-f63c-4e12-9483-fa723c0888b5 spec: sourcePod: network-check-source-7f44b6dd87-fwztx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T09:41:11Z" message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.687325ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:55:11Z" - latency: 1.842656ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:54:11Z" - latency: 1.952418ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:53:11Z" - latency: 2.009012ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:52:11Z" - latency: 1.92042ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:51:11Z" - latency: 2.029498ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:50:11Z" - latency: 2.010609ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:49:11Z" - latency: 2.295ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:48:11Z" - latency: 1.944007ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:47:11Z" - latency: 2.250046ms message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:46:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T09:34:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-139-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-139.ec2.internal uid: 911d995c-fb6c-4586-a63e-aae58fbaab3a resourceVersion: "20107" uid: b5f4775f-ba9a-4009-8d83-410537719caa spec: sourcePod: network-check-source-7f44b6dd87-fwztx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T09:40:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 876.892µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:58:11Z" - latency: 1.91399ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T09:58:11Z" - latency: 766.736µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:57:11Z" - latency: 2.182001ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T09:57:11Z" - latency: 1.050022ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:56:11Z" - latency: 1.567824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T09:56:11Z" - latency: 747µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:55:11Z" - latency: 1.719427ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T09:55:11Z" - latency: 866.309µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T09:54:11Z" - latency: 1.908599ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T09:54:11Z" kind: List metadata: resourceVersion: ""