apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T11:37:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-96-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-96.ec2.internal uid: aec953b5-94b6-4ec0-9440-003e14f3d787 resourceVersion: "17461" uid: 838cbe4b-5d2e-4fee-b930-a46e1cb6111d spec: sourcePod: network-check-source-7bc5b6bf85-ztckp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T11:44:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 979.422µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:44:12Z" - latency: 888.176µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:43:12Z" - latency: 773.273µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:42:12Z" - latency: 927.34µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:41:12Z" - latency: 1.149935ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:40:12Z" - latency: 1.069242ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:39:12Z" - latency: 1.094322ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:38:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T11:37:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-96-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-96.ec2.internal uid: aec953b5-94b6-4ec0-9440-003e14f3d787 resourceVersion: "19721" uid: 5c21a768-fa93-42a9-9de6-ea723cbadc94 spec: sourcePod: network-check-source-7bc5b6bf85-ztckp targetEndpoint: ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T11:43:12Z" message: 'load-balancer-api-external: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.509272ms message: 'load-balancer-api-external: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:49:12Z" - latency: 8.842485ms message: 'load-balancer-api-external: resolved host name ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:49:12Z" - latency: 5.835908ms message: 'load-balancer-api-external: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:48:12Z" - latency: 7.753153ms message: 'load-balancer-api-external: resolved host name ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:48:12Z" - latency: 5.138003ms message: 'load-balancer-api-external: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:47:12Z" - latency: 6.47778ms message: 'load-balancer-api-external: resolved host name ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:47:12Z" - latency: 5.130845ms message: 'load-balancer-api-external: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:46:12Z" - latency: 7.39526ms message: 'load-balancer-api-external: resolved host name ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:46:12Z" - latency: 5.058999ms message: 'load-balancer-api-external: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:45:12Z" - latency: 6.646914ms message: 'load-balancer-api-external: resolved host name ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:45:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T11:37:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-96-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-96.ec2.internal uid: aec953b5-94b6-4ec0-9440-003e14f3d787 resourceVersion: "19720" uid: c8f18c7c-d915-4949-a160-1203b958e72b spec: sourcePod: network-check-source-7bc5b6bf85-ztckp targetEndpoint: ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T11:43:12Z" message: 'load-balancer-api-internal: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.44196ms message: 'load-balancer-api-internal: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:49:12Z" - latency: 8.867683ms message: 'load-balancer-api-internal: resolved host name ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:49:12Z" - latency: 5.810107ms message: 'load-balancer-api-internal: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:48:12Z" - latency: 7.796788ms message: 'load-balancer-api-internal: resolved host name ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:48:12Z" - latency: 5.841049ms message: 'load-balancer-api-internal: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:47:12Z" - latency: 6.499117ms message: 'load-balancer-api-internal: resolved host name ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:47:12Z" - latency: 5.146974ms message: 'load-balancer-api-internal: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:46:12Z" - latency: 7.44456ms message: 'load-balancer-api-internal: resolved host name ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:46:12Z" - latency: 5.086308ms message: 'load-balancer-api-internal: tcp connection to ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:45:12Z" - latency: 6.585163ms message: 'load-balancer-api-internal: resolved host name ab2f1e529851f4a5ebac62eef5c9a8e7-67214cdc43c6439d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:45:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T11:37:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-96-to-network-check-target-ip-10-0-136-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-96.ec2.internal uid: aec953b5-94b6-4ec0-9440-003e14f3d787 resourceVersion: "17460" uid: 3ecd8238-f969-4a51-903e-b28617466f40 spec: sourcePod: network-check-source-7bc5b6bf85-ztckp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T11:44:12Z" message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.84515ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:44:12Z" - latency: 2.20376ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:43:12Z" - latency: 1.763012ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:42:12Z" - latency: 1.965783ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:41:12Z" - latency: 2.05341ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:40:12Z" - latency: 2.422944ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:39:12Z" - latency: 2.242169ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:38:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T11:37:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-96-to-network-check-target-ip-10-0-141-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-96.ec2.internal uid: aec953b5-94b6-4ec0-9440-003e14f3d787 resourceVersion: "17458" uid: 97ba0660-d363-4716-880f-62481c037438 spec: sourcePod: network-check-source-7bc5b6bf85-ztckp targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T11:44:12Z" message: 'network-check-target-ip-10-0-141-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.753µs message: 'network-check-target-ip-10-0-141-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:44:12Z" - latency: 903.686µs message: 'network-check-target-ip-10-0-141-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:43:12Z" - latency: 859.317µs message: 'network-check-target-ip-10-0-141-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:42:12Z" - latency: 1.039798ms message: 'network-check-target-ip-10-0-141-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:41:12Z" - latency: 877.023µs message: 'network-check-target-ip-10-0-141-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:40:12Z" - latency: 938.406µs message: 'network-check-target-ip-10-0-141-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:39:12Z" - latency: 1.599157ms message: 'network-check-target-ip-10-0-141-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:38:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T11:37:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-96-to-network-check-target-ip-10-0-142-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-96.ec2.internal uid: aec953b5-94b6-4ec0-9440-003e14f3d787 resourceVersion: "17459" uid: c67c0b6e-9a4e-4268-8288-b4ea3747ed15 spec: sourcePod: network-check-source-7bc5b6bf85-ztckp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T11:44:12Z" message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.910886ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:44:12Z" - latency: 1.874908ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:43:12Z" - latency: 1.852511ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:42:12Z" - latency: 1.889545ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:41:12Z" - latency: 1.936855ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:40:12Z" - latency: 2.203783ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:39:12Z" - latency: 2.203604ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:38:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T11:37:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-96-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-96.ec2.internal uid: aec953b5-94b6-4ec0-9440-003e14f3d787 resourceVersion: "19719" uid: 64be4272-86e4-4ab2-9169-c38fff4a1b31 spec: sourcePod: network-check-source-7bc5b6bf85-ztckp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T11:43:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 754.907µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:49:12Z" - latency: 2.079658ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:49:12Z" - latency: 775.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:48:12Z" - latency: 1.692624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:48:12Z" - latency: 857.495µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:47:12Z" - latency: 1.745264ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:47:12Z" - latency: 822.33µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:46:12Z" - latency: 1.788158ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:46:12Z" - latency: 898.143µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:45:12Z" - latency: 1.827696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:45:12Z" kind: List metadata: resourceVersion: ""