apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:44:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-142-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-142.ec2.internal uid: 46f9abf5-8938-49c2-bbfc-a5792c1bbbba resourceVersion: "43919" uid: 4663cc0c-1cad-4721-aee1-f7bf1edb30bd spec: sourcePod: network-check-source-7f44b6dd87-5nhgx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T19:51:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.091095ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:33Z" - latency: 1.461067ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:33Z" - latency: 996.509µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:33Z" - latency: 1.45493ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:09:33Z" - latency: 1.028091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:08:33Z" - latency: 895.214µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:07:33Z" - latency: 1.150973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:06:33Z" - latency: 1.02447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:05:33Z" - latency: 1.50649ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:04:33Z" - latency: 932.619µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:03:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:44:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-142-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-142.ec2.internal uid: 46f9abf5-8938-49c2-bbfc-a5792c1bbbba resourceVersion: "46201" uid: 4c3e64bd-9e70-43e9-9a4f-d60f1178c92d spec: sourcePod: network-check-source-7f44b6dd87-5nhgx targetEndpoint: adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T19:50:33Z" message: 'load-balancer-api-external: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.430476ms message: 'load-balancer-api-external: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:14:33Z" - latency: 6.209354ms message: 'load-balancer-api-external: resolved host name adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:14:33Z" - latency: 2.954942ms message: 'load-balancer-api-external: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:13:33Z" - latency: 8.076175ms message: 'load-balancer-api-external: resolved host name adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:13:33Z" - latency: 3.699107ms message: 'load-balancer-api-external: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:33Z" - latency: 7.764361ms message: 'load-balancer-api-external: resolved host name adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:12:33Z" - latency: 3.046239ms message: 'load-balancer-api-external: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:33Z" - latency: 6.37894ms message: 'load-balancer-api-external: resolved host name adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:11:33Z" - latency: 4.880739ms message: 'load-balancer-api-external: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:33Z" - latency: 6.136246ms message: 'load-balancer-api-external: resolved host name adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:10:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:44:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-142-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-142.ec2.internal uid: 46f9abf5-8938-49c2-bbfc-a5792c1bbbba resourceVersion: "46200" uid: 77e72c91-5ccf-4d1e-a868-590dfd51dc0f spec: sourcePod: network-check-source-7f44b6dd87-5nhgx targetEndpoint: adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T19:50:33Z" message: 'load-balancer-api-internal: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.466449ms message: 'load-balancer-api-internal: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:14:33Z" - latency: 6.157111ms message: 'load-balancer-api-internal: resolved host name adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:14:33Z" - latency: 4.295839ms message: 'load-balancer-api-internal: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:13:33Z" - latency: 8.131122ms message: 'load-balancer-api-internal: resolved host name adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:13:33Z" - latency: 4.236415ms message: 'load-balancer-api-internal: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:33Z" - latency: 7.742424ms message: 'load-balancer-api-internal: resolved host name adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:12:33Z" - latency: 2.991865ms message: 'load-balancer-api-internal: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:33Z" - latency: 6.470066ms message: 'load-balancer-api-internal: resolved host name adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:11:33Z" - latency: 4.446175ms message: 'load-balancer-api-internal: tcp connection to adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:33Z" - latency: 6.21243ms message: 'load-balancer-api-internal: resolved host name adf1fe575c78e44f18a7875505c7e7e5-6f9d8ad938bbbab1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:10:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:44:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-142-to-network-check-target-ip-10-0-129-255 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-142.ec2.internal uid: 46f9abf5-8938-49c2-bbfc-a5792c1bbbba resourceVersion: "43918" uid: 47d8a6c5-2da2-4977-9f69-05a7ef9716e3 spec: sourcePod: network-check-source-7f44b6dd87-5nhgx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T19:51:33Z" message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.332129ms message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:33Z" - latency: 2.015241ms message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:33Z" - latency: 2.670876ms message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:33Z" - latency: 1.905882ms message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:09:33Z" - latency: 2.235801ms message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:08:33Z" - latency: 2.254817ms message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:07:33Z" - latency: 2.234085ms message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:06:33Z" - latency: 2.229337ms message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:05:33Z" - latency: 2.073882ms message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:04:33Z" - latency: 2.41458ms message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:03:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:44:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-142-to-network-check-target-ip-10-0-137-200 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-142.ec2.internal uid: 46f9abf5-8938-49c2-bbfc-a5792c1bbbba resourceVersion: "43917" uid: 48945285-b43b-478b-8a4e-44aff456956d spec: sourcePod: network-check-source-7f44b6dd87-5nhgx targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T19:51:33Z" message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.239837ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:33Z" - latency: 2.142936ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:33Z" - latency: 2.24155ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:33Z" - latency: 2.264432ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:09:33Z" - latency: 2.256313ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:08:33Z" - latency: 2.155624ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:07:33Z" - latency: 2.34147ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:06:33Z" - latency: 2.343242ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:05:33Z" - latency: 2.923168ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:04:33Z" - latency: 2.303872ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:03:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:44:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-142-to-network-check-target-ip-10-0-140-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-142.ec2.internal uid: 46f9abf5-8938-49c2-bbfc-a5792c1bbbba resourceVersion: "43916" uid: d9953664-4f82-46af-ac53-4a471555144c spec: sourcePod: network-check-source-7f44b6dd87-5nhgx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T19:51:33Z" message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 794.766µs message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:33Z" - latency: 776.009µs message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:33Z" - latency: 869.442µs message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:33Z" - latency: 788.182µs message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:09:33Z" - latency: 827.082µs message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:08:33Z" - latency: 830.329µs message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:07:33Z" - latency: 1.17409ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:06:33Z" - latency: 857.538µs message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:05:33Z" - latency: 818.535µs message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:04:33Z" - latency: 1.121059ms message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:03:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:44:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-142-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-142.ec2.internal uid: 46f9abf5-8938-49c2-bbfc-a5792c1bbbba resourceVersion: "46199" uid: b3d1642d-4875-4c27-b11c-4220fcfb7294 spec: sourcePod: network-check-source-7f44b6dd87-5nhgx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T19:50:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 968.549µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:14:33Z" - latency: 1.603756ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T20:14:33Z" - latency: 837.748µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:13:33Z" - latency: 1.931309ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T20:13:33Z" - latency: 809.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:33Z" - latency: 1.564834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T20:12:33Z" - latency: 860.793µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:33Z" - latency: 1.663523ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T20:11:33Z" - latency: 1.496927ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:33Z" - latency: 1.692378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T20:10:33Z" kind: List metadata: resourceVersion: ""