apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-191-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-191.ec2.internal uid: e14de915-7cd9-4a9f-b258-8d741fc491e7 resourceVersion: "54695" uid: 4b449a32-1a94-4d70-8d5b-cdbf336aae5a spec: sourcePod: network-check-source-989f8b8dc-6j68f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-05T13:28:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.021412ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:49Z" - latency: 1.076151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:49Z" - latency: 1.296116ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:49Z" - latency: 1.17941ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:49Z" - latency: 975.646µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:49Z" - latency: 1.099198ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:49Z" - latency: 877.844µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:49Z" - latency: 1.17979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:49Z" - latency: 911.335µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:48:49Z" - latency: 922.18µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:47:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-191-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-191.ec2.internal uid: e14de915-7cd9-4a9f-b258-8d741fc491e7 resourceVersion: "55668" uid: 59c86986-81bb-4493-a6bd-aa9eee6990ab spec: sourcePod: network-check-source-989f8b8dc-6j68f targetEndpoint: af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-05T13:27:49Z" message: 'load-balancer-api-external: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.782424ms message: 'load-balancer-api-external: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:49Z" - latency: 7.078659ms message: 'load-balancer-api-external: resolved host name af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:57:49Z" - latency: 5.227097ms message: 'load-balancer-api-external: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:49Z" - latency: 9.340082ms message: 'load-balancer-api-external: resolved host name af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:56:49Z" - latency: 5.043819ms message: 'load-balancer-api-external: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:49Z" - latency: 8.476669ms message: 'load-balancer-api-external: resolved host name af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:55:49Z" - latency: 3.90763ms message: 'load-balancer-api-external: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:49Z" - latency: 7.52018ms message: 'load-balancer-api-external: resolved host name af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:54:49Z" - latency: 5.003131ms message: 'load-balancer-api-external: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:49Z" - latency: 8.193183ms message: 'load-balancer-api-external: resolved host name af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:53:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-191-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-191.ec2.internal uid: e14de915-7cd9-4a9f-b258-8d741fc491e7 resourceVersion: "55667" uid: 27032f7d-9e3e-43e9-84ce-7cd2ab4d887d spec: sourcePod: network-check-source-989f8b8dc-6j68f targetEndpoint: af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-05T13:27:49Z" message: 'load-balancer-api-internal: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.704317ms message: 'load-balancer-api-internal: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:49Z" - latency: 7.224699ms message: 'load-balancer-api-internal: resolved host name af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:57:49Z" - latency: 4.642828ms message: 'load-balancer-api-internal: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:49Z" - latency: 9.483134ms message: 'load-balancer-api-internal: resolved host name af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:56:49Z" - latency: 4.994082ms message: 'load-balancer-api-internal: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:49Z" - latency: 8.559682ms message: 'load-balancer-api-internal: resolved host name af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:55:49Z" - latency: 3.886375ms message: 'load-balancer-api-internal: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:49Z" - latency: 7.566974ms message: 'load-balancer-api-internal: resolved host name af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:54:49Z" - latency: 4.519041ms message: 'load-balancer-api-internal: tcp connection to af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:49Z" - latency: 8.295707ms message: 'load-balancer-api-internal: resolved host name af265d907616d4d3e8aed774ad652eba-491bdfe90b816103.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:53:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-191-to-network-check-target-ip-10-0-129-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-191.ec2.internal uid: e14de915-7cd9-4a9f-b258-8d741fc491e7 resourceVersion: "54694" uid: 161ccc9c-0ea2-4e71-895e-78523f62fa5b spec: sourcePod: network-check-source-989f8b8dc-6j68f targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-05T13:28:49Z" message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.236642ms message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:49Z" - latency: 2.252771ms message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:49Z" - latency: 2.436598ms message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:49Z" - latency: 2.409813ms message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:49Z" - latency: 1.878292ms message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:49Z" - latency: 2.224444ms message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:49Z" - latency: 2.478934ms message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:49Z" - latency: 2.31945ms message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:49Z" - latency: 1.848696ms message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:48:49Z" - latency: 2.166255ms message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:47:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-191-to-network-check-target-ip-10-0-130-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-191.ec2.internal uid: e14de915-7cd9-4a9f-b258-8d741fc491e7 resourceVersion: "54692" uid: 69186ff1-1788-4f3f-9cd6-df2afade591e spec: sourcePod: network-check-source-989f8b8dc-6j68f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-05T13:28:49Z" message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.303783ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:49Z" - latency: 906.996µs message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:49Z" - latency: 1.721699ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:49Z" - latency: 1.015403ms message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:49Z" - latency: 865.008µs message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:49Z" - latency: 956.008µs message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:49Z" - latency: 986.115µs message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:49Z" - latency: 981.008µs message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:49Z" - latency: 843.109µs message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:48:49Z" - latency: 804.597µs message: 'network-check-target-ip-10-0-130-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:47:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-191-to-network-check-target-ip-10-0-134-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-191.ec2.internal uid: e14de915-7cd9-4a9f-b258-8d741fc491e7 resourceVersion: "54693" uid: bfdaa6d1-8637-4249-a6b3-a73724da0b59 spec: sourcePod: network-check-source-989f8b8dc-6j68f targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-05T13:28:49Z" message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.448141ms message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:49Z" - latency: 2.487898ms message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:49Z" - latency: 2.33263ms message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:49Z" - latency: 2.479901ms message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:49Z" - latency: 2.170948ms message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:49Z" - latency: 2.202952ms message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:49Z" - latency: 2.209251ms message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:49Z" - latency: 2.736526ms message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:49Z" - latency: 1.985209ms message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:48:49Z" - latency: 2.253448ms message: 'network-check-target-ip-10-0-134-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:47:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:21:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-191-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-191.ec2.internal uid: e14de915-7cd9-4a9f-b258-8d741fc491e7 resourceVersion: "55666" uid: c3bbce9d-bf61-4889-a139-980d3febb442 spec: sourcePod: network-check-source-989f8b8dc-6j68f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-05T13:27:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 905.453µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:49Z" - latency: 2.024692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:57:49Z" - latency: 1.063544ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:49Z" - latency: 2.219491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:56:49Z" - latency: 986.283µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:49Z" - latency: 2.110694ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:55:49Z" - latency: 1.256341ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:49Z" - latency: 1.905275ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:54:49Z" - latency: 843.003µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:49Z" - latency: 1.553421ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:53:49Z" kind: List metadata: resourceVersion: ""