apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T03:51:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-206-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-206.ec2.internal uid: d5622b3c-e0ef-4509-9c5e-b8bc3a862f92 resourceVersion: "31018" uid: 6389e7f0-b099-4358-8440-9f7077e5ae99 spec: sourcePod: network-check-source-6947749cfc-lbtld targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-13T03:58:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.001662ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:05:12Z" - latency: 969.494µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:04:12Z" - latency: 746.324µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:03:12Z" - latency: 750.069µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:02:12Z" - latency: 1.438033ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:01:12Z" - latency: 1.037843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:00:12Z" - latency: 826.694µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:59:12Z" - latency: 995.45µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:58:12Z" - latency: 829.639µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:57:12Z" - latency: 1.376148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:56:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T03:51:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-206-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-206.ec2.internal uid: d5622b3c-e0ef-4509-9c5e-b8bc3a862f92 resourceVersion: "29733" uid: 1f8768cd-032e-4338-bb3c-2f5a12ce5b5a spec: sourcePod: network-check-source-6947749cfc-lbtld targetEndpoint: ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-13T03:57:12Z" message: 'load-balancer-api-external: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.636277ms message: 'load-balancer-api-external: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:03:12Z" - latency: 7.367672ms message: 'load-balancer-api-external: resolved host name ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T04:03:12Z" - latency: 5.256368ms message: 'load-balancer-api-external: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:02:12Z" - latency: 7.145523ms message: 'load-balancer-api-external: resolved host name ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T04:02:12Z" - latency: 5.019236ms message: 'load-balancer-api-external: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:01:12Z" - latency: 5.823157ms message: 'load-balancer-api-external: resolved host name ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T04:01:12Z" - latency: 4.379689ms message: 'load-balancer-api-external: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:00:12Z" - latency: 6.436216ms message: 'load-balancer-api-external: resolved host name ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T04:00:12Z" - latency: 4.882717ms message: 'load-balancer-api-external: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:59:12Z" - latency: 6.354869ms message: 'load-balancer-api-external: resolved host name ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T03:59:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T03:51:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-206-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-206.ec2.internal uid: d5622b3c-e0ef-4509-9c5e-b8bc3a862f92 resourceVersion: "29732" uid: 66993084-8dcb-4cbe-8d44-00c0e7dbfab1 spec: sourcePod: network-check-source-6947749cfc-lbtld targetEndpoint: ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-13T03:57:12Z" message: 'load-balancer-api-internal: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.628649ms message: 'load-balancer-api-internal: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:03:12Z" - latency: 7.31813ms message: 'load-balancer-api-internal: resolved host name ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T04:03:12Z" - latency: 6.037702ms message: 'load-balancer-api-internal: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:02:12Z" - latency: 7.08391ms message: 'load-balancer-api-internal: resolved host name ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T04:02:12Z" - latency: 5.036334ms message: 'load-balancer-api-internal: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:01:12Z" - latency: 5.895817ms message: 'load-balancer-api-internal: resolved host name ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T04:01:12Z" - latency: 3.926988ms message: 'load-balancer-api-internal: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:00:12Z" - latency: 6.529048ms message: 'load-balancer-api-internal: resolved host name ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T04:00:12Z" - latency: 4.889737ms message: 'load-balancer-api-internal: tcp connection to ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:59:12Z" - latency: 6.42911ms message: 'load-balancer-api-internal: resolved host name ab4224db27d76492dba2204314bfeecd-b1187fa2fb67d7d7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T03:59:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T03:51:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-206-to-network-check-target-ip-10-0-133-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-206.ec2.internal uid: d5622b3c-e0ef-4509-9c5e-b8bc3a862f92 resourceVersion: "31016" uid: 6c24112e-7a3b-4968-ae52-9eafc54c8c1f spec: sourcePod: network-check-source-6947749cfc-lbtld targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-13T03:58:12Z" message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.289593ms message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:05:12Z" - latency: 817.767µs message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:04:12Z" - latency: 800.356µs message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:03:12Z" - latency: 983.947µs message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:02:12Z" - latency: 853.297µs message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:01:12Z" - latency: 890.568µs message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:00:12Z" - latency: 857.431µs message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:59:12Z" - latency: 850.29µs message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:58:12Z" - latency: 791.304µs message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:57:12Z" - latency: 828.092µs message: 'network-check-target-ip-10-0-133-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:56:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T03:51:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-206-to-network-check-target-ip-10-0-137-174 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-206.ec2.internal uid: d5622b3c-e0ef-4509-9c5e-b8bc3a862f92 resourceVersion: "31015" uid: cd6ce2c6-726c-44c4-98c1-2502ebbde661 spec: sourcePod: network-check-source-6947749cfc-lbtld targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-13T03:58:12Z" message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.829165ms message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:05:12Z" - latency: 1.507823ms message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:04:12Z" - latency: 1.791067ms message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:03:12Z" - latency: 1.621924ms message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:02:12Z" - latency: 1.582549ms message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:01:12Z" - latency: 1.862786ms message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:00:12Z" - latency: 1.585136ms message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:59:12Z" - latency: 1.927317ms message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:58:12Z" - latency: 1.905209ms message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:57:12Z" - latency: 1.974663ms message: 'network-check-target-ip-10-0-137-174: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:56:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T03:51:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-206-to-network-check-target-ip-10-0-142-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-206.ec2.internal uid: d5622b3c-e0ef-4509-9c5e-b8bc3a862f92 resourceVersion: "31017" uid: ebed55ab-2a0c-4a4f-b1b1-d38351ed2f8c spec: sourcePod: network-check-source-6947749cfc-lbtld targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-13T03:58:12Z" message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.038844ms message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:05:12Z" - latency: 2.3019ms message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:04:12Z" - latency: 2.119614ms message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:03:12Z" - latency: 2.16135ms message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:02:12Z" - latency: 2.149056ms message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:01:12Z" - latency: 2.133663ms message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:00:12Z" - latency: 1.705284ms message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:59:12Z" - latency: 2.110266ms message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:58:12Z" - latency: 2.201078ms message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:57:12Z" - latency: 2.422612ms message: 'network-check-target-ip-10-0-142-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:56:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T03:51:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-206-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-206.ec2.internal uid: d5622b3c-e0ef-4509-9c5e-b8bc3a862f92 resourceVersion: "29731" uid: 5c517150-163e-467e-8e7d-00e7cb472942 spec: sourcePod: network-check-source-6947749cfc-lbtld targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-13T03:57:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.149µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:03:12Z" - latency: 2.390527ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T04:03:12Z" - latency: 870.695µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:02:12Z" - latency: 1.700653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T04:02:12Z" - latency: 1.007503ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:01:12Z" - latency: 1.667776ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T04:01:12Z" - latency: 954.84µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T04:00:12Z" - latency: 1.595899ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T04:00:12Z" - latency: 852.845µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T03:59:12Z" - latency: 1.756218ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T03:59:12Z" kind: List metadata: resourceVersion: ""