apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-14T10:26:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-156-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-156.ec2.internal uid: 17e1732a-7ae8-4c49-ab72-b06a4a2740de resourceVersion: "67204" uid: 22cef205-d0af-4aa1-9570-ce88b535ba4c spec: sourcePod: network-check-source-6f8b768455-vdqgt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-14T10:33:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 912.217µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:01:54Z" - latency: 1.261808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:00:54Z" - latency: 1.267962ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:59:54Z" - latency: 1.691002ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:58:54Z" - latency: 1.124602ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:57:54Z" - latency: 1.400636ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:56:54Z" - latency: 992.899µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:55:54Z" - latency: 1.269522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:54:54Z" - latency: 1.807723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:53:54Z" - latency: 1.21849ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:52:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-14T10:26:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-156-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-156.ec2.internal uid: 17e1732a-7ae8-4c49-ab72-b06a4a2740de resourceVersion: "68338" uid: b1e21c58-921a-4b88-906c-081f9584b5c1 spec: sourcePod: network-check-source-6f8b768455-vdqgt targetEndpoint: a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-14T10:32:54Z" message: 'load-balancer-api-external: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.704477ms message: 'load-balancer-api-external: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:02:54Z" - latency: 7.398975ms message: 'load-balancer-api-external: resolved host name a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-14T11:02:54Z" - latency: 5.449233ms message: 'load-balancer-api-external: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:01:54Z" - latency: 7.410547ms message: 'load-balancer-api-external: resolved host name a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-14T11:01:54Z" - latency: 4.334389ms message: 'load-balancer-api-external: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:00:54Z" - latency: 7.277117ms message: 'load-balancer-api-external: resolved host name a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-14T11:00:54Z" - latency: 5.374843ms message: 'load-balancer-api-external: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:59:54Z" - latency: 7.564382ms message: 'load-balancer-api-external: resolved host name a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-14T10:59:54Z" - latency: 5.127562ms message: 'load-balancer-api-external: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:58:54Z" - latency: 7.802202ms message: 'load-balancer-api-external: resolved host name a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-14T10:58:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-14T10:26:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-156-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-156.ec2.internal uid: 17e1732a-7ae8-4c49-ab72-b06a4a2740de resourceVersion: "68337" uid: 22ed4dfe-e747-4b07-a5fb-ca276195d95a spec: sourcePod: network-check-source-6f8b768455-vdqgt targetEndpoint: a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-14T10:32:54Z" message: 'load-balancer-api-internal: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.852984ms message: 'load-balancer-api-internal: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:02:54Z" - latency: 7.401845ms message: 'load-balancer-api-internal: resolved host name a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-14T11:02:54Z" - latency: 4.675601ms message: 'load-balancer-api-internal: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:01:54Z" - latency: 7.546935ms message: 'load-balancer-api-internal: resolved host name a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-14T11:01:54Z" - latency: 4.981869ms message: 'load-balancer-api-internal: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:00:54Z" - latency: 7.327278ms message: 'load-balancer-api-internal: resolved host name a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-14T11:00:54Z" - latency: 5.371135ms message: 'load-balancer-api-internal: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:59:54Z" - latency: 7.636732ms message: 'load-balancer-api-internal: resolved host name a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-14T10:59:54Z" - latency: 4.091481ms message: 'load-balancer-api-internal: tcp connection to a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:58:54Z" - latency: 7.874948ms message: 'load-balancer-api-internal: resolved host name a0465b068e17649688c6db7ce01cefba-9ee2cf30741b0140.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-14T10:58:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-14T10:26:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-156-to-network-check-target-ip-10-0-133-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-156.ec2.internal uid: 17e1732a-7ae8-4c49-ab72-b06a4a2740de resourceVersion: "67253" uid: 88f50d75-f460-4b2e-9386-7d9645e1db02 spec: sourcePod: network-check-source-6f8b768455-vdqgt targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-14T10:33:56Z" message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 972.838µs message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:01:56Z" - latency: 2.180372ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:00:56Z" - latency: 2.295576ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:59:56Z" - latency: 1.330691ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:58:56Z" - latency: 2.577926ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:57:56Z" - latency: 1.038092ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:56:56Z" - latency: 1.380014ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:55:56Z" - latency: 2.294244ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:54:56Z" - latency: 2.585077ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:53:56Z" - latency: 1.135902ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:52:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-14T10:26:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-156-to-network-check-target-ip-10-0-135-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-156.ec2.internal uid: 17e1732a-7ae8-4c49-ab72-b06a4a2740de resourceVersion: "67203" uid: 0ecf4c58-0fca-4b57-9f49-5208af68f000 spec: sourcePod: network-check-source-6f8b768455-vdqgt targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-14T10:33:54Z" message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.21315ms message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:01:54Z" - latency: 2.132704ms message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:00:54Z" - latency: 2.298492ms message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:59:54Z" - latency: 2.423993ms message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:58:54Z" - latency: 2.263553ms message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:57:54Z" - latency: 2.104218ms message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:56:54Z" - latency: 2.497133ms message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:55:54Z" - latency: 2.063492ms message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:54:54Z" - latency: 3.251576ms message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:53:54Z" - latency: 2.343424ms message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:52:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-14T10:26:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-156-to-network-check-target-ip-10-0-141-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-156.ec2.internal uid: 17e1732a-7ae8-4c49-ab72-b06a4a2740de resourceVersion: "67202" uid: 8eb1dc43-9013-4f07-9e14-e02b9fa73a6b spec: sourcePod: network-check-source-6f8b768455-vdqgt targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-14T10:33:54Z" message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 952.979µs message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:01:54Z" - latency: 1.338603ms message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:00:54Z" - latency: 1.083046ms message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:59:54Z" - latency: 1.680312ms message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:58:54Z" - latency: 1.365451ms message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:57:54Z" - latency: 1.457222ms message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:56:54Z" - latency: 1.070955ms message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:55:54Z" - latency: 1.030727ms message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:54:54Z" - latency: 2.012955ms message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:53:54Z" - latency: 1.512603ms message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:52:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-14T10:26:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-156-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-156.ec2.internal uid: 17e1732a-7ae8-4c49-ab72-b06a4a2740de resourceVersion: "68336" uid: 667a8449-b624-4c9d-9676-dafd6b890e7d spec: sourcePod: network-check-source-6f8b768455-vdqgt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-14T10:32:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 964.29µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:02:54Z" - latency: 2.127194ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-14T11:02:54Z" - latency: 2.064357ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:01:54Z" - latency: 2.092051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-14T11:01:54Z" - latency: 1.134213ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-14T11:00:54Z" - latency: 1.999137ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-14T11:00:54Z" - latency: 902.193µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:59:54Z" - latency: 1.969156ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-14T10:59:54Z" - latency: 2.313082ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-14T10:58:54Z" - latency: 2.223621ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-14T10:58:54Z" kind: List metadata: resourceVersion: ""