apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:27:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-138-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-138.ec2.internal uid: 79435ba0-6ff7-4f8e-90e0-033e67550da7 resourceVersion: "56002" uid: 538440e2-3061-4978-809d-4da84feae1be spec: sourcePod: network-check-source-869dcfcdcd-dtzqb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T20:34:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.270091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:02:40Z" - latency: 1.063133ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:01:40Z" - latency: 1.068073ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:00:40Z" - latency: 997.813µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:59:40Z" - latency: 987.942µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:58:40Z" - latency: 1.097324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:57:40Z" - latency: 885.489µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:56:40Z" - latency: 1.130271ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:55:40Z" - latency: 1.71832ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:54:40Z" - latency: 1.153499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:53:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:27:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-138-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-138.ec2.internal uid: 79435ba0-6ff7-4f8e-90e0-033e67550da7 resourceVersion: "57046" uid: 7335abbd-0dad-4f71-973e-c2fd3502b6ef spec: sourcePod: network-check-source-869dcfcdcd-dtzqb targetEndpoint: a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T20:33:40Z" message: 'load-balancer-api-external: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.096957ms message: 'load-balancer-api-external: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:03:40Z" - latency: 6.78324ms message: 'load-balancer-api-external: resolved host name a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:03:40Z" - latency: 4.170491ms message: 'load-balancer-api-external: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:02:40Z" - latency: 6.487479ms message: 'load-balancer-api-external: resolved host name a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:02:40Z" - latency: 3.44518ms message: 'load-balancer-api-external: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:01:40Z" - latency: 6.876168ms message: 'load-balancer-api-external: resolved host name a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:01:40Z" - latency: 5.71152ms message: 'load-balancer-api-external: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:00:40Z" - latency: 6.962366ms message: 'load-balancer-api-external: resolved host name a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:00:40Z" - latency: 4.188729ms message: 'load-balancer-api-external: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:59:40Z" - latency: 7.391252ms message: 'load-balancer-api-external: resolved host name a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:59:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:27:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-138-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-138.ec2.internal uid: 79435ba0-6ff7-4f8e-90e0-033e67550da7 resourceVersion: "57045" uid: 9f25aa90-c3e8-4901-bc91-ccc7072a86d8 spec: sourcePod: network-check-source-869dcfcdcd-dtzqb targetEndpoint: a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T20:33:40Z" message: 'load-balancer-api-internal: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.060015ms message: 'load-balancer-api-internal: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:03:40Z" - latency: 6.795061ms message: 'load-balancer-api-internal: resolved host name a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:03:40Z" - latency: 4.599529ms message: 'load-balancer-api-internal: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:02:40Z" - latency: 6.505618ms message: 'load-balancer-api-internal: resolved host name a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:02:40Z" - latency: 5.011758ms message: 'load-balancer-api-internal: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:01:40Z" - latency: 6.852587ms message: 'load-balancer-api-internal: resolved host name a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:01:40Z" - latency: 5.645827ms message: 'load-balancer-api-internal: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:00:40Z" - latency: 6.999498ms message: 'load-balancer-api-internal: resolved host name a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:00:40Z" - latency: 4.183201ms message: 'load-balancer-api-internal: tcp connection to a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:59:40Z" - latency: 7.365208ms message: 'load-balancer-api-internal: resolved host name a8ba8f1ade19a400bbf5b7a8f9bcf037-18b6df7f5bc0f998.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:59:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:27:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-138-to-network-check-target-ip-10-0-130-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-138.ec2.internal uid: 79435ba0-6ff7-4f8e-90e0-033e67550da7 resourceVersion: "55999" uid: 994eb326-79be-4c6b-b81b-cf1ac6d347d7 spec: sourcePod: network-check-source-869dcfcdcd-dtzqb targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T20:34:40Z" message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.016064ms message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:02:40Z" - latency: 878.725µs message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:01:40Z" - latency: 1.13702ms message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:00:40Z" - latency: 1.033735ms message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:59:40Z" - latency: 1.407524ms message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:58:40Z" - latency: 1.764137ms message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:57:40Z" - latency: 1.307787ms message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:56:40Z" - latency: 961.787µs message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:55:40Z" - latency: 1.596195ms message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:54:40Z" - latency: 1.365038ms message: 'network-check-target-ip-10-0-130-138: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:53:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:27:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-138-to-network-check-target-ip-10-0-133-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-138.ec2.internal uid: 79435ba0-6ff7-4f8e-90e0-033e67550da7 resourceVersion: "56000" uid: b20c1570-cc8f-4d6d-b32d-67471b301148 spec: sourcePod: network-check-source-869dcfcdcd-dtzqb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T20:34:40Z" message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.400905ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:02:40Z" - latency: 2.011658ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:01:40Z" - latency: 2.447995ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:00:40Z" - latency: 2.11274ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:59:40Z" - latency: 2.089759ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:58:40Z" - latency: 2.157434ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:57:40Z" - latency: 2.305757ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:56:40Z" - latency: 2.262705ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:55:40Z" - latency: 3.196305ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:54:40Z" - latency: 2.93768ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:53:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:27:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-138-to-network-check-target-ip-10-0-141-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-138.ec2.internal uid: 79435ba0-6ff7-4f8e-90e0-033e67550da7 resourceVersion: "56001" uid: 3252849b-2b89-41a4-9a78-f016df3b1e42 spec: sourcePod: network-check-source-869dcfcdcd-dtzqb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T20:34:40Z" message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.356164ms message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:02:40Z" - latency: 2.305424ms message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:01:40Z" - latency: 2.623698ms message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:00:40Z" - latency: 2.411215ms message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:59:40Z" - latency: 2.207494ms message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:58:40Z" - latency: 6.792208ms message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:57:40Z" - latency: 2.325212ms message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:56:40Z" - latency: 2.332124ms message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:55:40Z" - latency: 2.945914ms message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:54:40Z" - latency: 2.126616ms message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:53:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:27:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-138-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-138.ec2.internal uid: 79435ba0-6ff7-4f8e-90e0-033e67550da7 resourceVersion: "57044" uid: 99d095cb-144a-491c-9760-8b5286f1aeba spec: sourcePod: network-check-source-869dcfcdcd-dtzqb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T20:33:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 978.964µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:03:40Z" - latency: 1.771459ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:03:40Z" - latency: 805.161µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:02:40Z" - latency: 1.691395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:02:40Z" - latency: 836.552µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:01:40Z" - latency: 1.801292ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:01:40Z" - latency: 917.902µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:00:40Z" - latency: 1.806419ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:00:40Z" - latency: 901.014µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:59:40Z" - latency: 2.404563ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T20:59:40Z" kind: List metadata: resourceVersion: ""