apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:05:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-10-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-10.ec2.internal uid: f93984ee-e0ae-437d-b5ef-5186b0d65b3a resourceVersion: "25689" uid: 081b6d82-1a9f-4f7c-adfe-8e198ac0f04d spec: sourcePod: network-check-source-7d88cb55d8-c77sp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T16:12:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 954.549µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:59Z" - latency: 1.019986ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:59Z" - latency: 1.006641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:59Z" - latency: 751.977µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:30:59Z" - latency: 744.936µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:29:59Z" - latency: 1.160257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:28:59Z" - latency: 1.074944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:27:59Z" - latency: 1.02941ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:26:59Z" - latency: 1.077631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:25:59Z" - latency: 1.073245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:24:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-10-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-10.ec2.internal uid: f93984ee-e0ae-437d-b5ef-5186b0d65b3a resourceVersion: "26727" uid: a4e4e955-2a05-4440-80ba-a6c536cd2329 spec: sourcePod: network-check-source-7d88cb55d8-c77sp targetEndpoint: aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T16:11:59Z" message: 'load-balancer-api-external: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.25046ms message: 'load-balancer-api-external: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:35:59Z" - latency: 7.125629ms message: 'load-balancer-api-external: resolved host name aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:35:59Z" - latency: 5.120195ms message: 'load-balancer-api-external: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:34:59Z" - latency: 8.110774ms message: 'load-balancer-api-external: resolved host name aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:34:59Z" - latency: 6.359605ms message: 'load-balancer-api-external: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:59Z" - latency: 7.669919ms message: 'load-balancer-api-external: resolved host name aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:33:59Z" - latency: 5.851633ms message: 'load-balancer-api-external: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:59Z" - latency: 7.705514ms message: 'load-balancer-api-external: resolved host name aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:32:59Z" - latency: 5.67251ms message: 'load-balancer-api-external: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:59Z" - latency: 6.360673ms message: 'load-balancer-api-external: resolved host name aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:31:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-10-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-10.ec2.internal uid: f93984ee-e0ae-437d-b5ef-5186b0d65b3a resourceVersion: "26728" uid: cdce2fa3-2c23-4734-abda-a0d776030ff8 spec: sourcePod: network-check-source-7d88cb55d8-c77sp targetEndpoint: aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T16:11:59Z" message: 'load-balancer-api-internal: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.255682ms message: 'load-balancer-api-internal: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:35:59Z" - latency: 7.169466ms message: 'load-balancer-api-internal: resolved host name aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:35:59Z" - latency: 5.154766ms message: 'load-balancer-api-internal: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:34:59Z" - latency: 8.048036ms message: 'load-balancer-api-internal: resolved host name aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:34:59Z" - latency: 6.409501ms message: 'load-balancer-api-internal: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:59Z" - latency: 7.707491ms message: 'load-balancer-api-internal: resolved host name aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:33:59Z" - latency: 5.805215ms message: 'load-balancer-api-internal: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:59Z" - latency: 7.768661ms message: 'load-balancer-api-internal: resolved host name aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:32:59Z" - latency: 5.660278ms message: 'load-balancer-api-internal: tcp connection to aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:59Z" - latency: 6.545077ms message: 'load-balancer-api-internal: resolved host name aa92a00c0556e4a2b95012e499e0a2f5-c4cf88cb529b89d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:31:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-10-to-network-check-target-ip-10-0-131-181 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-10.ec2.internal uid: f93984ee-e0ae-437d-b5ef-5186b0d65b3a resourceVersion: "25688" uid: 7c4a3663-7820-4f00-9516-96cd0f804f23 spec: sourcePod: network-check-source-7d88cb55d8-c77sp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T16:12:59Z" message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.207179ms message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:59Z" - latency: 2.180379ms message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:59Z" - latency: 2.026624ms message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:59Z" - latency: 2.005775ms message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:30:59Z" - latency: 1.821227ms message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:29:59Z" - latency: 2.304884ms message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:28:59Z" - latency: 2.256699ms message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:27:59Z" - latency: 2.32881ms message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:26:59Z" - latency: 2.266154ms message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:25:59Z" - latency: 2.538003ms message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:24:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-10-to-network-check-target-ip-10-0-138-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-10.ec2.internal uid: f93984ee-e0ae-437d-b5ef-5186b0d65b3a resourceVersion: "25686" uid: 838545ef-e4a4-4711-8b89-00409f2b4fbc spec: sourcePod: network-check-source-7d88cb55d8-c77sp targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T16:12:59Z" message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.350102ms message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:59Z" - latency: 927.323µs message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:59Z" - latency: 1.088007ms message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:59Z" - latency: 805.64µs message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:30:59Z" - latency: 942.62µs message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:29:59Z" - latency: 1.487969ms message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:28:59Z" - latency: 1.637679ms message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:27:59Z" - latency: 1.377032ms message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:26:59Z" - latency: 1.136009ms message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:25:59Z" - latency: 998.934µs message: 'network-check-target-ip-10-0-138-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:24:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-10-to-network-check-target-ip-10-0-142-59 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-10.ec2.internal uid: f93984ee-e0ae-437d-b5ef-5186b0d65b3a resourceVersion: "25687" uid: 95bae64b-5b04-4b62-9fe0-84d16f6f82f2 spec: sourcePod: network-check-source-7d88cb55d8-c77sp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T16:12:59Z" message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.009637ms message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:59Z" - latency: 1.872215ms message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:59Z" - latency: 1.959879ms message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:59Z" - latency: 1.530666ms message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:30:59Z" - latency: 1.879777ms message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:29:59Z" - latency: 2.051365ms message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:28:59Z" - latency: 1.67442ms message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:27:59Z" - latency: 1.799083ms message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:26:59Z" - latency: 1.95846ms message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:25:59Z" - latency: 2.10786ms message: 'network-check-target-ip-10-0-142-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:24:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-10-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-10.ec2.internal uid: f93984ee-e0ae-437d-b5ef-5186b0d65b3a resourceVersion: "26726" uid: 13e1cfca-1ae2-4a34-bea2-6d6f90d85094 spec: sourcePod: network-check-source-7d88cb55d8-c77sp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T16:11:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.163366ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:35:59Z" - latency: 2.41458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:35:59Z" - latency: 1.299049ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:34:59Z" - latency: 1.779027ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:34:59Z" - latency: 965.21µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:59Z" - latency: 1.862574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:33:59Z" - latency: 943.496µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:59Z" - latency: 1.909239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:32:59Z" - latency: 886.039µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:59Z" - latency: 1.93934ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:31:59Z" kind: List metadata: resourceVersion: ""