apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:48:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-124-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-124.ec2.internal uid: a87629e3-98a3-4ea7-b6ff-193170875266 resourceVersion: "70520" uid: c8d025fc-f472-4b50-8302-9a171efeca8a spec: sourcePod: network-check-source-7d88cb55d8-ltzm4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T21:55:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.242443ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:37:19Z" - latency: 1.187811ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:36:19Z" - latency: 1.243467ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:35:19Z" - latency: 1.151561ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:34:19Z" - latency: 1.569195ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:19Z" - latency: 1.017179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:19Z" - latency: 1.182784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:19Z" - latency: 1.128329ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:19Z" - latency: 1.022267ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:19Z" - latency: 1.171705ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:28:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:48:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-124-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-124.ec2.internal uid: a87629e3-98a3-4ea7-b6ff-193170875266 resourceVersion: "69650" uid: 228e7bee-f093-4805-a9aa-1429abea25aa spec: sourcePod: network-check-source-7d88cb55d8-ltzm4 targetEndpoint: a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T21:54:19Z" message: 'load-balancer-api-external: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.533162ms message: 'load-balancer-api-external: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:36:19Z" - latency: 8.421402ms message: 'load-balancer-api-external: resolved host name a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:36:19Z" - latency: 4.42257ms message: 'load-balancer-api-external: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:35:19Z" - latency: 9.301183ms message: 'load-balancer-api-external: resolved host name a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:35:19Z" - latency: 5.800012ms message: 'load-balancer-api-external: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:34:19Z" - latency: 11.001819ms message: 'load-balancer-api-external: resolved host name a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:34:19Z" - latency: 6.425938ms message: 'load-balancer-api-external: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:19Z" - latency: 8.683109ms message: 'load-balancer-api-external: resolved host name a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:33:19Z" - latency: 5.86869ms message: 'load-balancer-api-external: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:19Z" - latency: 9.195231ms message: 'load-balancer-api-external: resolved host name a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:32:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:48:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-124-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-124.ec2.internal uid: a87629e3-98a3-4ea7-b6ff-193170875266 resourceVersion: "69651" uid: decf5795-cf74-4dd2-ae8f-ffdae4ded327 spec: sourcePod: network-check-source-7d88cb55d8-ltzm4 targetEndpoint: a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T21:54:19Z" message: 'load-balancer-api-internal: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.900599ms message: 'load-balancer-api-internal: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:36:19Z" - latency: 8.369084ms message: 'load-balancer-api-internal: resolved host name a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:36:19Z" - latency: 4.048685ms message: 'load-balancer-api-internal: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:35:19Z" - latency: 9.209324ms message: 'load-balancer-api-internal: resolved host name a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:35:19Z" - latency: 5.775917ms message: 'load-balancer-api-internal: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:34:19Z" - latency: 10.974359ms message: 'load-balancer-api-internal: resolved host name a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:34:19Z" - latency: 6.416691ms message: 'load-balancer-api-internal: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:19Z" - latency: 8.609832ms message: 'load-balancer-api-internal: resolved host name a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:33:19Z" - latency: 5.854644ms message: 'load-balancer-api-internal: tcp connection to a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:19Z" - latency: 9.14699ms message: 'load-balancer-api-internal: resolved host name a56f2eec9658d4601a04c888e41e996f-8c2297773d6e786c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:32:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:48:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-124-to-network-check-target-ip-10-0-129-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-124.ec2.internal uid: a87629e3-98a3-4ea7-b6ff-193170875266 resourceVersion: "70519" uid: c794aaa8-dd0c-4dee-9fa2-1598f8db5a28 spec: sourcePod: network-check-source-7d88cb55d8-ltzm4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:55:19Z" message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.21891ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:37:19Z" - latency: 2.172936ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:36:19Z" - latency: 2.162271ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:35:19Z" - latency: 2.456215ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:34:19Z" - latency: 2.774848ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:19Z" - latency: 2.418885ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:19Z" - latency: 2.282445ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:19Z" - latency: 2.110612ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:19Z" - latency: 2.136087ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:19Z" - latency: 2.407399ms message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:28:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:48:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-124-to-network-check-target-ip-10-0-138-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-124.ec2.internal uid: a87629e3-98a3-4ea7-b6ff-193170875266 resourceVersion: "70517" uid: 8b77abca-b9f7-4e8e-a6db-052101fbacab spec: sourcePod: network-check-source-7d88cb55d8-ltzm4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:55:19Z" message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 971.55µs message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:37:19Z" - latency: 1.454874ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:36:19Z" - latency: 1.010616ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:35:19Z" - latency: 1.402213ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:34:19Z" - latency: 1.31158ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:19Z" - latency: 1.223401ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:19Z" - latency: 940.424µs message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:19Z" - latency: 923.262µs message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:19Z" - latency: 1.102818ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:19Z" - latency: 892.592µs message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:28:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:48:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-124-to-network-check-target-ip-10-0-143-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-124.ec2.internal uid: a87629e3-98a3-4ea7-b6ff-193170875266 resourceVersion: "70518" uid: d5e69880-f11b-4a02-8640-11b729224a07 spec: sourcePod: network-check-source-7d88cb55d8-ltzm4 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:55:19Z" message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.112211ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:37:19Z" - latency: 2.59917ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:36:19Z" - latency: 2.765817ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:35:19Z" - latency: 2.274916ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:34:19Z" - latency: 2.343858ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:19Z" - latency: 2.577741ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:19Z" - latency: 2.192779ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:19Z" - latency: 2.457503ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:19Z" - latency: 2.105784ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:19Z" - latency: 1.987807ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:28:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:48:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-124-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-124.ec2.internal uid: a87629e3-98a3-4ea7-b6ff-193170875266 resourceVersion: "69649" uid: 0e9a7e1e-146a-4603-9371-55a81b7dcc3f spec: sourcePod: network-check-source-7d88cb55d8-ltzm4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T21:54:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.7µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:36:19Z" - latency: 1.747552ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:36:19Z" - latency: 900.317µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:35:19Z" - latency: 1.833443ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:35:19Z" - latency: 973.595µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:34:19Z" - latency: 2.315359ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:34:19Z" - latency: 852.203µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:19Z" - latency: 1.937999ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:33:19Z" - latency: 1.328909ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:19Z" - latency: 1.918704ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:32:19Z" kind: List metadata: resourceVersion: ""