apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:40:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-178-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-178.ec2.internal uid: 68de8203-180a-4d06-99ad-590abca4ff10 resourceVersion: "32182" uid: e7f10b95-df1c-41af-b2a5-fd16f7fe886f spec: sourcePod: network-check-source-56499946bc-45t9c targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T18:47:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.140899ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:22:59Z" - latency: 956.874µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:21:59Z" - latency: 1.039434ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:20:59Z" - latency: 1.295374ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:19:59Z" - latency: 983.501µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:18:59Z" - latency: 1.160254ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:17:59Z" - latency: 941.535µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:16:59Z" - latency: 1.142098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:15:59Z" - latency: 1.229249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:14:59Z" - latency: 1.476586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:13:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:40:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-178-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-178.ec2.internal uid: 68de8203-180a-4d06-99ad-590abca4ff10 resourceVersion: "32183" uid: 955814dd-3039-421a-a0ef-58633d926af1 spec: sourcePod: network-check-source-56499946bc-45t9c targetEndpoint: a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T18:46:59Z" message: 'load-balancer-api-external: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.47934ms message: 'load-balancer-api-external: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:22:59Z" - latency: 7.384627ms message: 'load-balancer-api-external: resolved host name a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:22:59Z" - latency: 4.825226ms message: 'load-balancer-api-external: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:21:59Z" - latency: 6.839118ms message: 'load-balancer-api-external: resolved host name a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:21:59Z" - latency: 6.21522ms message: 'load-balancer-api-external: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:20:59Z" - latency: 7.570156ms message: 'load-balancer-api-external: resolved host name a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:20:59Z" - latency: 4.544996ms message: 'load-balancer-api-external: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:19:59Z" - latency: 7.711379ms message: 'load-balancer-api-external: resolved host name a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:19:59Z" - latency: 5.901078ms message: 'load-balancer-api-external: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:18:59Z" - latency: 9.616818ms message: 'load-balancer-api-external: resolved host name a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:18:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:40:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-178-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-178.ec2.internal uid: 68de8203-180a-4d06-99ad-590abca4ff10 resourceVersion: "32184" uid: 23f8d10c-f18a-48b6-8195-e15666e1256d spec: sourcePod: network-check-source-56499946bc-45t9c targetEndpoint: a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T18:46:59Z" message: 'load-balancer-api-internal: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.543736ms message: 'load-balancer-api-internal: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:22:59Z" - latency: 7.430766ms message: 'load-balancer-api-internal: resolved host name a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:22:59Z" - latency: 4.654347ms message: 'load-balancer-api-internal: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:21:59Z" - latency: 6.886236ms message: 'load-balancer-api-internal: resolved host name a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:21:59Z" - latency: 4.872659ms message: 'load-balancer-api-internal: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:20:59Z" - latency: 7.546128ms message: 'load-balancer-api-internal: resolved host name a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:20:59Z" - latency: 4.511853ms message: 'load-balancer-api-internal: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:19:59Z" - latency: 7.731331ms message: 'load-balancer-api-internal: resolved host name a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:19:59Z" - latency: 7.528266ms message: 'load-balancer-api-internal: tcp connection to a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:18:59Z" - latency: 9.697896ms message: 'load-balancer-api-internal: resolved host name a6aca39276a0c4baf9ab75240026f0ea-2b11aa60b6fc00a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:18:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:40:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-178-to-network-check-target-ip-10-0-129-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-178.ec2.internal uid: 68de8203-180a-4d06-99ad-590abca4ff10 resourceVersion: "32180" uid: f960a6c7-be52-42f2-9cdc-67a89b996284 spec: sourcePod: network-check-source-56499946bc-45t9c targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-01T18:47:59Z" message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.229622ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:22:59Z" - latency: 2.264167ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:21:59Z" - latency: 2.211011ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:20:59Z" - latency: 2.261916ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:19:59Z" - latency: 2.279619ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:18:59Z" - latency: 1.998139ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:17:59Z" - latency: 2.276532ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:16:59Z" - latency: 2.264237ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:15:59Z" - latency: 2.231613ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:14:59Z" - latency: 2.295763ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:13:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:40:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-178-to-network-check-target-ip-10-0-134-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-178.ec2.internal uid: 68de8203-180a-4d06-99ad-590abca4ff10 resourceVersion: "32181" uid: 88f189c6-3217-4d74-af70-20736b37d834 spec: sourcePod: network-check-source-56499946bc-45t9c targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T18:47:59Z" message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.357293ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:22:59Z" - latency: 2.258386ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:21:59Z" - latency: 2.205709ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:20:59Z" - latency: 2.182735ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:19:59Z" - latency: 2.004032ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:18:59Z" - latency: 2.127752ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:17:59Z" - latency: 2.377252ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:16:59Z" - latency: 2.293127ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:15:59Z" - latency: 2.185644ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:14:59Z" - latency: 2.368617ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:13:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:40:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-178-to-network-check-target-ip-10-0-139-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-178.ec2.internal uid: 68de8203-180a-4d06-99ad-590abca4ff10 resourceVersion: "32178" uid: 244225a6-9bea-49aa-9254-064d447a4447 spec: sourcePod: network-check-source-56499946bc-45t9c targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T18:47:59Z" message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 867.539µs message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:22:59Z" - latency: 1.024991ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:21:59Z" - latency: 1.166601ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:20:59Z" - latency: 933.718µs message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:19:59Z" - latency: 1.044857ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:18:59Z" - latency: 877.266µs message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:17:59Z" - latency: 1.161978ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:16:59Z" - latency: 1.00956ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:15:59Z" - latency: 932.018µs message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:14:59Z" - latency: 974.73µs message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:13:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T18:40:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-178-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-178.ec2.internal uid: 68de8203-180a-4d06-99ad-590abca4ff10 resourceVersion: "32179" uid: 64b9b0d0-61d8-4e6d-8e01-e9e9b8e25688 spec: sourcePod: network-check-source-56499946bc-45t9c targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T18:46:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.902µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:22:59Z" - latency: 1.915012ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:22:59Z" - latency: 900.259µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:21:59Z" - latency: 1.703906ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:21:59Z" - latency: 1.2981ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:20:59Z" - latency: 1.850333ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:20:59Z" - latency: 862.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:19:59Z" - latency: 2.02091ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:19:59Z" - latency: 856.742µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:18:59Z" - latency: 1.679297ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:18:59Z" kind: List metadata: resourceVersion: ""