apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:05:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-111.ec2.internal
      uid: 0939adc7-6135-43af-9c12-fee40878c4ae
    resourceVersion: "15251"
    uid: 1948780e-2814-4615-9313-9a43f3295030
  spec:
    sourcePod: network-check-source-65bdbbff45-hjhgn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:12:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.088892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:12:32Z"
    - latency: 1.002306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:11:32Z"
    - latency: 1.989382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:10:32Z"
    - latency: 1.546113ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:09:32Z"
    - latency: 1.262143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:08:32Z"
    - latency: 1.088973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:07:32Z"
    - latency: 1.075728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:06:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:05:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-111.ec2.internal
      uid: 0939adc7-6135-43af-9c12-fee40878c4ae
    resourceVersion: "14751"
    uid: 25d67d8e-de0b-42b4-a4f4-f39306892dd4
  spec:
    sourcePod: network-check-source-65bdbbff45-hjhgn
    targetEndpoint: a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:11:32Z"
      message: 'load-balancer-api-external: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.079842ms
      message: 'load-balancer-api-external: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:11:32Z"
    - latency: 7.140201ms
      message: 'load-balancer-api-external: resolved host name a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:11:32Z"
    - latency: 5.637163ms
      message: 'load-balancer-api-external: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:10:32Z"
    - latency: 8.182752ms
      message: 'load-balancer-api-external: resolved host name a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:10:32Z"
    - latency: 5.034581ms
      message: 'load-balancer-api-external: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:09:32Z"
    - latency: 9.651509ms
      message: 'load-balancer-api-external: resolved host name a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:09:32Z"
    - latency: 4.920462ms
      message: 'load-balancer-api-external: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:08:32Z"
    - latency: 8.01729ms
      message: 'load-balancer-api-external: resolved host name a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:08:32Z"
    - latency: 5.854158ms
      message: 'load-balancer-api-external: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:07:32Z"
    - latency: 11.662656ms
      message: 'load-balancer-api-external: resolved host name a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:07:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:05:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-111.ec2.internal
      uid: 0939adc7-6135-43af-9c12-fee40878c4ae
    resourceVersion: "14752"
    uid: 1da5413a-c55d-4dc6-9812-038c333d4753
  spec:
    sourcePod: network-check-source-65bdbbff45-hjhgn
    targetEndpoint: a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:11:32Z"
      message: 'load-balancer-api-internal: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.568882ms
      message: 'load-balancer-api-internal: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:11:32Z"
    - latency: 7.012306ms
      message: 'load-balancer-api-internal: resolved host name a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:11:32Z"
    - latency: 5.585848ms
      message: 'load-balancer-api-internal: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:10:32Z"
    - latency: 8.23834ms
      message: 'load-balancer-api-internal: resolved host name a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:10:32Z"
    - latency: 5.071195ms
      message: 'load-balancer-api-internal: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:09:32Z"
    - latency: 9.591995ms
      message: 'load-balancer-api-internal: resolved host name a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:09:32Z"
    - latency: 4.906194ms
      message: 'load-balancer-api-internal: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:08:32Z"
    - latency: 8.085633ms
      message: 'load-balancer-api-internal: resolved host name a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:08:32Z"
    - latency: 5.887135ms
      message: 'load-balancer-api-internal: tcp connection to a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:07:32Z"
    - latency: 11.737469ms
      message: 'load-balancer-api-internal: resolved host name a02d221f3808b4e0ab786a7ed1e0f502-897ff7ba7e558a24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:07:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:05:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-111-to-network-check-target-ip-10-0-132-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-111.ec2.internal
      uid: 0939adc7-6135-43af-9c12-fee40878c4ae
    resourceVersion: "15248"
    uid: 4c024d54-e930-4464-abe2-829eec4f550a
  spec:
    sourcePod: network-check-source-65bdbbff45-hjhgn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:12:32Z"
      message: 'network-check-target-ip-10-0-132-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.007786ms
      message: 'network-check-target-ip-10-0-132-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:12:32Z"
    - latency: 1.034536ms
      message: 'network-check-target-ip-10-0-132-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:11:32Z"
    - latency: 1.107151ms
      message: 'network-check-target-ip-10-0-132-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:10:32Z"
    - latency: 2.071065ms
      message: 'network-check-target-ip-10-0-132-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:09:32Z"
    - latency: 1.224238ms
      message: 'network-check-target-ip-10-0-132-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:08:32Z"
    - latency: 957.883µs
      message: 'network-check-target-ip-10-0-132-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:07:32Z"
    - latency: 1.559429ms
      message: 'network-check-target-ip-10-0-132-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:06:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:05:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-111-to-network-check-target-ip-10-0-136-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-111.ec2.internal
      uid: 0939adc7-6135-43af-9c12-fee40878c4ae
    resourceVersion: "15250"
    uid: 5b1cdd6e-8af5-49c2-9977-73b846575936
  spec:
    sourcePod: network-check-source-65bdbbff45-hjhgn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:12:32Z"
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.518184ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:12:32Z"
    - latency: 2.515883ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:11:32Z"
    - latency: 3.130206ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:10:32Z"
    - latency: 2.688992ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:09:32Z"
    - latency: 2.508008ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:08:32Z"
    - latency: 2.458921ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:07:32Z"
    - latency: 2.129186ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:06:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:05:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-111-to-network-check-target-ip-10-0-140-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-111.ec2.internal
      uid: 0939adc7-6135-43af-9c12-fee40878c4ae
    resourceVersion: "15249"
    uid: 61592f87-b07a-4786-b9c2-8d2fb2f0d022
  spec:
    sourcePod: network-check-source-65bdbbff45-hjhgn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:12:32Z"
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.528593ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:12:32Z"
    - latency: 2.38098ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:11:32Z"
    - latency: 2.51996ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:10:32Z"
    - latency: 2.449544ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:09:32Z"
    - latency: 2.516496ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:08:32Z"
    - latency: 2.442146ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:07:32Z"
    - latency: 2.443004ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:06:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T09:05:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-111.ec2.internal
      uid: 0939adc7-6135-43af-9c12-fee40878c4ae
    resourceVersion: "14748"
    uid: 064b35f3-52eb-4733-bd2b-0940596ded7e
  spec:
    sourcePod: network-check-source-65bdbbff45-hjhgn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T09:11:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.226µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:11:32Z"
    - latency: 1.805997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:11:32Z"
    - latency: 1.04335ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:10:32Z"
    - latency: 2.624798ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:10:32Z"
    - latency: 1.790068ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:09:32Z"
    - latency: 2.024028ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:09:32Z"
    - latency: 1.335584ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:08:32Z"
    - latency: 2.169428ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:08:32Z"
    - latency: 899.504µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T09:07:32Z"
    - latency: 1.861026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T09:07:32Z"
kind: List
metadata:
  resourceVersion: ""