apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:58:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-205-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-205.ec2.internal uid: d19be4c0-2db7-4394-a10a-6453c6dd62c1 resourceVersion: "18358" uid: be5525e5-dde1-46e0-ab45-3c540baeba2e spec: sourcePod: network-check-source-8894fc9bd-wjmcc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T20:05:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 783.006µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:12:16Z" - latency: 970.585µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:11:16Z" - latency: 994.494µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:10:16Z" - latency: 1.1938ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:09:16Z" - latency: 1.283011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:08:16Z" - latency: 1.059169ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:07:16Z" - latency: 997.015µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:06:16Z" - latency: 1.216465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:05:16Z" - latency: 1.573139ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:04:16Z" - latency: 1.022107ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:03:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:58:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-205-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-205.ec2.internal uid: d19be4c0-2db7-4394-a10a-6453c6dd62c1 resourceVersion: "20455" uid: 7789a762-3028-4c54-ab33-8a3fb8f60be8 spec: sourcePod: network-check-source-8894fc9bd-wjmcc targetEndpoint: aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T20:04:16Z" message: 'load-balancer-api-external: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.180764ms message: 'load-balancer-api-external: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:16:16Z" - latency: 9.114472ms message: 'load-balancer-api-external: resolved host name aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:16:16Z" - latency: 4.899492ms message: 'load-balancer-api-external: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:15:16Z" - latency: 9.132176ms message: 'load-balancer-api-external: resolved host name aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:15:16Z" - latency: 5.308064ms message: 'load-balancer-api-external: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:14:16Z" - latency: 8.876321ms message: 'load-balancer-api-external: resolved host name aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:14:16Z" - latency: 4.859376ms message: 'load-balancer-api-external: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:13:16Z" - latency: 6.57894ms message: 'load-balancer-api-external: resolved host name aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:13:16Z" - latency: 4.197712ms message: 'load-balancer-api-external: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:12:16Z" - latency: 9.01326ms message: 'load-balancer-api-external: resolved host name aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:12:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:58:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-205-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-205.ec2.internal uid: d19be4c0-2db7-4394-a10a-6453c6dd62c1 resourceVersion: "20454" uid: 92889303-f6ad-4502-9409-ea948a66e83d spec: sourcePod: network-check-source-8894fc9bd-wjmcc targetEndpoint: aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T20:04:16Z" message: 'load-balancer-api-internal: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.171338ms message: 'load-balancer-api-internal: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:16:16Z" - latency: 9.198181ms message: 'load-balancer-api-internal: resolved host name aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:16:16Z" - latency: 4.905804ms message: 'load-balancer-api-internal: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:15:16Z" - latency: 8.909863ms message: 'load-balancer-api-internal: resolved host name aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:15:16Z" - latency: 5.340635ms message: 'load-balancer-api-internal: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:14:16Z" - latency: 8.829193ms message: 'load-balancer-api-internal: resolved host name aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:14:16Z" - latency: 4.381917ms message: 'load-balancer-api-internal: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:13:16Z" - latency: 6.527247ms message: 'load-balancer-api-internal: resolved host name aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:13:16Z" - latency: 4.770403ms message: 'load-balancer-api-internal: tcp connection to aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:12:16Z" - latency: 9.026275ms message: 'load-balancer-api-internal: resolved host name aadf30221be9d421991eab640385e9b4-df8091dd3af36a01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:12:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:58:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-205-to-network-check-target-ip-10-0-130-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-205.ec2.internal uid: d19be4c0-2db7-4394-a10a-6453c6dd62c1 resourceVersion: "18357" uid: 6a7899b2-29a0-46a0-9664-e733b4cc911f spec: sourcePod: network-check-source-8894fc9bd-wjmcc targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:05:16Z" message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.458859ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:12:16Z" - latency: 2.386946ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:11:16Z" - latency: 2.319773ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:10:16Z" - latency: 2.234299ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:09:16Z" - latency: 2.368043ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:08:16Z" - latency: 2.27029ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:07:16Z" - latency: 2.376594ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:06:16Z" - latency: 2.273213ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:05:16Z" - latency: 2.23378ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:04:16Z" - latency: 2.32666ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:03:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:58:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-205-to-network-check-target-ip-10-0-136-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-205.ec2.internal uid: d19be4c0-2db7-4394-a10a-6453c6dd62c1 resourceVersion: "18356" uid: f02ff063-fedb-4c31-b4c5-5faef6219091 spec: sourcePod: network-check-source-8894fc9bd-wjmcc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:05:16Z" message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.336502ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:12:16Z" - latency: 2.303832ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:11:16Z" - latency: 2.183482ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:10:16Z" - latency: 2.185514ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:09:16Z" - latency: 1.883564ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:08:16Z" - latency: 2.094506ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:07:16Z" - latency: 2.268206ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:06:16Z" - latency: 2.183446ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:05:16Z" - latency: 2.349261ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:04:16Z" - latency: 2.16609ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:03:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:58:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-205-to-network-check-target-ip-10-0-139-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-205.ec2.internal uid: d19be4c0-2db7-4394-a10a-6453c6dd62c1 resourceVersion: "18355" uid: c3945ffd-5eb3-495f-abb3-714a328bdb9b spec: sourcePod: network-check-source-8894fc9bd-wjmcc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:05:16Z" message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.145199ms message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:12:16Z" - latency: 1.071578ms message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:11:16Z" - latency: 782.714µs message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:10:16Z" - latency: 941.842µs message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:09:16Z" - latency: 880.533µs message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:08:16Z" - latency: 801.16µs message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:07:16Z" - latency: 1.480923ms message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:06:16Z" - latency: 991.622µs message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:05:16Z" - latency: 927.409µs message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:04:16Z" - latency: 789.42µs message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:03:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T19:58:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-205-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-205.ec2.internal uid: d19be4c0-2db7-4394-a10a-6453c6dd62c1 resourceVersion: "20453" uid: 0414eb27-0ca2-4708-8d1c-63b35b5d12ca spec: sourcePod: network-check-source-8894fc9bd-wjmcc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T20:04:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.050245ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:16:16Z" - latency: 2.0419ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:16:16Z" - latency: 1.020496ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:15:16Z" - latency: 1.826453ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:15:16Z" - latency: 886.608µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:14:16Z" - latency: 2.026402ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:14:16Z" - latency: 850.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:13:16Z" - latency: 1.746571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:13:16Z" - latency: 736.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:12:16Z" - latency: 1.718973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:12:16Z" kind: List metadata: resourceVersion: ""