apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-67-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-67.ec2.internal uid: e84b0fef-c9b4-4256-8b94-01fbd97f5f11 resourceVersion: "55109" uid: 3300799c-0f69-4d49-b0bd-f0f59bb376a6 spec: sourcePod: network-check-source-56499946bc-qrstt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T17:24:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 841.351µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:52:21Z" - latency: 1.727979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:51:21Z" - latency: 797.815µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:50:21Z" - latency: 740.051µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:49:21Z" - latency: 1.264324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:48:21Z" - latency: 819.161µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:47:21Z" - latency: 1.035109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:46:21Z" - latency: 791.81µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:45:21Z" - latency: 804.968µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:44:21Z" - latency: 1.618916ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:43:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-67-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-67.ec2.internal uid: e84b0fef-c9b4-4256-8b94-01fbd97f5f11 resourceVersion: "56018" uid: a47390fc-39d7-4250-9124-1ecc1d0f1af0 spec: sourcePod: network-check-source-56499946bc-qrstt targetEndpoint: a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T17:23:21Z" message: 'load-balancer-api-external: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.073131ms message: 'load-balancer-api-external: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:53:21Z" - latency: 6.605272ms message: 'load-balancer-api-external: resolved host name a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:53:21Z" - latency: 4.489645ms message: 'load-balancer-api-external: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:52:21Z" - latency: 7.063553ms message: 'load-balancer-api-external: resolved host name a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:52:21Z" - latency: 4.022302ms message: 'load-balancer-api-external: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:51:21Z" - latency: 7.370173ms message: 'load-balancer-api-external: resolved host name a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:51:21Z" - latency: 6.088327ms message: 'load-balancer-api-external: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:50:21Z" - latency: 6.684978ms message: 'load-balancer-api-external: resolved host name a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:50:21Z" - latency: 3.924866ms message: 'load-balancer-api-external: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:49:21Z" - latency: 8.925509ms message: 'load-balancer-api-external: resolved host name a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:49:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-67-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-67.ec2.internal uid: e84b0fef-c9b4-4256-8b94-01fbd97f5f11 resourceVersion: "56019" uid: eec771fc-3c2e-46b1-97ca-883f3dab05fb spec: sourcePod: network-check-source-56499946bc-qrstt targetEndpoint: a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T17:23:21Z" message: 'load-balancer-api-internal: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.514479ms message: 'load-balancer-api-internal: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:53:21Z" - latency: 6.679513ms message: 'load-balancer-api-internal: resolved host name a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:53:21Z" - latency: 4.517982ms message: 'load-balancer-api-internal: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:52:21Z" - latency: 7.142757ms message: 'load-balancer-api-internal: resolved host name a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:52:21Z" - latency: 3.999491ms message: 'load-balancer-api-internal: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:51:21Z" - latency: 7.461331ms message: 'load-balancer-api-internal: resolved host name a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:51:21Z" - latency: 4.903818ms message: 'load-balancer-api-internal: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:50:21Z" - latency: 6.704227ms message: 'load-balancer-api-internal: resolved host name a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:50:21Z" - latency: 5.344261ms message: 'load-balancer-api-internal: tcp connection to a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:49:21Z" - latency: 8.975174ms message: 'load-balancer-api-internal: resolved host name a65025233e4cb4140947181a0b056a87-7e4d7d56c067f332.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T17:49:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-67-to-network-check-target-ip-10-0-133-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-67.ec2.internal uid: e84b0fef-c9b4-4256-8b94-01fbd97f5f11 resourceVersion: "55107" uid: 739a4a68-b3ef-448f-a561-4ba84756d47c spec: sourcePod: network-check-source-56499946bc-qrstt targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T17:24:21Z" message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.773127ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:52:21Z" - latency: 1.982796ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:51:21Z" - latency: 1.596535ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:50:21Z" - latency: 1.940022ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:49:21Z" - latency: 1.735201ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:48:21Z" - latency: 1.641105ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:47:21Z" - latency: 1.818808ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:46:21Z" - latency: 2.628473ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:45:21Z" - latency: 1.825859ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:44:21Z" - latency: 1.795001ms message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:43:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-67-to-network-check-target-ip-10-0-142-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-67.ec2.internal uid: e84b0fef-c9b4-4256-8b94-01fbd97f5f11 resourceVersion: "55108" uid: a01ee3cb-3022-48c1-9b28-10ecfedf5dcc spec: sourcePod: network-check-source-56499946bc-qrstt targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T17:24:21Z" message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.212731ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:52:21Z" - latency: 2.226505ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:51:21Z" - latency: 2.078171ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:50:21Z" - latency: 2.227078ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:49:21Z" - latency: 2.671378ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:48:21Z" - latency: 1.789809ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:47:21Z" - latency: 2.267355ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:46:21Z" - latency: 1.97566ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:45:21Z" - latency: 1.959453ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:44:21Z" - latency: 2.440752ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:43:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-67-to-network-check-target-ip-10-0-143-67 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-67.ec2.internal uid: e84b0fef-c9b4-4256-8b94-01fbd97f5f11 resourceVersion: "55106" uid: 7adeec59-2dd0-4a69-b2b7-4982630477e2 spec: sourcePod: network-check-source-56499946bc-qrstt targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T17:24:21Z" message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 776.053µs message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:52:21Z" - latency: 835.83µs message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:51:21Z" - latency: 727.169µs message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:50:21Z" - latency: 806.466µs message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:49:21Z" - latency: 1.469382ms message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:48:21Z" - latency: 629.188µs message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:47:21Z" - latency: 1.97478ms message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:46:21Z" - latency: 1.345787ms message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:45:21Z" - latency: 1.26427ms message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:44:21Z" - latency: 740.792µs message: 'network-check-target-ip-10-0-143-67: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:43:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T17:17:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-67-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-67.ec2.internal uid: e84b0fef-c9b4-4256-8b94-01fbd97f5f11 resourceVersion: "56015" uid: f4c70e9f-8870-4452-9616-ae8da1268444 spec: sourcePod: network-check-source-56499946bc-qrstt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T17:23:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 859.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:53:21Z" - latency: 1.78834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:53:21Z" - latency: 814.97µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:52:21Z" - latency: 2.072322ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:52:21Z" - latency: 807.027µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:51:21Z" - latency: 2.431075ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:51:21Z" - latency: 937.942µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:50:21Z" - latency: 1.74826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:50:21Z" - latency: 754.391µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T17:49:21Z" - latency: 1.799355ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T17:49:21Z" kind: List metadata: resourceVersion: ""