apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-115-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-115.ec2.internal uid: 333aac46-7d31-4e7f-b2b0-a4cd0c344d96 resourceVersion: "63075" uid: fcb4ed16-10f0-45ab-829a-dc94ba867d37 spec: sourcePod: network-check-source-869dcfcdcd-n2wvf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T18:08:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.106793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:43:57Z" - latency: 871.098µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:42:57Z" - latency: 1.082142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:41:57Z" - latency: 921.193µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:40:57Z" - latency: 995.54µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:39:57Z" - latency: 912.293µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:38:57Z" - latency: 925.397µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:37:57Z" - latency: 878.784µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:36:57Z" - latency: 1.028085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:35:57Z" - latency: 889.094µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:34:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-115-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-115.ec2.internal uid: 333aac46-7d31-4e7f-b2b0-a4cd0c344d96 resourceVersion: "63077" uid: 1a69b2a3-fc26-45eb-820e-7263f1ffe24d spec: sourcePod: network-check-source-869dcfcdcd-n2wvf targetEndpoint: a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T18:07:57Z" message: 'load-balancer-api-external: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.731507ms message: 'load-balancer-api-external: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:43:57Z" - latency: 6.04792ms message: 'load-balancer-api-external: resolved host name a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:43:57Z" - latency: 5.738833ms message: 'load-balancer-api-external: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:42:57Z" - latency: 6.916294ms message: 'load-balancer-api-external: resolved host name a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:42:57Z" - latency: 7.056264ms message: 'load-balancer-api-external: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:41:57Z" - latency: 6.453846ms message: 'load-balancer-api-external: resolved host name a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:41:57Z" - latency: 5.449087ms message: 'load-balancer-api-external: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:40:57Z" - latency: 9.042694ms message: 'load-balancer-api-external: resolved host name a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:40:57Z" - latency: 4.170191ms message: 'load-balancer-api-external: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:39:57Z" - latency: 6.325777ms message: 'load-balancer-api-external: resolved host name a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:39:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-115-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-115.ec2.internal uid: 333aac46-7d31-4e7f-b2b0-a4cd0c344d96 resourceVersion: "63076" uid: 5b63f285-ba58-4030-b65c-ae581d3f7a71 spec: sourcePod: network-check-source-869dcfcdcd-n2wvf targetEndpoint: a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T18:07:57Z" message: 'load-balancer-api-internal: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.438365ms message: 'load-balancer-api-internal: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:43:57Z" - latency: 5.987597ms message: 'load-balancer-api-internal: resolved host name a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:43:57Z" - latency: 5.128281ms message: 'load-balancer-api-internal: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:42:57Z" - latency: 6.873524ms message: 'load-balancer-api-internal: resolved host name a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:42:57Z" - latency: 7.026063ms message: 'load-balancer-api-internal: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:41:57Z" - latency: 6.390111ms message: 'load-balancer-api-internal: resolved host name a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:41:57Z" - latency: 5.058956ms message: 'load-balancer-api-internal: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:40:57Z" - latency: 8.963653ms message: 'load-balancer-api-internal: resolved host name a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:40:57Z" - latency: 4.167652ms message: 'load-balancer-api-internal: tcp connection to a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:39:57Z" - latency: 6.30195ms message: 'load-balancer-api-internal: resolved host name a20d6a651866a4cf0b1595ef275ba133-2ecee0cf8f05bb4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T18:39:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-115-to-network-check-target-ip-10-0-129-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-115.ec2.internal uid: 333aac46-7d31-4e7f-b2b0-a4cd0c344d96 resourceVersion: "63071" uid: 7402d4b0-4a27-4f06-b75a-c01d4dd82fe3 spec: sourcePod: network-check-source-869dcfcdcd-n2wvf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T18:08:57Z" message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 969.542µs message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:43:57Z" - latency: 823.784µs message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:42:57Z" - latency: 934.382µs message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:41:57Z" - latency: 932.127µs message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:40:57Z" - latency: 971.703µs message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:39:57Z" - latency: 832.085µs message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:38:57Z" - latency: 811.204µs message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:37:57Z" - latency: 900.4µs message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:36:57Z" - latency: 951.012µs message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:35:57Z" - latency: 895.779µs message: 'network-check-target-ip-10-0-129-115: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:34:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-115-to-network-check-target-ip-10-0-130-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-115.ec2.internal uid: 333aac46-7d31-4e7f-b2b0-a4cd0c344d96 resourceVersion: "63073" uid: 768b93ea-304d-4e65-bf9a-375b05da773f spec: sourcePod: network-check-source-869dcfcdcd-n2wvf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T18:08:57Z" message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.184712ms message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:43:57Z" - latency: 2.845027ms message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:42:57Z" - latency: 2.385143ms message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:41:57Z" - latency: 2.737491ms message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:40:57Z" - latency: 2.32654ms message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:39:57Z" - latency: 2.044338ms message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:38:57Z" - latency: 2.140492ms message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:37:57Z" - latency: 1.852725ms message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:36:57Z" - latency: 2.075884ms message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:35:57Z" - latency: 1.857053ms message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:34:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-115-to-network-check-target-ip-10-0-139-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-115.ec2.internal uid: 333aac46-7d31-4e7f-b2b0-a4cd0c344d96 resourceVersion: "63072" uid: 6e2fc7f7-6f46-45a5-90b3-3e7e5535e51c spec: sourcePod: network-check-source-869dcfcdcd-n2wvf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T18:08:57Z" message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.707667ms message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:43:57Z" - latency: 2.675919ms message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:42:57Z" - latency: 2.491822ms message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:41:57Z" - latency: 2.477012ms message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:40:57Z" - latency: 2.363133ms message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:39:57Z" - latency: 2.22116ms message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:38:57Z" - latency: 2.208054ms message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:37:57Z" - latency: 2.585302ms message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:36:57Z" - latency: 2.446657ms message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:35:57Z" - latency: 2.522214ms message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:34:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T18:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-115-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-115.ec2.internal uid: 333aac46-7d31-4e7f-b2b0-a4cd0c344d96 resourceVersion: "63074" uid: ce4c74bb-34bf-41b3-a88c-a5b55c734ef2 spec: sourcePod: network-check-source-869dcfcdcd-n2wvf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T18:07:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.303554ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:43:57Z" - latency: 1.647211ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:43:57Z" - latency: 1.083521ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:42:57Z" - latency: 1.734456ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:42:57Z" - latency: 774.181µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:41:57Z" - latency: 1.740134ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:41:57Z" - latency: 1.111588ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:40:57Z" - latency: 1.888085ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:40:57Z" - latency: 900.927µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T18:39:57Z" - latency: 1.848849ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T18:39:57Z" kind: List metadata: resourceVersion: ""