apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:46:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-162-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-162.ec2.internal uid: 7a61dc9b-2350-4b23-86e4-19861dc9cbfa resourceVersion: "62920" uid: e5d078ec-54c7-40b5-900d-6540c0c7bdf4 spec: sourcePod: network-check-source-869dcfcdcd-pxvb5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T16:53:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.161659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:28:34Z" - latency: 1.359263ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:27:34Z" - latency: 748.692µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:26:34Z" - latency: 1.066912ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:25:34Z" - latency: 1.174377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:24:34Z" - latency: 756.528µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:23:34Z" - latency: 1.075298ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:22:34Z" - latency: 1.131932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:21:34Z" - latency: 1.086645ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:20:34Z" - latency: 1.206065ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:19:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:46:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-162-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-162.ec2.internal uid: 7a61dc9b-2350-4b23-86e4-19861dc9cbfa resourceVersion: "62921" uid: 4e174f58-dc4f-44b4-b4c1-b7fcc2329aa8 spec: sourcePod: network-check-source-869dcfcdcd-pxvb5 targetEndpoint: a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T16:52:34Z" message: 'load-balancer-api-external: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.033268ms message: 'load-balancer-api-external: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:28:34Z" - latency: 6.725626ms message: 'load-balancer-api-external: resolved host name a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:28:34Z" - latency: 4.612459ms message: 'load-balancer-api-external: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:27:34Z" - latency: 12.576653ms message: 'load-balancer-api-external: resolved host name a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:27:34Z" - latency: 5.024476ms message: 'load-balancer-api-external: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:26:34Z" - latency: 8.767505ms message: 'load-balancer-api-external: resolved host name a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:26:34Z" - latency: 4.386051ms message: 'load-balancer-api-external: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:25:34Z" - latency: 8.735282ms message: 'load-balancer-api-external: resolved host name a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:25:34Z" - latency: 3.73767ms message: 'load-balancer-api-external: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:24:34Z" - latency: 8.500211ms message: 'load-balancer-api-external: resolved host name a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:24:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:46:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-162-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-162.ec2.internal uid: 7a61dc9b-2350-4b23-86e4-19861dc9cbfa resourceVersion: "62922" uid: b131eb79-274e-487d-bece-ad6a041fcfe8 spec: sourcePod: network-check-source-869dcfcdcd-pxvb5 targetEndpoint: a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T16:52:34Z" message: 'load-balancer-api-internal: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.981759ms message: 'load-balancer-api-internal: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:28:34Z" - latency: 6.80969ms message: 'load-balancer-api-internal: resolved host name a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:28:34Z" - latency: 4.65801ms message: 'load-balancer-api-internal: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:27:34Z" - latency: 12.637039ms message: 'load-balancer-api-internal: resolved host name a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:27:34Z" - latency: 5.049293ms message: 'load-balancer-api-internal: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:26:34Z" - latency: 8.719291ms message: 'load-balancer-api-internal: resolved host name a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:26:34Z" - latency: 3.377282ms message: 'load-balancer-api-internal: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:25:34Z" - latency: 8.781684ms message: 'load-balancer-api-internal: resolved host name a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:25:34Z" - latency: 3.246713ms message: 'load-balancer-api-internal: tcp connection to a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:24:34Z" - latency: 8.566914ms message: 'load-balancer-api-internal: resolved host name a45a81a3aee2843bdaf32ca34a6404d2-d04bfb13b427714b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:24:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:46:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-162-to-network-check-target-ip-10-0-128-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-162.ec2.internal uid: 7a61dc9b-2350-4b23-86e4-19861dc9cbfa resourceVersion: "62918" uid: 57220b65-2e99-4fec-b39e-0789b052c4d4 spec: sourcePod: network-check-source-869dcfcdcd-pxvb5 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T16:53:34Z" message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.035226ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:28:34Z" - latency: 2.334991ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:27:34Z" - latency: 2.316292ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:26:34Z" - latency: 2.49983ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:25:34Z" - latency: 2.046666ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:24:34Z" - latency: 1.727625ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:23:34Z" - latency: 1.821433ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:22:34Z" - latency: 2.097209ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:21:34Z" - latency: 2.086937ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:20:34Z" - latency: 2.238528ms message: 'network-check-target-ip-10-0-128-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:19:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:46:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-162-to-network-check-target-ip-10-0-132-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-162.ec2.internal uid: 7a61dc9b-2350-4b23-86e4-19861dc9cbfa resourceVersion: "62916" uid: d059a6bb-3afd-4f15-a164-b50b38d233e0 spec: sourcePod: network-check-source-869dcfcdcd-pxvb5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T16:53:34Z" message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 794.156µs message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:28:34Z" - latency: 1.536143ms message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:27:34Z" - latency: 1.001535ms message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:26:34Z" - latency: 942.053µs message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:25:34Z" - latency: 783.592µs message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:24:34Z" - latency: 757.469µs message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:23:34Z" - latency: 898.177µs message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:22:34Z" - latency: 1.142365ms message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:21:34Z" - latency: 843.672µs message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:20:34Z" - latency: 995.861µs message: 'network-check-target-ip-10-0-132-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:19:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:46:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-162-to-network-check-target-ip-10-0-135-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-162.ec2.internal uid: 7a61dc9b-2350-4b23-86e4-19861dc9cbfa resourceVersion: "62917" uid: 704d1577-e316-4ab1-9148-ac1cc049f619 spec: sourcePod: network-check-source-869dcfcdcd-pxvb5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T16:53:34Z" message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.040555ms message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:28:34Z" - latency: 1.697288ms message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:27:34Z" - latency: 1.79649ms message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:26:34Z" - latency: 2.192151ms message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:25:34Z" - latency: 2.227939ms message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:24:34Z" - latency: 2.008082ms message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:23:34Z" - latency: 1.752893ms message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:22:34Z" - latency: 2.679207ms message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:21:34Z" - latency: 2.098189ms message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:20:34Z" - latency: 2.172353ms message: 'network-check-target-ip-10-0-135-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:19:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:46:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-162-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-162.ec2.internal uid: 7a61dc9b-2350-4b23-86e4-19861dc9cbfa resourceVersion: "62919" uid: b2c46757-7dfd-4c7e-93aa-3434a83522f5 spec: sourcePod: network-check-source-869dcfcdcd-pxvb5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T16:52:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 939.805µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:28:34Z" - latency: 1.577268ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:28:34Z" - latency: 715.769µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:27:34Z" - latency: 1.737939ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:27:34Z" - latency: 1.047212ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:26:34Z" - latency: 1.487411ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:26:34Z" - latency: 873.706µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:25:34Z" - latency: 1.897005ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:25:34Z" - latency: 848.162µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:24:34Z" - latency: 1.864766ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:24:34Z" kind: List metadata: resourceVersion: ""