apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-44-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-44.ec2.internal
      uid: 9e022caa-68df-4210-b839-1e322cc1873c
    resourceVersion: "24606"
    uid: 4e16e360-c61f-4336-8552-f83f048e67a0
  spec:
    sourcePod: network-check-source-6f8b768455-b86zv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:27:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.119173ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:27:38Z"
    - latency: 1.343144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:26:38Z"
    - latency: 1.142785ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:25:38Z"
    - latency: 1.568321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:24:38Z"
    - latency: 1.16754ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:23:38Z"
    - latency: 1.049513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:22:38Z"
    - latency: 1.153827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:21:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-44-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-44.ec2.internal
      uid: 9e022caa-68df-4210-b839-1e322cc1873c
    resourceVersion: "23404"
    uid: 67c32493-ae7b-4c45-ae3d-6093959cebf4
  spec:
    sourcePod: network-check-source-6f8b768455-b86zv
    targetEndpoint: a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:26:38Z"
      message: 'load-balancer-api-external: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.424714ms
      message: 'load-balancer-api-external: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:26:38Z"
    - latency: 11.768445ms
      message: 'load-balancer-api-external: resolved host name a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:26:38Z"
    - latency: 5.549535ms
      message: 'load-balancer-api-external: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:25:38Z"
    - latency: 12.558824ms
      message: 'load-balancer-api-external: resolved host name a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:25:38Z"
    - latency: 5.833775ms
      message: 'load-balancer-api-external: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:24:38Z"
    - latency: 11.439367ms
      message: 'load-balancer-api-external: resolved host name a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:24:38Z"
    - latency: 3.905263ms
      message: 'load-balancer-api-external: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:23:38Z"
    - latency: 8.08895ms
      message: 'load-balancer-api-external: resolved host name a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:23:38Z"
    - latency: 5.801426ms
      message: 'load-balancer-api-external: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:22:38Z"
    - latency: 8.329026ms
      message: 'load-balancer-api-external: resolved host name a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:22:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-44-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-44.ec2.internal
      uid: 9e022caa-68df-4210-b839-1e322cc1873c
    resourceVersion: "23403"
    uid: 08a6f8db-ae60-45df-9167-48598342c5ed
  spec:
    sourcePod: network-check-source-6f8b768455-b86zv
    targetEndpoint: a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:26:38Z"
      message: 'load-balancer-api-internal: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.83626ms
      message: 'load-balancer-api-internal: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:26:38Z"
    - latency: 11.819026ms
      message: 'load-balancer-api-internal: resolved host name a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:26:38Z"
    - latency: 5.581513ms
      message: 'load-balancer-api-internal: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:25:38Z"
    - latency: 12.559878ms
      message: 'load-balancer-api-internal: resolved host name a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:25:38Z"
    - latency: 5.816807ms
      message: 'load-balancer-api-internal: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:24:38Z"
    - latency: 11.476731ms
      message: 'load-balancer-api-internal: resolved host name a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:24:38Z"
    - latency: 5.230869ms
      message: 'load-balancer-api-internal: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:23:38Z"
    - latency: 8.126917ms
      message: 'load-balancer-api-internal: resolved host name a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:23:38Z"
    - latency: 5.929135ms
      message: 'load-balancer-api-internal: tcp connection to a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:22:38Z"
    - latency: 8.373809ms
      message: 'load-balancer-api-internal: resolved host name a37307eb29a4c48d49952617a658c02d-a7259a00a787efd6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:22:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-44-to-network-check-target-ip-10-0-131-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-44.ec2.internal
      uid: 9e022caa-68df-4210-b839-1e322cc1873c
    resourceVersion: "24604"
    uid: 8169d586-5ce5-4090-90a1-7548f22ee609
  spec:
    sourcePod: network-check-source-6f8b768455-b86zv
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:27:38Z"
      message: 'network-check-target-ip-10-0-131-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.253438ms
      message: 'network-check-target-ip-10-0-131-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:27:38Z"
    - latency: 2.046088ms
      message: 'network-check-target-ip-10-0-131-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:26:38Z"
    - latency: 2.022318ms
      message: 'network-check-target-ip-10-0-131-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:25:38Z"
    - latency: 2.07953ms
      message: 'network-check-target-ip-10-0-131-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:24:38Z"
    - latency: 2.155569ms
      message: 'network-check-target-ip-10-0-131-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:23:38Z"
    - latency: 1.89529ms
      message: 'network-check-target-ip-10-0-131-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:22:38Z"
    - latency: 2.279012ms
      message: 'network-check-target-ip-10-0-131-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:21:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-44-to-network-check-target-ip-10-0-141-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-44.ec2.internal
      uid: 9e022caa-68df-4210-b839-1e322cc1873c
    resourceVersion: "24605"
    uid: 7c3f6b9d-3720-4b21-ae04-d07825f4a14c
  spec:
    sourcePod: network-check-source-6f8b768455-b86zv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:27:38Z"
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.362551ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:27:38Z"
    - latency: 2.66035ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:26:38Z"
    - latency: 2.061368ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:25:38Z"
    - latency: 2.014478ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:24:38Z"
    - latency: 2.071157ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:23:38Z"
    - latency: 2.08469ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:22:38Z"
    - latency: 2.130481ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:21:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-44-to-network-check-target-ip-10-0-141-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-44.ec2.internal
      uid: 9e022caa-68df-4210-b839-1e322cc1873c
    resourceVersion: "24603"
    uid: f103b444-ada8-49b1-8eaf-3d5424b04ae7
  spec:
    sourcePod: network-check-source-6f8b768455-b86zv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:27:38Z"
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.512507ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:27:38Z"
    - latency: 1.075004ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:26:38Z"
    - latency: 809.503µs
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:25:38Z"
    - latency: 1.114413ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:24:38Z"
    - latency: 883.68µs
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:23:38Z"
    - latency: 1.4857ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:22:38Z"
    - latency: 1.240789ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:21:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-44-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-44.ec2.internal
      uid: 9e022caa-68df-4210-b839-1e322cc1873c
    resourceVersion: "23401"
    uid: 0a72350d-06d2-421c-98b0-1acf21ef2729
  spec:
    sourcePod: network-check-source-6f8b768455-b86zv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:26:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.071ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:26:38Z"
    - latency: 2.410133ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:26:38Z"
    - latency: 999.651µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:25:38Z"
    - latency: 1.656981ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:25:38Z"
    - latency: 941.008µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:24:38Z"
    - latency: 1.946037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:24:38Z"
    - latency: 963.79µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:23:38Z"
    - latency: 2.044111ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:23:38Z"
    - latency: 1.103066ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:22:38Z"
    - latency: 1.704967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:22:38Z"
kind: List
metadata:
  resourceVersion: ""