apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:14:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-97-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-97.ec2.internal uid: 777dbdfd-4721-4d3b-a713-55937f719ee1 resourceVersion: "44153" uid: 8d2e5832-aca4-4988-9f9f-345c85a8a593 spec: sourcePod: network-check-source-7f44b6dd87-7lgw5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-27T20:21:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.697µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:39Z" - latency: 819.76µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:39Z" - latency: 1.00835ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:40:39Z" - latency: 968.273µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:39:39Z" - latency: 988.221µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:39Z" - latency: 922.968µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:39Z" - latency: 1.305064ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:39Z" - latency: 983.858µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:39Z" - latency: 1.095619ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:39Z" - latency: 922.591µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:33:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:14:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-97-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-97.ec2.internal uid: 777dbdfd-4721-4d3b-a713-55937f719ee1 resourceVersion: "39788" uid: 81797b0c-56f1-4012-a662-d184b5de625d spec: sourcePod: network-check-source-7f44b6dd87-7lgw5 targetEndpoint: a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T20:20:39Z" message: 'load-balancer-api-external: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.054068ms message: 'load-balancer-api-external: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:39Z" - latency: 8.093249ms message: 'load-balancer-api-external: resolved host name a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:38:39Z" - latency: 3.841766ms message: 'load-balancer-api-external: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:39Z" - latency: 8.012975ms message: 'load-balancer-api-external: resolved host name a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:37:39Z" - latency: 4.08136ms message: 'load-balancer-api-external: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:39Z" - latency: 7.648232ms message: 'load-balancer-api-external: resolved host name a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:36:39Z" - latency: 4.182922ms message: 'load-balancer-api-external: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:39Z" - latency: 8.568914ms message: 'load-balancer-api-external: resolved host name a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:35:39Z" - latency: 3.884768ms message: 'load-balancer-api-external: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:39Z" - latency: 7.668395ms message: 'load-balancer-api-external: resolved host name a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:34:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:14:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-97-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-97.ec2.internal uid: 777dbdfd-4721-4d3b-a713-55937f719ee1 resourceVersion: "39789" uid: b349a2bc-15b1-4c92-808e-217d0c0a58e8 spec: sourcePod: network-check-source-7f44b6dd87-7lgw5 targetEndpoint: a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T20:20:39Z" message: 'load-balancer-api-internal: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.214453ms message: 'load-balancer-api-internal: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:39Z" - latency: 7.93105ms message: 'load-balancer-api-internal: resolved host name a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:38:39Z" - latency: 4.194124ms message: 'load-balancer-api-internal: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:39Z" - latency: 7.987875ms message: 'load-balancer-api-internal: resolved host name a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:37:39Z" - latency: 4.422764ms message: 'load-balancer-api-internal: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:39Z" - latency: 7.617475ms message: 'load-balancer-api-internal: resolved host name a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:36:39Z" - latency: 4.124488ms message: 'load-balancer-api-internal: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:39Z" - latency: 8.595009ms message: 'load-balancer-api-internal: resolved host name a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:35:39Z" - latency: 3.707045ms message: 'load-balancer-api-internal: tcp connection to a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:39Z" - latency: 7.576805ms message: 'load-balancer-api-internal: resolved host name a706ed80dd9b5495fb998aff7c93d4c9-f54424c109b0609e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T20:34:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:14:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-97-to-network-check-target-ip-10-0-135-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-97.ec2.internal uid: 777dbdfd-4721-4d3b-a713-55937f719ee1 resourceVersion: "44150" uid: f8736b98-4a3c-42a1-b945-80bd0d7b18bf spec: sourcePod: network-check-source-7f44b6dd87-7lgw5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T20:21:39Z" message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.202299ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:39Z" - latency: 1.74206ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:39Z" - latency: 1.712812ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:40:39Z" - latency: 1.693024ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:39:39Z" - latency: 1.990813ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:39Z" - latency: 1.834828ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:39Z" - latency: 1.835545ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:39Z" - latency: 2.050236ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:39Z" - latency: 2.123798ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:39Z" - latency: 1.808564ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:33:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:14:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-97-to-network-check-target-ip-10-0-141-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-97.ec2.internal uid: 777dbdfd-4721-4d3b-a713-55937f719ee1 resourceVersion: "44149" uid: 96494aa7-7bef-422f-ba15-9bbfda0b1df8 spec: sourcePod: network-check-source-7f44b6dd87-7lgw5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T20:21:39Z" message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.274318ms message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:39Z" - latency: 1.175911ms message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:39Z" - latency: 835.063µs message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:40:39Z" - latency: 1.109163ms message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:39:39Z" - latency: 1.089291ms message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:39Z" - latency: 915.387µs message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:39Z" - latency: 882.323µs message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:39Z" - latency: 1.214396ms message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:39Z" - latency: 1.299019ms message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:39Z" - latency: 767.696µs message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:33:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:14:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-97-to-network-check-target-ip-10-0-142-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-97.ec2.internal uid: 777dbdfd-4721-4d3b-a713-55937f719ee1 resourceVersion: "44151" uid: d847b124-615b-4508-9b59-91a0c4ee63f2 spec: sourcePod: network-check-source-7f44b6dd87-7lgw5 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T20:21:39Z" message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.418411ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:42:39Z" - latency: 2.410541ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:41:39Z" - latency: 2.578191ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:40:39Z" - latency: 2.138499ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:39:39Z" - latency: 4.577481ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:39Z" - latency: 1.904766ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:39Z" - latency: 1.899102ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:39Z" - latency: 2.5044ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:39Z" - latency: 1.972808ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:39Z" - latency: 2.459362ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:33:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T20:14:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-97-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-97.ec2.internal uid: 777dbdfd-4721-4d3b-a713-55937f719ee1 resourceVersion: "39786" uid: 36f11676-090d-4ecf-ab30-a2be3053ffc6 spec: sourcePod: network-check-source-7f44b6dd87-7lgw5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-27T20:20:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 834.906µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:38:39Z" - latency: 1.84768ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T20:38:39Z" - latency: 1.003058ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:37:39Z" - latency: 1.678674ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T20:37:39Z" - latency: 982.959µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:36:39Z" - latency: 1.810878ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T20:36:39Z" - latency: 796.102µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:35:39Z" - latency: 2.06213ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T20:35:39Z" - latency: 1.190616ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T20:34:39Z" - latency: 1.47315ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T20:34:39Z" kind: List metadata: resourceVersion: ""