apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T07:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-78-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-78.ec2.internal uid: 7047371a-6c74-4092-a6c5-fe76665993d8 resourceVersion: "19460" uid: 52de5922-5b3a-417c-bffb-fee318655e77 spec: sourcePod: network-check-source-7f44b6dd87-bq4sw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T07:08:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.971µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:22:47Z" - latency: 1.012206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:21:47Z" - latency: 1.009376ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:20:47Z" - latency: 1.221028ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:19:47Z" - latency: 1.48866ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:18:47Z" - latency: 1.059469ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:17:47Z" - latency: 885.804µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:16:47Z" - latency: 1.018035ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:15:47Z" - latency: 1.183737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:14:47Z" - latency: 1.141054ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:13:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T07:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-78-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-78.ec2.internal uid: 7047371a-6c74-4092-a6c5-fe76665993d8 resourceVersion: "20627" uid: ef5eadf3-bf4f-4be7-86b7-1944d90da139 spec: sourcePod: network-check-source-7f44b6dd87-bq4sw targetEndpoint: a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T07:07:47Z" message: 'load-balancer-api-external: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.135449ms message: 'load-balancer-api-external: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:25:47Z" - latency: 6.355322ms message: 'load-balancer-api-external: resolved host name a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T07:25:47Z" - latency: 4.618725ms message: 'load-balancer-api-external: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:24:47Z" - latency: 7.363068ms message: 'load-balancer-api-external: resolved host name a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T07:24:47Z" - latency: 5.084044ms message: 'load-balancer-api-external: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:23:47Z" - latency: 6.324621ms message: 'load-balancer-api-external: resolved host name a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T07:23:47Z" - latency: 5.141592ms message: 'load-balancer-api-external: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:22:47Z" - latency: 7.082415ms message: 'load-balancer-api-external: resolved host name a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T07:22:47Z" - latency: 5.043602ms message: 'load-balancer-api-external: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:21:47Z" - latency: 6.542825ms message: 'load-balancer-api-external: resolved host name a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T07:21:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T07:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-78-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-78.ec2.internal uid: 7047371a-6c74-4092-a6c5-fe76665993d8 resourceVersion: "20626" uid: f12312c3-f7a4-4f38-bf32-664407639a30 spec: sourcePod: network-check-source-7f44b6dd87-bq4sw targetEndpoint: a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T07:07:47Z" message: 'load-balancer-api-internal: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.176749ms message: 'load-balancer-api-internal: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:25:47Z" - latency: 6.425128ms message: 'load-balancer-api-internal: resolved host name a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T07:25:47Z" - latency: 4.566424ms message: 'load-balancer-api-internal: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:24:47Z" - latency: 7.323739ms message: 'load-balancer-api-internal: resolved host name a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T07:24:47Z" - latency: 5.046086ms message: 'load-balancer-api-internal: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:23:47Z" - latency: 6.424237ms message: 'load-balancer-api-internal: resolved host name a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T07:23:47Z" - latency: 5.14287ms message: 'load-balancer-api-internal: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:22:47Z" - latency: 7.126647ms message: 'load-balancer-api-internal: resolved host name a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T07:22:47Z" - latency: 5.059346ms message: 'load-balancer-api-internal: tcp connection to a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:21:47Z" - latency: 6.608576ms message: 'load-balancer-api-internal: resolved host name a0a7f288488ff43e2899ee1478c7f942-2829d873109eb928.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T07:21:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T07:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-78-to-network-check-target-ip-10-0-133-78 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-78.ec2.internal uid: 7047371a-6c74-4092-a6c5-fe76665993d8 resourceVersion: "19457" uid: f49461d0-a484-4b57-8e9e-2be30ac18edc spec: sourcePod: network-check-source-7f44b6dd87-bq4sw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T07:08:47Z" message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 909.63µs message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:22:47Z" - latency: 845.945µs message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:21:47Z" - latency: 855.362µs message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:20:47Z" - latency: 797.814µs message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:19:47Z" - latency: 790.701µs message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:18:47Z" - latency: 1.586325ms message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:17:47Z" - latency: 1.572759ms message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:16:47Z" - latency: 1.537491ms message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:15:47Z" - latency: 1.161474ms message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:14:47Z" - latency: 1.377393ms message: 'network-check-target-ip-10-0-133-78: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:13:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T07:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-78-to-network-check-target-ip-10-0-134-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-78.ec2.internal uid: 7047371a-6c74-4092-a6c5-fe76665993d8 resourceVersion: "19458" uid: 71d0df63-2158-4150-b5f6-136fc032475b spec: sourcePod: network-check-source-7f44b6dd87-bq4sw targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T07:08:47Z" message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.11018ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:22:47Z" - latency: 2.142958ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:21:47Z" - latency: 2.215264ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:20:47Z" - latency: 2.209146ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:19:47Z" - latency: 2.820286ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:18:47Z" - latency: 2.380417ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:17:47Z" - latency: 2.049904ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:16:47Z" - latency: 2.004921ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:15:47Z" - latency: 2.421276ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:14:47Z" - latency: 2.117227ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:13:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T07:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-78-to-network-check-target-ip-10-0-137-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-78.ec2.internal uid: 7047371a-6c74-4092-a6c5-fe76665993d8 resourceVersion: "19459" uid: 0602b99f-43e0-4a3d-bcaf-7220d18eec3d spec: sourcePod: network-check-source-7f44b6dd87-bq4sw targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T07:08:47Z" message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.123017ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:22:47Z" - latency: 1.995086ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:21:47Z" - latency: 2.012449ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:20:47Z" - latency: 1.9145ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:19:47Z" - latency: 1.811766ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:18:47Z" - latency: 1.887318ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:17:47Z" - latency: 1.894977ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:16:47Z" - latency: 1.846427ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:15:47Z" - latency: 1.962298ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:14:47Z" - latency: 1.866451ms message: 'network-check-target-ip-10-0-137-85: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:13:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T07:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-78-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-78.ec2.internal uid: 7047371a-6c74-4092-a6c5-fe76665993d8 resourceVersion: "20625" uid: c3eebd53-9dc3-498f-944b-57e27c5dc289 spec: sourcePod: network-check-source-7f44b6dd87-bq4sw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T07:07:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 817.27µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:25:47Z" - latency: 1.895416ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T07:25:47Z" - latency: 894.822µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:24:47Z" - latency: 1.664221ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T07:24:47Z" - latency: 897.578µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:23:47Z" - latency: 2.194476ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T07:23:47Z" - latency: 934.334µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:22:47Z" - latency: 1.717181ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T07:22:47Z" - latency: 775.169µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T07:21:47Z" - latency: 1.906735ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T07:21:47Z" kind: List metadata: resourceVersion: ""