apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:07:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.ec2.internal uid: 4a4523cb-b2ac-4132-b0c2-31ca4fd3bcad resourceVersion: "39538" uid: ecda2cf0-d5c1-4e26-8eed-a5c265f19a26 spec: sourcePod: network-check-source-7b678d77c7-rqrcp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T16:14:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.621883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:38Z" - latency: 911.939µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:38Z" - latency: 1.560455ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:38Z" - latency: 980.083µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:38Z" - latency: 882.755µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:38Z" - latency: 1.164641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:38Z" - latency: 1.31848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:57:38Z" - latency: 1.02081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:56:38Z" - latency: 1.056553ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:55:38Z" - latency: 945.602µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:54:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:07:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.ec2.internal uid: 4a4523cb-b2ac-4132-b0c2-31ca4fd3bcad resourceVersion: "38430" uid: f935c51e-b809-48a9-9fea-8860f3331e6b spec: sourcePod: network-check-source-7b678d77c7-rqrcp targetEndpoint: a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:13:38Z" message: 'load-balancer-api-external: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.023728ms message: 'load-balancer-api-external: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:38Z" - latency: 6.477627ms message: 'load-balancer-api-external: resolved host name a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:01:38Z" - latency: 4.460049ms message: 'load-balancer-api-external: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:38Z" - latency: 6.096184ms message: 'load-balancer-api-external: resolved host name a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:00:38Z" - latency: 4.455049ms message: 'load-balancer-api-external: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:38Z" - latency: 6.318922ms message: 'load-balancer-api-external: resolved host name a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:59:38Z" - latency: 5.146787ms message: 'load-balancer-api-external: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:38Z" - latency: 10.103627ms message: 'load-balancer-api-external: resolved host name a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:58:38Z" - latency: 4.637762ms message: 'load-balancer-api-external: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:57:38Z" - latency: 5.582749ms message: 'load-balancer-api-external: resolved host name a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:57:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:07:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.ec2.internal uid: 4a4523cb-b2ac-4132-b0c2-31ca4fd3bcad resourceVersion: "38431" uid: f03e721b-46f7-4fc7-b909-d24e992a5103 spec: sourcePod: network-check-source-7b678d77c7-rqrcp targetEndpoint: a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:13:38Z" message: 'load-balancer-api-internal: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.112056ms message: 'load-balancer-api-internal: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:38Z" - latency: 6.449725ms message: 'load-balancer-api-internal: resolved host name a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:01:38Z" - latency: 4.423344ms message: 'load-balancer-api-internal: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:38Z" - latency: 6.174056ms message: 'load-balancer-api-internal: resolved host name a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:00:38Z" - latency: 4.429257ms message: 'load-balancer-api-internal: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:38Z" - latency: 6.426318ms message: 'load-balancer-api-internal: resolved host name a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:59:38Z" - latency: 5.403195ms message: 'load-balancer-api-internal: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:38Z" - latency: 10.029755ms message: 'load-balancer-api-internal: resolved host name a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:58:38Z" - latency: 4.639187ms message: 'load-balancer-api-internal: tcp connection to a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:57:38Z" - latency: 5.629695ms message: 'load-balancer-api-internal: resolved host name a77e534a4d5f54793b02d00cd227e29c-9e63b65a7b5bc836.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:57:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:07:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-network-check-target-ip-10-0-130-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.ec2.internal uid: 4a4523cb-b2ac-4132-b0c2-31ca4fd3bcad resourceVersion: "39537" uid: a162aed6-50f3-4314-bb1b-c2d973bf2db1 spec: sourcePod: network-check-source-7b678d77c7-rqrcp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:14:38Z" message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.13545ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:38Z" - latency: 2.002496ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:38Z" - latency: 1.854643ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:38Z" - latency: 2.010064ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:38Z" - latency: 1.983684ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:38Z" - latency: 1.786777ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:38Z" - latency: 1.954626ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:57:38Z" - latency: 2.115834ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:56:38Z" - latency: 1.706973ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:55:38Z" - latency: 2.306509ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:54:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:07:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-network-check-target-ip-10-0-137-150 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.ec2.internal uid: 4a4523cb-b2ac-4132-b0c2-31ca4fd3bcad resourceVersion: "39535" uid: 7b14c0db-c89a-4b81-9881-9def65091351 spec: sourcePod: network-check-source-7b678d77c7-rqrcp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:14:38Z" message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 712.511µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:38Z" - latency: 764.093µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:38Z" - latency: 751.153µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:38Z" - latency: 781.519µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:38Z" - latency: 1.328818ms message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:38Z" - latency: 807.935µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:38Z" - latency: 721.991µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:57:38Z" - latency: 745.878µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:56:38Z" - latency: 1.158938ms message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:55:38Z" - latency: 794.096µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:54:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:07:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-network-check-target-ip-10-0-143-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.ec2.internal uid: 4a4523cb-b2ac-4132-b0c2-31ca4fd3bcad resourceVersion: "39536" uid: 551d2b8c-c051-4ff4-a002-eb755f761220 spec: sourcePod: network-check-source-7b678d77c7-rqrcp targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:14:38Z" message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.910153ms message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:38Z" - latency: 1.80253ms message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:38Z" - latency: 1.756271ms message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:38Z" - latency: 1.690263ms message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:38Z" - latency: 1.790209ms message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:38Z" - latency: 1.521568ms message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:38Z" - latency: 1.762081ms message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:57:38Z" - latency: 1.912698ms message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:56:38Z" - latency: 1.683996ms message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:55:38Z" - latency: 1.738377ms message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:54:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:07:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.ec2.internal uid: 4a4523cb-b2ac-4132-b0c2-31ca4fd3bcad resourceVersion: "38429" uid: 953ea8b9-9b30-475e-a251-eac82356c9af spec: sourcePod: network-check-source-7b678d77c7-rqrcp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T16:13:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.023773ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:38Z" - latency: 2.085295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:01:38Z" - latency: 1.102116ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:38Z" - latency: 1.588782ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:00:38Z" - latency: 978.784µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:38Z" - latency: 1.763773ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:59:38Z" - latency: 1.085095ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:38Z" - latency: 1.582241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:58:38Z" - latency: 1.036036ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:57:38Z" - latency: 1.534757ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:57:38Z" kind: List metadata: resourceVersion: ""