apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T13:35:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 352f56a7-84d7-4ce9-b0dd-cad7d297db57 resourceVersion: "35626" uid: 4f5467f4-dc7b-468b-906a-284ec3ddbd34 spec: sourcePod: network-check-source-8894fc9bd-mtqqq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T13:42:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.149255ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:56:06Z" - latency: 1.045631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:55:06Z" - latency: 1.116339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:54:06Z" - latency: 1.139818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:53:06Z" - latency: 908.495µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:52:06Z" - latency: 1.432074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:51:06Z" - latency: 894.115µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:50:06Z" - latency: 911.3µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:49:06Z" - latency: 1.063782ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:48:06Z" - latency: 1.064869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:47:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T13:35:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 352f56a7-84d7-4ce9-b0dd-cad7d297db57 resourceVersion: "38332" uid: 6e2caa98-fda8-45e9-b6d6-a72266d1a362 spec: sourcePod: network-check-source-8894fc9bd-mtqqq targetEndpoint: a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T13:41:06Z" message: 'load-balancer-api-external: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.51185ms message: 'load-balancer-api-external: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:59:06Z" - latency: 8.206459ms message: 'load-balancer-api-external: resolved host name a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T13:59:06Z" - latency: 3.835314ms message: 'load-balancer-api-external: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:58:06Z" - latency: 6.682666ms message: 'load-balancer-api-external: resolved host name a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T13:58:06Z" - latency: 4.399951ms message: 'load-balancer-api-external: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:57:06Z" - latency: 6.833433ms message: 'load-balancer-api-external: resolved host name a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T13:57:06Z" - latency: 4.098841ms message: 'load-balancer-api-external: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:56:06Z" - latency: 6.382751ms message: 'load-balancer-api-external: resolved host name a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T13:56:06Z" - latency: 4.429496ms message: 'load-balancer-api-external: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:55:06Z" - latency: 6.416173ms message: 'load-balancer-api-external: resolved host name a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T13:55:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T13:35:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 352f56a7-84d7-4ce9-b0dd-cad7d297db57 resourceVersion: "38333" uid: 45d9d449-6051-4746-8326-da060991f5e8 spec: sourcePod: network-check-source-8894fc9bd-mtqqq targetEndpoint: a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T13:41:06Z" message: 'load-balancer-api-internal: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.099034ms message: 'load-balancer-api-internal: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:59:06Z" - latency: 8.152583ms message: 'load-balancer-api-internal: resolved host name a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T13:59:06Z" - latency: 3.763918ms message: 'load-balancer-api-internal: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:58:06Z" - latency: 6.805921ms message: 'load-balancer-api-internal: resolved host name a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T13:58:06Z" - latency: 4.410786ms message: 'load-balancer-api-internal: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:57:06Z" - latency: 6.78012ms message: 'load-balancer-api-internal: resolved host name a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T13:57:06Z" - latency: 4.117179ms message: 'load-balancer-api-internal: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:56:06Z" - latency: 6.485519ms message: 'load-balancer-api-internal: resolved host name a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T13:56:06Z" - latency: 4.25033ms message: 'load-balancer-api-internal: tcp connection to a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:55:06Z" - latency: 6.333352ms message: 'load-balancer-api-internal: resolved host name a46bb105318e2474d92430c9e71fcd65-7fa8c04388e4fd8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T13:55:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T13:35:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-network-check-target-ip-10-0-132-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 352f56a7-84d7-4ce9-b0dd-cad7d297db57 resourceVersion: "35624" uid: e7dd1044-f1a9-473e-a6aa-0612bb1a74f9 spec: sourcePod: network-check-source-8894fc9bd-mtqqq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T13:42:06Z" message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 980.692µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:56:06Z" - latency: 963.526µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:55:06Z" - latency: 774.683µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:54:06Z" - latency: 800.257µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:53:06Z" - latency: 855.712µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:52:06Z" - latency: 1.439205ms message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:51:06Z" - latency: 878.653µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:50:06Z" - latency: 934.398µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:49:06Z" - latency: 1.012066ms message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:48:06Z" - latency: 854.004µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:47:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T13:35:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-network-check-target-ip-10-0-133-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 352f56a7-84d7-4ce9-b0dd-cad7d297db57 resourceVersion: "35623" uid: e2049a85-ae79-48bf-8ca3-07e2366da3ed spec: sourcePod: network-check-source-8894fc9bd-mtqqq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T13:42:06Z" message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.687834ms message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:56:06Z" - latency: 1.886704ms message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:55:06Z" - latency: 1.917994ms message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:54:06Z" - latency: 1.928886ms message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:53:06Z" - latency: 1.775002ms message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:52:06Z" - latency: 2.145222ms message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:51:06Z" - latency: 1.638072ms message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:50:06Z" - latency: 1.846254ms message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:49:06Z" - latency: 1.89945ms message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:48:06Z" - latency: 1.873714ms message: 'network-check-target-ip-10-0-133-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:47:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T13:35:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-network-check-target-ip-10-0-142-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 352f56a7-84d7-4ce9-b0dd-cad7d297db57 resourceVersion: "35625" uid: 1b6b82cd-37c9-4f80-8bbf-2537d2c35c79 spec: sourcePod: network-check-source-8894fc9bd-mtqqq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T13:42:06Z" message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.972766ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:56:06Z" - latency: 2.335ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:55:06Z" - latency: 2.307664ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:54:06Z" - latency: 2.136311ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:53:06Z" - latency: 2.072359ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:52:06Z" - latency: 2.39338ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:51:06Z" - latency: 2.233551ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:50:06Z" - latency: 1.898726ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:49:06Z" - latency: 2.168123ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:48:06Z" - latency: 2.332948ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:47:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T13:35:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 352f56a7-84d7-4ce9-b0dd-cad7d297db57 resourceVersion: "38331" uid: 69293ddb-0a1f-46ae-8468-828069dc55f8 spec: sourcePod: network-check-source-8894fc9bd-mtqqq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T13:41:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 947.863µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:59:06Z" - latency: 1.703732ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T13:59:06Z" - latency: 836.053µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:58:06Z" - latency: 1.696052ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T13:58:06Z" - latency: 977.025µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:57:06Z" - latency: 1.73873ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T13:57:06Z" - latency: 1.025319ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:56:06Z" - latency: 1.594855ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T13:56:06Z" - latency: 1.053671ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T13:55:06Z" - latency: 2.01281ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T13:55:06Z" kind: List metadata: resourceVersion: ""