apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T01:19:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-225-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-225.ec2.internal uid: 4106d632-bda4-48c2-93ee-1e075bd56f94 resourceVersion: "65829" uid: b93e3a44-2852-4be9-8ede-4c7a157dc2e4 spec: sourcePod: network-check-source-6f8b768455-f2nnr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T01:26:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.22291ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:54:45Z" - latency: 1.021175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:53:45Z" - latency: 1.242092ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:52:45Z" - latency: 1.024938ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:51:45Z" - latency: 961.143µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:50:45Z" - latency: 1.42243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:49:45Z" - latency: 1.18967ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:48:45Z" - latency: 882.341µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:47:45Z" - latency: 1.241217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:46:45Z" - latency: 1.285899ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:45:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T01:19:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-225-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-225.ec2.internal uid: 4106d632-bda4-48c2-93ee-1e075bd56f94 resourceVersion: "66615" uid: d5c031b1-c225-47c9-89fb-da625167e27f spec: sourcePod: network-check-source-6f8b768455-f2nnr targetEndpoint: a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T01:25:45Z" message: 'load-balancer-api-external: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.817ms message: 'load-balancer-api-external: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:55:45Z" - latency: 8.903094ms message: 'load-balancer-api-external: resolved host name a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T01:55:45Z" - latency: 4.826373ms message: 'load-balancer-api-external: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:54:45Z" - latency: 8.737931ms message: 'load-balancer-api-external: resolved host name a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T01:54:45Z" - latency: 4.929598ms message: 'load-balancer-api-external: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:53:45Z" - latency: 9.216142ms message: 'load-balancer-api-external: resolved host name a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T01:53:45Z" - latency: 5.59598ms message: 'load-balancer-api-external: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:52:45Z" - latency: 9.030533ms message: 'load-balancer-api-external: resolved host name a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T01:52:45Z" - latency: 5.018216ms message: 'load-balancer-api-external: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:51:45Z" - latency: 7.65595ms message: 'load-balancer-api-external: resolved host name a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T01:51:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T01:19:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-225-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-225.ec2.internal uid: 4106d632-bda4-48c2-93ee-1e075bd56f94 resourceVersion: "66614" uid: a1edd801-3f3f-4a59-9f21-e0a66fd0c00e spec: sourcePod: network-check-source-6f8b768455-f2nnr targetEndpoint: a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T01:25:45Z" message: 'load-balancer-api-internal: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.711012ms message: 'load-balancer-api-internal: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:55:45Z" - latency: 8.843956ms message: 'load-balancer-api-internal: resolved host name a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T01:55:45Z" - latency: 4.731935ms message: 'load-balancer-api-internal: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:54:45Z" - latency: 8.822909ms message: 'load-balancer-api-internal: resolved host name a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T01:54:45Z" - latency: 5.030512ms message: 'load-balancer-api-internal: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:53:45Z" - latency: 9.163352ms message: 'load-balancer-api-internal: resolved host name a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T01:53:45Z" - latency: 5.603949ms message: 'load-balancer-api-internal: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:52:45Z" - latency: 9.196206ms message: 'load-balancer-api-internal: resolved host name a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T01:52:45Z" - latency: 4.967251ms message: 'load-balancer-api-internal: tcp connection to a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:51:45Z" - latency: 7.687043ms message: 'load-balancer-api-internal: resolved host name a446397bc340947f7ae22a08939899a0-8dcdd5160ce01e5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T01:51:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T01:19:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-225-to-network-check-target-ip-10-0-135-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-225.ec2.internal uid: 4106d632-bda4-48c2-93ee-1e075bd56f94 resourceVersion: "65826" uid: 8c32fe30-305f-4fe7-a0c2-3ee11548e4c3 spec: sourcePod: network-check-source-6f8b768455-f2nnr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T01:26:45Z" message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.001125ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:54:45Z" - latency: 1.108252ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:53:45Z" - latency: 894.399µs message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:52:45Z" - latency: 1.176736ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:51:45Z" - latency: 1.340362ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:50:45Z" - latency: 1.652041ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:49:45Z" - latency: 1.014959ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:48:45Z" - latency: 1.45051ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:47:45Z" - latency: 1.038545ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:46:45Z" - latency: 1.199753ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:45:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T01:19:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-225-to-network-check-target-ip-10-0-137-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-225.ec2.internal uid: 4106d632-bda4-48c2-93ee-1e075bd56f94 resourceVersion: "65827" uid: f6512589-dbf5-4a09-a614-2d3f905e1a9d spec: sourcePod: network-check-source-6f8b768455-f2nnr targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T01:26:45Z" message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.238035ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:54:45Z" - latency: 2.250455ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:53:45Z" - latency: 2.379382ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:52:45Z" - latency: 2.177192ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:51:45Z" - latency: 2.09341ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:50:45Z" - latency: 2.285925ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:49:45Z" - latency: 2.21172ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:48:45Z" - latency: 2.485432ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:47:45Z" - latency: 2.216999ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:46:45Z" - latency: 2.255414ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:45:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T01:19:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-225-to-network-check-target-ip-10-0-142-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-225.ec2.internal uid: 4106d632-bda4-48c2-93ee-1e075bd56f94 resourceVersion: "65828" uid: 22b12ff8-d6f5-4728-8914-657d4753c3cb spec: sourcePod: network-check-source-6f8b768455-f2nnr targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T01:26:45Z" message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.381879ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:54:45Z" - latency: 2.313663ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:53:45Z" - latency: 2.499453ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:52:45Z" - latency: 2.361422ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:51:45Z" - latency: 2.439763ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:50:45Z" - latency: 2.427537ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:49:45Z" - latency: 2.097841ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:48:45Z" - latency: 2.239831ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:47:45Z" - latency: 2.437379ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:46:45Z" - latency: 2.383206ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:45:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T01:19:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-225-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-225.ec2.internal uid: 4106d632-bda4-48c2-93ee-1e075bd56f94 resourceVersion: "66613" uid: ce802182-e26c-4c93-b397-059e38c66b64 spec: sourcePod: network-check-source-6f8b768455-f2nnr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T01:25:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.395722ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:55:45Z" - latency: 1.994121ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T01:55:45Z" - latency: 938.21µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:54:45Z" - latency: 1.558278ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T01:54:45Z" - latency: 973.872µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:53:45Z" - latency: 1.826073ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T01:53:45Z" - latency: 928.311µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:52:45Z" - latency: 1.776313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T01:52:45Z" - latency: 1.154111ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T01:51:45Z" - latency: 2.109035ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T01:51:45Z" kind: List metadata: resourceVersion: ""