apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T14:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-215-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-215.ec2.internal uid: fe6db6bd-7632-4871-88b6-92beb86aa336 resourceVersion: "44162" uid: cf9d6c21-ad4c-49f5-8585-178a5c56e5c5 spec: sourcePod: network-check-source-8894fc9bd-2pchd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T14:33:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.022378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:54:53Z" - latency: 1.034985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:53:53Z" - latency: 902.263µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:52:53Z" - latency: 1.099247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:51:53Z" - latency: 1.272473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:50:53Z" - latency: 1.468574ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:49:53Z" - latency: 917.541µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:48:53Z" - latency: 958.764µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:47:53Z" - latency: 833.292µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:46:53Z" - latency: 1.172125ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:45:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T14:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-215-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-215.ec2.internal uid: fe6db6bd-7632-4871-88b6-92beb86aa336 resourceVersion: "39701" uid: e72f1443-ac87-46b0-b0e2-726f9a870b66 spec: sourcePod: network-check-source-8894fc9bd-2pchd targetEndpoint: af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T14:32:53Z" message: 'load-balancer-api-external: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.939052ms message: 'load-balancer-api-external: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:50:53Z" - latency: 8.478793ms message: 'load-balancer-api-external: resolved host name af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T14:50:53Z" - latency: 4.900675ms message: 'load-balancer-api-external: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:49:53Z" - latency: 9.458102ms message: 'load-balancer-api-external: resolved host name af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T14:49:53Z" - latency: 4.464714ms message: 'load-balancer-api-external: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:48:53Z" - latency: 9.685109ms message: 'load-balancer-api-external: resolved host name af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T14:48:53Z" - latency: 4.354534ms message: 'load-balancer-api-external: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:47:53Z" - latency: 8.252569ms message: 'load-balancer-api-external: resolved host name af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T14:47:53Z" - latency: 7.25945ms message: 'load-balancer-api-external: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:46:53Z" - latency: 8.3395ms message: 'load-balancer-api-external: resolved host name af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T14:46:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T14:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-215-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-215.ec2.internal uid: fe6db6bd-7632-4871-88b6-92beb86aa336 resourceVersion: "39700" uid: 27845afe-6e46-4c5e-a3da-82a7176d6798 spec: sourcePod: network-check-source-8894fc9bd-2pchd targetEndpoint: af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T14:32:53Z" message: 'load-balancer-api-internal: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.769488ms message: 'load-balancer-api-internal: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:50:53Z" - latency: 8.524327ms message: 'load-balancer-api-internal: resolved host name af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T14:50:53Z" - latency: 3.697093ms message: 'load-balancer-api-internal: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:49:53Z" - latency: 9.542644ms message: 'load-balancer-api-internal: resolved host name af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T14:49:53Z" - latency: 4.469084ms message: 'load-balancer-api-internal: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:48:53Z" - latency: 9.656135ms message: 'load-balancer-api-internal: resolved host name af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T14:48:53Z" - latency: 4.17654ms message: 'load-balancer-api-internal: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:47:53Z" - latency: 8.32756ms message: 'load-balancer-api-internal: resolved host name af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T14:47:53Z" - latency: 7.251756ms message: 'load-balancer-api-internal: tcp connection to af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:46:53Z" - latency: 8.409374ms message: 'load-balancer-api-internal: resolved host name af06543d9ceda4e26bac588756568586-049405f6133ca6b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T14:46:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T14:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-215-to-network-check-target-ip-10-0-132-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-215.ec2.internal uid: fe6db6bd-7632-4871-88b6-92beb86aa336 resourceVersion: "44161" uid: d51caca1-7d6d-4599-9099-58f0fcde97be spec: sourcePod: network-check-source-8894fc9bd-2pchd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T14:33:53Z" message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.424417ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:54:53Z" - latency: 2.215919ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:53:53Z" - latency: 2.550866ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:52:53Z" - latency: 2.253115ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:51:53Z" - latency: 1.755385ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:50:53Z" - latency: 2.285046ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:49:53Z" - latency: 2.199704ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:48:53Z" - latency: 2.134304ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:47:53Z" - latency: 2.740511ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:46:53Z" - latency: 1.70736ms message: 'network-check-target-ip-10-0-132-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:45:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T14:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-215-to-network-check-target-ip-10-0-138-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-215.ec2.internal uid: fe6db6bd-7632-4871-88b6-92beb86aa336 resourceVersion: "44160" uid: 67031fe5-68ac-444a-87ba-3dbafa2f9ebd spec: sourcePod: network-check-source-8894fc9bd-2pchd targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T14:33:53Z" message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.038635ms message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:54:53Z" - latency: 2.038472ms message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:53:53Z" - latency: 2.758916ms message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:52:53Z" - latency: 2.087835ms message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:51:53Z" - latency: 2.033689ms message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:50:53Z" - latency: 1.807185ms message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:49:53Z" - latency: 2.273345ms message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:48:53Z" - latency: 2.179853ms message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:47:53Z" - latency: 2.165266ms message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:46:53Z" - latency: 2.181601ms message: 'network-check-target-ip-10-0-138-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:45:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T14:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-215-to-network-check-target-ip-10-0-143-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-215.ec2.internal uid: fe6db6bd-7632-4871-88b6-92beb86aa336 resourceVersion: "44159" uid: 784843e8-9acb-4ca0-b279-4f8c9265f9a4 spec: sourcePod: network-check-source-8894fc9bd-2pchd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T14:33:53Z" message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.165772ms message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:54:53Z" - latency: 685.327µs message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:53:53Z" - latency: 1.268207ms message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:52:53Z" - latency: 853.279µs message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:51:53Z" - latency: 874.917µs message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:50:53Z" - latency: 1.164458ms message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:49:53Z" - latency: 866.812µs message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:48:53Z" - latency: 790.25µs message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:47:53Z" - latency: 814.571µs message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:46:53Z" - latency: 778.863µs message: 'network-check-target-ip-10-0-143-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:45:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T14:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-215-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-215.ec2.internal uid: fe6db6bd-7632-4871-88b6-92beb86aa336 resourceVersion: "39699" uid: 21179fdf-f4c6-42f7-af1e-f7974abbfd0d spec: sourcePod: network-check-source-8894fc9bd-2pchd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T14:32:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 738.45µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:50:53Z" - latency: 1.633619ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T14:50:53Z" - latency: 877.612µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:49:53Z" - latency: 1.805648ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T14:49:53Z" - latency: 894.414µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:48:53Z" - latency: 1.695093ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T14:48:53Z" - latency: 1.206608ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:47:53Z" - latency: 2.037038ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T14:47:53Z" - latency: 855.918µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T14:46:53Z" - latency: 1.71643ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T14:46:53Z" kind: List metadata: resourceVersion: ""