apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:31:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: dc2c4ad4-dc60-4994-b2c3-241aac43bcba
    resourceVersion: "15615"
    uid: 4d4e8035-281e-4450-b4dc-c84997828202
  spec:
    sourcePod: network-check-source-dbd9cf844-lbb2c
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:38:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.037751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:47Z"
    - latency: 847.951µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:47Z"
    - latency: 1.131703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:47Z"
    - latency: 881.198µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:47Z"
    - latency: 981.938µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:47Z"
    - latency: 916.143µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:33:47Z"
    - latency: 882.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:31:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: dc2c4ad4-dc60-4994-b2c3-241aac43bcba
    resourceVersion: "15283"
    uid: a833ad3e-641a-4cc7-9033-2f0b7ca4c7fe
  spec:
    sourcePod: network-check-source-dbd9cf844-lbb2c
    targetEndpoint: aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:37:47Z"
      message: 'load-balancer-api-external: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.843701ms
      message: 'load-balancer-api-external: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:47Z"
    - latency: 8.095682ms
      message: 'load-balancer-api-external: resolved host name aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:37:47Z"
    - latency: 4.380747ms
      message: 'load-balancer-api-external: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:47Z"
    - latency: 8.679404ms
      message: 'load-balancer-api-external: resolved host name aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:36:47Z"
    - latency: 5.191762ms
      message: 'load-balancer-api-external: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:47Z"
    - latency: 8.379592ms
      message: 'load-balancer-api-external: resolved host name aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:35:47Z"
    - latency: 3.355938ms
      message: 'load-balancer-api-external: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:47Z"
    - latency: 8.131183ms
      message: 'load-balancer-api-external: resolved host name aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:34:47Z"
    - latency: 5.357893ms
      message: 'load-balancer-api-external: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:33:47Z"
    - latency: 7.209751ms
      message: 'load-balancer-api-external: resolved host name aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:33:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:31:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: dc2c4ad4-dc60-4994-b2c3-241aac43bcba
    resourceVersion: "15284"
    uid: bc2bf86d-d71f-47ee-bedb-3b5fc565525d
  spec:
    sourcePod: network-check-source-dbd9cf844-lbb2c
    targetEndpoint: aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:37:47Z"
      message: 'load-balancer-api-internal: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.169941ms
      message: 'load-balancer-api-internal: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:47Z"
    - latency: 8.138881ms
      message: 'load-balancer-api-internal: resolved host name aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:37:47Z"
    - latency: 4.340987ms
      message: 'load-balancer-api-internal: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:47Z"
    - latency: 8.755545ms
      message: 'load-balancer-api-internal: resolved host name aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:36:47Z"
    - latency: 5.172764ms
      message: 'load-balancer-api-internal: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:47Z"
    - latency: 8.434146ms
      message: 'load-balancer-api-internal: resolved host name aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:35:47Z"
    - latency: 5.907349ms
      message: 'load-balancer-api-internal: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:47Z"
    - latency: 8.173278ms
      message: 'load-balancer-api-internal: resolved host name aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:34:47Z"
    - latency: 5.795344ms
      message: 'load-balancer-api-internal: tcp connection to aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:33:47Z"
    - latency: 7.298668ms
      message: 'load-balancer-api-internal: resolved host name aa085bec8ef0e4e059331cf128f1efc4-15df5a87cfd55c86.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:33:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:31:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-135-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: dc2c4ad4-dc60-4994-b2c3-241aac43bcba
    resourceVersion: "15613"
    uid: 168f8ac6-d3e3-44e1-a959-57aea16b3f1e
  spec:
    sourcePod: network-check-source-dbd9cf844-lbb2c
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:38:47Z"
      message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.509432ms
      message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:47Z"
    - latency: 2.271267ms
      message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:47Z"
    - latency: 2.016268ms
      message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:47Z"
    - latency: 2.505381ms
      message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:47Z"
    - latency: 2.257072ms
      message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:47Z"
    - latency: 1.971993ms
      message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:33:47Z"
    - latency: 2.45882ms
      message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:31:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-138-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: dc2c4ad4-dc60-4994-b2c3-241aac43bcba
    resourceVersion: "15612"
    uid: df5900f1-e577-431e-80a6-99faf15adf12
  spec:
    sourcePod: network-check-source-dbd9cf844-lbb2c
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:38:47Z"
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 829.622µs
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:47Z"
    - latency: 941.276µs
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:47Z"
    - latency: 1.286549ms
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:47Z"
    - latency: 897.394µs
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:47Z"
    - latency: 1.273802ms
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:47Z"
    - latency: 845.723µs
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:33:47Z"
    - latency: 1.257196ms
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:31:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-141-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: dc2c4ad4-dc60-4994-b2c3-241aac43bcba
    resourceVersion: "15614"
    uid: 12ae4660-94f3-44a0-9f11-6f1722219a65
  spec:
    sourcePod: network-check-source-dbd9cf844-lbb2c
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:38:47Z"
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.527861ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:47Z"
    - latency: 1.958619ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:47Z"
    - latency: 2.14895ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:47Z"
    - latency: 2.198456ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:47Z"
    - latency: 2.18091ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:47Z"
    - latency: 2.024196ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:33:47Z"
    - latency: 2.310696ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:31:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: dc2c4ad4-dc60-4994-b2c3-241aac43bcba
    resourceVersion: "15282"
    uid: d4ed51b4-f011-4fa6-b8ef-63710c54ccc4
  spec:
    sourcePod: network-check-source-dbd9cf844-lbb2c
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:37:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 789.704µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:47Z"
    - latency: 1.624226ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:37:47Z"
    - latency: 737.081µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:47Z"
    - latency: 2.100362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:36:47Z"
    - latency: 1.082604ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:47Z"
    - latency: 1.755304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:35:47Z"
    - latency: 838.815µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:47Z"
    - latency: 1.983048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:34:47Z"
    - latency: 1.203004ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:33:47Z"
    - latency: 1.567019ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:33:47Z"
kind: List
metadata:
  resourceVersion: ""