apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:32:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-236-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-236.ec2.internal uid: 1619ba5c-7443-4fd4-8f09-540cd82f05fc resourceVersion: "54969" uid: 97e593d7-0920-4695-89de-a52aaddd4b2f spec: sourcePod: network-check-source-685456655f-sj2fc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-06T19:39:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.008185ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:00:04Z" - latency: 1.488586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:59:04Z" - latency: 1.213269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:58:04Z" - latency: 991.036µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:57:04Z" - latency: 980.852µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:56:04Z" - latency: 1.313466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:55:04Z" - latency: 1.281587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:54:04Z" - latency: 1.413489ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:53:04Z" - latency: 1.297758ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:52:04Z" - latency: 1.062952ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:32:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-236-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-236.ec2.internal uid: 1619ba5c-7443-4fd4-8f09-540cd82f05fc resourceVersion: "56627" uid: ca6de89e-8548-4479-923d-3b9176d7a8bb spec: sourcePod: network-check-source-685456655f-sj2fc targetEndpoint: ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-06T19:38:04Z" message: 'load-balancer-api-external: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.491657ms message: 'load-balancer-api-external: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:02:04Z" - latency: 8.19233ms message: 'load-balancer-api-external: resolved host name ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T20:02:04Z" - latency: 3.468667ms message: 'load-balancer-api-external: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:01:04Z" - latency: 7.055191ms message: 'load-balancer-api-external: resolved host name ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T20:01:04Z" - latency: 6.637645ms message: 'load-balancer-api-external: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:00:04Z" - latency: 7.157899ms message: 'load-balancer-api-external: resolved host name ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T20:00:04Z" - latency: 4.553478ms message: 'load-balancer-api-external: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:59:04Z" - latency: 6.690037ms message: 'load-balancer-api-external: resolved host name ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:59:04Z" - latency: 4.418498ms message: 'load-balancer-api-external: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:58:04Z" - latency: 6.680612ms message: 'load-balancer-api-external: resolved host name ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:58:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:32:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-236-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-236.ec2.internal uid: 1619ba5c-7443-4fd4-8f09-540cd82f05fc resourceVersion: "56626" uid: c548906a-1459-4144-b3fa-2071c3749b0f spec: sourcePod: network-check-source-685456655f-sj2fc targetEndpoint: ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-06T19:38:04Z" message: 'load-balancer-api-internal: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.880496ms message: 'load-balancer-api-internal: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:02:04Z" - latency: 8.135147ms message: 'load-balancer-api-internal: resolved host name ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T20:02:04Z" - latency: 3.472777ms message: 'load-balancer-api-internal: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:01:04Z" - latency: 7.157392ms message: 'load-balancer-api-internal: resolved host name ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T20:01:04Z" - latency: 6.704633ms message: 'load-balancer-api-internal: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:00:04Z" - latency: 7.048937ms message: 'load-balancer-api-internal: resolved host name ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T20:00:04Z" - latency: 4.522935ms message: 'load-balancer-api-internal: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:59:04Z" - latency: 6.728368ms message: 'load-balancer-api-internal: resolved host name ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:59:04Z" - latency: 4.545557ms message: 'load-balancer-api-internal: tcp connection to ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:58:04Z" - latency: 6.575537ms message: 'load-balancer-api-internal: resolved host name ab05e593c065f42999beedfdb55d4901-788c5c3fc98d96d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-06T19:58:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:32:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-236-to-network-check-target-ip-10-0-135-174 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-236.ec2.internal uid: 1619ba5c-7443-4fd4-8f09-540cd82f05fc resourceVersion: "54968" uid: dfcf7456-eb61-4743-bec7-b357654e10e0 spec: sourcePod: network-check-source-685456655f-sj2fc targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-06T19:39:04Z" message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.313184ms message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:00:04Z" - latency: 2.239915ms message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:59:04Z" - latency: 2.080898ms message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:58:04Z" - latency: 2.177394ms message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:57:04Z" - latency: 2.338922ms message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:56:04Z" - latency: 2.113168ms message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:55:04Z" - latency: 2.667766ms message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:54:04Z" - latency: 2.523709ms message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:53:04Z" - latency: 2.431929ms message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:52:04Z" - latency: 2.42605ms message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:32:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-236-to-network-check-target-ip-10-0-135-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-236.ec2.internal uid: 1619ba5c-7443-4fd4-8f09-540cd82f05fc resourceVersion: "54966" uid: df081488-83d0-48d6-a8f5-7d6bcdfc2cd8 spec: sourcePod: network-check-source-685456655f-sj2fc targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-06T19:39:04Z" message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 952.572µs message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:00:04Z" - latency: 982.846µs message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:59:04Z" - latency: 1.071494ms message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:58:04Z" - latency: 1.022361ms message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:57:04Z" - latency: 1.046114ms message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:56:04Z" - latency: 1.32893ms message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:55:04Z" - latency: 1.943695ms message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:54:04Z" - latency: 1.059018ms message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:53:04Z" - latency: 984.527µs message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:52:04Z" - latency: 1.028538ms message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:32:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-236-to-network-check-target-ip-10-0-141-42 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-236.ec2.internal uid: 1619ba5c-7443-4fd4-8f09-540cd82f05fc resourceVersion: "54967" uid: abad0003-3f5e-43bf-aa83-5374ca6416b3 spec: sourcePod: network-check-source-685456655f-sj2fc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-06T19:39:04Z" message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.94429ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:00:04Z" - latency: 2.151429ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:59:04Z" - latency: 2.487727ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:58:04Z" - latency: 2.337107ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:57:04Z" - latency: 2.090759ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:56:04Z" - latency: 2.359285ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:55:04Z" - latency: 2.437842ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:54:04Z" - latency: 2.325628ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:53:04Z" - latency: 2.344538ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:52:04Z" - latency: 2.479605ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-06T19:32:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-236-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-236.ec2.internal uid: 1619ba5c-7443-4fd4-8f09-540cd82f05fc resourceVersion: "56625" uid: cdc1623b-8ce9-458c-9647-824c84fad49f spec: sourcePod: network-check-source-685456655f-sj2fc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-06T19:38:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.02261ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:02:04Z" - latency: 1.801162ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-06T20:02:04Z" - latency: 1.007863ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:01:04Z" - latency: 2.349225ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-06T20:01:04Z" - latency: 1.118247ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-06T20:00:04Z" - latency: 1.914607ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-06T20:00:04Z" - latency: 814.165µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:59:04Z" - latency: 1.990687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-06T19:59:04Z" - latency: 1.478399ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-06T19:58:04Z" - latency: 1.822123ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-06T19:58:04Z" kind: List metadata: resourceVersion: ""