apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:39:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 51614773-ea12-4eb9-a8df-5d95abd4ac84 resourceVersion: "70368" uid: 11bbf0ed-954c-4114-8da3-8e64da993aaa spec: sourcePod: network-check-source-7d88cb55d8-7k7kp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T00:46:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 839.3µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:28:08Z" - latency: 1.371108ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:27:08Z" - latency: 780.143µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:26:08Z" - latency: 1.413011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:25:08Z" - latency: 1.138207ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:24:08Z" - latency: 1.036648ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:23:08Z" - latency: 782.74µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:22:08Z" - latency: 813.99µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:21:08Z" - latency: 1.189949ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:20:08Z" - latency: 929.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:19:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:39:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 51614773-ea12-4eb9-a8df-5d95abd4ac84 resourceVersion: "69537" uid: 1051f643-73e1-4e39-b395-4de94fbe125a spec: sourcePod: network-check-source-7d88cb55d8-7k7kp targetEndpoint: a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T00:45:08Z" message: 'load-balancer-api-external: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.53626ms message: 'load-balancer-api-external: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:27:08Z" - latency: 6.498158ms message: 'load-balancer-api-external: resolved host name a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:27:08Z" - latency: 3.419502ms message: 'load-balancer-api-external: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:26:08Z" - latency: 6.926409ms message: 'load-balancer-api-external: resolved host name a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:26:08Z" - latency: 5.171202ms message: 'load-balancer-api-external: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:25:08Z" - latency: 6.816645ms message: 'load-balancer-api-external: resolved host name a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:25:08Z" - latency: 5.404657ms message: 'load-balancer-api-external: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:24:08Z" - latency: 7.18437ms message: 'load-balancer-api-external: resolved host name a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:24:08Z" - latency: 5.200609ms message: 'load-balancer-api-external: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:23:08Z" - latency: 6.912883ms message: 'load-balancer-api-external: resolved host name a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:23:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:39:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 51614773-ea12-4eb9-a8df-5d95abd4ac84 resourceVersion: "69536" uid: 61dce44e-50f0-40cd-9d46-c73b8ce34514 spec: sourcePod: network-check-source-7d88cb55d8-7k7kp targetEndpoint: a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T00:45:08Z" message: 'load-balancer-api-internal: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.346291ms message: 'load-balancer-api-internal: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:27:08Z" - latency: 6.383102ms message: 'load-balancer-api-internal: resolved host name a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:27:08Z" - latency: 4.423835ms message: 'load-balancer-api-internal: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:26:08Z" - latency: 6.907294ms message: 'load-balancer-api-internal: resolved host name a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:26:08Z" - latency: 6.176077ms message: 'load-balancer-api-internal: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:25:08Z" - latency: 6.754287ms message: 'load-balancer-api-internal: resolved host name a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:25:08Z" - latency: 5.391735ms message: 'load-balancer-api-internal: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:24:08Z" - latency: 7.213962ms message: 'load-balancer-api-internal: resolved host name a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:24:08Z" - latency: 5.214235ms message: 'load-balancer-api-internal: tcp connection to a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:23:08Z" - latency: 6.797149ms message: 'load-balancer-api-internal: resolved host name a11e7e5ef4c004c50a3c68cbd6116489-830ba20d7eb3e002.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:23:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:39:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-network-check-target-ip-10-0-132-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 51614773-ea12-4eb9-a8df-5d95abd4ac84 resourceVersion: "70367" uid: 5655ed91-5e8c-487b-9730-66771f3ca95c spec: sourcePod: network-check-source-7d88cb55d8-7k7kp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T00:46:08Z" message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.442973ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:28:08Z" - latency: 2.29209ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:27:08Z" - latency: 2.191397ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:26:08Z" - latency: 2.15867ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:25:08Z" - latency: 2.158093ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:24:08Z" - latency: 2.376177ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:23:08Z" - latency: 1.972791ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:22:08Z" - latency: 2.15779ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:21:08Z" - latency: 2.141615ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:20:08Z" - latency: 2.243234ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:19:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:39:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-network-check-target-ip-10-0-135-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 51614773-ea12-4eb9-a8df-5d95abd4ac84 resourceVersion: "70366" uid: 86423bc7-b25d-40ad-b36a-7d6a73dd9691 spec: sourcePod: network-check-source-7d88cb55d8-7k7kp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T00:46:08Z" message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.35861ms message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:28:08Z" - latency: 1.001604ms message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:27:08Z" - latency: 1.246899ms message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:26:08Z" - latency: 989.846µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:25:08Z" - latency: 830.71µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:24:08Z" - latency: 781.543µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:23:08Z" - latency: 923.246µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:22:08Z" - latency: 887.438µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:21:08Z" - latency: 838.472µs message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:20:08Z" - latency: 1.377841ms message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:19:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:39:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-network-check-target-ip-10-0-138-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 51614773-ea12-4eb9-a8df-5d95abd4ac84 resourceVersion: "70365" uid: 4ab5e8fe-d321-43d1-b564-7ce34c157ebf spec: sourcePod: network-check-source-7d88cb55d8-7k7kp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T00:46:08Z" message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.278691ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:28:08Z" - latency: 2.173753ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:27:08Z" - latency: 1.931302ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:26:08Z" - latency: 1.871139ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:25:08Z" - latency: 1.748867ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:24:08Z" - latency: 2.081933ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:23:08Z" - latency: 1.727646ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:22:08Z" - latency: 2.206857ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:21:08Z" - latency: 1.915829ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:20:08Z" - latency: 1.80225ms message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:19:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T00:39:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-11-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-11.ec2.internal uid: 51614773-ea12-4eb9-a8df-5d95abd4ac84 resourceVersion: "69535" uid: bcfcac17-2f0a-43cb-aec4-f18fe6b9d623 spec: sourcePod: network-check-source-7d88cb55d8-7k7kp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T00:45:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.031µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:27:08Z" - latency: 2.153478ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T01:27:08Z" - latency: 1.102256ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:26:08Z" - latency: 2.077932ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T01:26:08Z" - latency: 782.925µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:25:08Z" - latency: 2.044344ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T01:25:08Z" - latency: 857.852µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:24:08Z" - latency: 1.922705ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T01:24:08Z" - latency: 934.761µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:23:08Z" - latency: 1.694737ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T01:23:08Z" kind: List metadata: resourceVersion: ""