apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T19:27:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 1d46b1ff-d12a-4955-ba06-d73e2fb9188c resourceVersion: "75744" uid: a6e02006-85b3-4d7f-abef-c06a2ee74293 spec: sourcePod: network-check-source-65bdbbff45-pgm6p targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T19:34:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.11721ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:23:42Z" - latency: 1.046284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:22:42Z" - latency: 1.316143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:21:42Z" - latency: 1.216689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:20:42Z" - latency: 1.333876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:19:42Z" - latency: 1.266469ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:18:42Z" - latency: 935.475µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:17:42Z" - latency: 1.796811ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:16:42Z" - latency: 1.191322ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:15:42Z" - latency: 1.201326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:14:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T19:27:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 1d46b1ff-d12a-4955-ba06-d73e2fb9188c resourceVersion: "79696" uid: cd244d05-c7ba-4dec-b78f-1973d1f63390 spec: sourcePod: network-check-source-65bdbbff45-pgm6p targetEndpoint: adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T19:33:42Z" message: 'load-balancer-api-external: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.242977ms message: 'load-balancer-api-external: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:27:42Z" - latency: 12.83915ms message: 'load-balancer-api-external: resolved host name adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T20:27:42Z" - latency: 5.80883ms message: 'load-balancer-api-external: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:26:42Z" - latency: 7.299785ms message: 'load-balancer-api-external: resolved host name adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T20:26:42Z" - latency: 4.899689ms message: 'load-balancer-api-external: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:25:42Z" - latency: 6.778463ms message: 'load-balancer-api-external: resolved host name adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T20:25:42Z" - latency: 4.785142ms message: 'load-balancer-api-external: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:24:42Z" - latency: 10.909264ms message: 'load-balancer-api-external: resolved host name adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T20:24:42Z" - latency: 5.531328ms message: 'load-balancer-api-external: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:23:42Z" - latency: 7.147288ms message: 'load-balancer-api-external: resolved host name adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T20:23:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T19:27:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 1d46b1ff-d12a-4955-ba06-d73e2fb9188c resourceVersion: "79697" uid: 6ef80fcc-a16a-453f-ae18-bb3bbd070be0 spec: sourcePod: network-check-source-65bdbbff45-pgm6p targetEndpoint: adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T19:33:42Z" message: 'load-balancer-api-internal: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.24887ms message: 'load-balancer-api-internal: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:27:42Z" - latency: 12.885903ms message: 'load-balancer-api-internal: resolved host name adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T20:27:42Z" - latency: 5.653505ms message: 'load-balancer-api-internal: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:26:42Z" - latency: 7.369774ms message: 'load-balancer-api-internal: resolved host name adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T20:26:42Z" - latency: 4.808271ms message: 'load-balancer-api-internal: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:25:42Z" - latency: 6.855722ms message: 'load-balancer-api-internal: resolved host name adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T20:25:42Z" - latency: 4.770457ms message: 'load-balancer-api-internal: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:24:42Z" - latency: 10.944666ms message: 'load-balancer-api-internal: resolved host name adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T20:24:42Z" - latency: 3.843768ms message: 'load-balancer-api-internal: tcp connection to adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:23:42Z" - latency: 7.20285ms message: 'load-balancer-api-internal: resolved host name adf27e91709934bebb3ab32943703877-9e8fc46d155cc9ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T20:23:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T19:27:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-network-check-target-ip-10-0-129-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 1d46b1ff-d12a-4955-ba06-d73e2fb9188c resourceVersion: "75743" uid: bc5342c9-c3a2-42ca-b666-1a20c211f2fa spec: sourcePod: network-check-source-65bdbbff45-pgm6p targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T19:34:42Z" message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.141615ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:23:42Z" - latency: 2.107152ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:22:42Z" - latency: 2.555471ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:21:42Z" - latency: 2.714479ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:20:42Z" - latency: 2.18798ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:19:42Z" - latency: 2.077021ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:18:42Z" - latency: 1.884547ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:17:42Z" - latency: 2.907616ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:16:42Z" - latency: 2.473438ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:15:42Z" - latency: 2.13532ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:14:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T19:27:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-network-check-target-ip-10-0-129-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 1d46b1ff-d12a-4955-ba06-d73e2fb9188c resourceVersion: "75742" uid: 07f10757-94c2-4bf1-876b-ecbc14b78b9a spec: sourcePod: network-check-source-65bdbbff45-pgm6p targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T19:34:42Z" message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.993336ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:23:42Z" - latency: 1.784535ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:22:42Z" - latency: 2.010769ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:21:42Z" - latency: 2.08933ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:20:42Z" - latency: 1.926372ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:19:42Z" - latency: 1.923538ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:18:42Z" - latency: 2.025588ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:17:42Z" - latency: 2.728278ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:16:42Z" - latency: 2.15824ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:15:42Z" - latency: 2.133992ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:14:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T19:27:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-network-check-target-ip-10-0-134-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 1d46b1ff-d12a-4955-ba06-d73e2fb9188c resourceVersion: "75741" uid: d0e2a37d-26e3-43ee-b35a-a25fcfd44648 spec: sourcePod: network-check-source-65bdbbff45-pgm6p targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T19:34:42Z" message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 938.596µs message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:23:42Z" - latency: 962.359µs message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:22:42Z" - latency: 982.308µs message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:21:42Z" - latency: 1.054028ms message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:20:42Z" - latency: 1.272394ms message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:19:42Z" - latency: 1.088137ms message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:18:42Z" - latency: 1.091586ms message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:17:42Z" - latency: 931.676µs message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:16:42Z" - latency: 1.653283ms message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:15:42Z" - latency: 1.02546ms message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:14:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T19:27:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 1d46b1ff-d12a-4955-ba06-d73e2fb9188c resourceVersion: "79695" uid: ffa2cdc8-ea15-4dbc-b730-401f4404fd91 spec: sourcePod: network-check-source-65bdbbff45-pgm6p targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T19:33:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 983.958µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:27:42Z" - latency: 2.315524ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T20:27:42Z" - latency: 950.614µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:26:42Z" - latency: 2.017943ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T20:26:42Z" - latency: 946.365µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:25:42Z" - latency: 1.914763ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T20:25:42Z" - latency: 793.677µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:24:42Z" - latency: 2.141618ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T20:24:42Z" - latency: 974.188µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T20:23:42Z" - latency: 2.390363ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T20:23:42Z" kind: List metadata: resourceVersion: ""