apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:01:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-183-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-183.ec2.internal uid: cb9ac042-b675-4d5f-9625-e7badb1725f6 resourceVersion: "54252" uid: ed852126-e3fa-4519-82fb-67ede06e8683 spec: sourcePod: network-check-source-869dcfcdcd-n55wp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T22:08:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.132996ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:18Z" - latency: 1.177388ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:35:18Z" - latency: 1.293397ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:34:18Z" - latency: 1.276124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:33:18Z" - latency: 1.539828ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:32:18Z" - latency: 3.371269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:31:18Z" - latency: 1.162024ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:30:18Z" - latency: 1.115614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:29:18Z" - latency: 865.649µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:28:18Z" - latency: 1.458571ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:27:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:01:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-183-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-183.ec2.internal uid: cb9ac042-b675-4d5f-9625-e7badb1725f6 resourceVersion: "55190" uid: 071ed9cf-ed80-4df4-9e9b-fbba093a4b91 spec: sourcePod: network-check-source-869dcfcdcd-n55wp targetEndpoint: ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T22:07:18Z" message: 'load-balancer-api-external: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.33117ms message: 'load-balancer-api-external: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:37:18Z" - latency: 8.767819ms message: 'load-balancer-api-external: resolved host name ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:37:18Z" - latency: 3.400901ms message: 'load-balancer-api-external: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:18Z" - latency: 18.523651ms message: 'load-balancer-api-external: resolved host name ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:36:18Z" - latency: 4.887578ms message: 'load-balancer-api-external: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:35:18Z" - latency: 9.573617ms message: 'load-balancer-api-external: resolved host name ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:35:18Z" - latency: 4.626642ms message: 'load-balancer-api-external: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:34:18Z" - latency: 9.800919ms message: 'load-balancer-api-external: resolved host name ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:34:18Z" - latency: 4.070004ms message: 'load-balancer-api-external: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:33:18Z" - latency: 8.806756ms message: 'load-balancer-api-external: resolved host name ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:33:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:01:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-183-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-183.ec2.internal uid: cb9ac042-b675-4d5f-9625-e7badb1725f6 resourceVersion: "55189" uid: 4d7e8a50-e5bd-4f4c-90f3-5a147ff24db8 spec: sourcePod: network-check-source-869dcfcdcd-n55wp targetEndpoint: ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T22:07:18Z" message: 'load-balancer-api-internal: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.381075ms message: 'load-balancer-api-internal: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:37:18Z" - latency: 8.918893ms message: 'load-balancer-api-internal: resolved host name ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:37:18Z" - latency: 3.373209ms message: 'load-balancer-api-internal: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:18Z" - latency: 18.594916ms message: 'load-balancer-api-internal: resolved host name ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:36:18Z" - latency: 4.928025ms message: 'load-balancer-api-internal: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:35:18Z" - latency: 9.636898ms message: 'load-balancer-api-internal: resolved host name ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:35:18Z" - latency: 4.638147ms message: 'load-balancer-api-internal: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:34:18Z" - latency: 9.87137ms message: 'load-balancer-api-internal: resolved host name ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:34:18Z" - latency: 5.434971ms message: 'load-balancer-api-internal: tcp connection to ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:33:18Z" - latency: 8.85691ms message: 'load-balancer-api-internal: resolved host name ad9e34a3b852d49e2aad3022de92a593-49e65670cc83d147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T22:33:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:01:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-183-to-network-check-target-ip-10-0-133-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-183.ec2.internal uid: cb9ac042-b675-4d5f-9625-e7badb1725f6 resourceVersion: "54251" uid: b184c781-f1cf-4297-bff0-5a684d67a5da spec: sourcePod: network-check-source-869dcfcdcd-n55wp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T22:08:18Z" message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.789818ms message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:18Z" - latency: 2.457301ms message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:35:18Z" - latency: 2.419323ms message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:34:18Z" - latency: 2.936276ms message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:33:18Z" - latency: 2.995346ms message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:32:18Z" - latency: 4.267472ms message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:31:18Z" - latency: 2.627947ms message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:30:18Z" - latency: 2.444023ms message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:29:18Z" - latency: 2.262847ms message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:28:18Z" - latency: 2.34321ms message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:27:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:01:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-183-to-network-check-target-ip-10-0-137-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-183.ec2.internal uid: cb9ac042-b675-4d5f-9625-e7badb1725f6 resourceVersion: "54249" uid: f4b642f7-3004-4596-950f-3ba21630af97 spec: sourcePod: network-check-source-869dcfcdcd-n55wp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T22:08:18Z" message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.559297ms message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:18Z" - latency: 932.457µs message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:35:18Z" - latency: 1.521721ms message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:34:18Z" - latency: 1.822453ms message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:33:18Z" - latency: 2.211173ms message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:32:18Z" - latency: 2.629976ms message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:31:18Z" - latency: 1.70082ms message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:30:18Z" - latency: 1.767025ms message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:29:18Z" - latency: 839.25µs message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:28:18Z" - latency: 1.069629ms message: 'network-check-target-ip-10-0-137-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:27:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:01:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-183-to-network-check-target-ip-10-0-143-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-183.ec2.internal uid: cb9ac042-b675-4d5f-9625-e7badb1725f6 resourceVersion: "54250" uid: 36c7b0cb-be22-434f-b38e-e24469f577f1 spec: sourcePod: network-check-source-869dcfcdcd-n55wp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-13T22:08:18Z" message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.519409ms message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:18Z" - latency: 2.533544ms message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:35:18Z" - latency: 2.612059ms message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:34:18Z" - latency: 2.888014ms message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:33:18Z" - latency: 2.555532ms message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:32:18Z" - latency: 3.460836ms message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:31:18Z" - latency: 2.345913ms message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:30:18Z" - latency: 2.398905ms message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:29:18Z" - latency: 1.770717ms message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:28:18Z" - latency: 2.239517ms message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:27:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T22:01:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-183-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-183.ec2.internal uid: cb9ac042-b675-4d5f-9625-e7badb1725f6 resourceVersion: "55187" uid: 4e75d2b3-7b83-4598-b516-a6ef4e1994fa spec: sourcePod: network-check-source-869dcfcdcd-n55wp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T22:07:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.251991ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:37:18Z" - latency: 1.799858ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T22:37:18Z" - latency: 1.010369ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:36:18Z" - latency: 1.725097ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T22:36:18Z" - latency: 1.029321ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:35:18Z" - latency: 2.5602ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T22:35:18Z" - latency: 1.214893ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:34:18Z" - latency: 2.34278ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T22:34:18Z" - latency: 946.325µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T22:33:18Z" - latency: 2.649272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T22:33:18Z" kind: List metadata: resourceVersion: ""