apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-105.ec2.internal
      uid: 8a2dd7df-3e66-4952-86da-d68b14b01390
    resourceVersion: "25736"
    uid: 5d5c4941-2965-45f8-8d19-006ef63777aa
  spec:
    sourcePod: network-check-source-6947749cfc-h9d46
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T20:32:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.522µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:32:35Z"
    - latency: 1.046712ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:31:35Z"
    - latency: 1.344913ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:30:35Z"
    - latency: 1.124063ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:29:35Z"
    - latency: 784.68µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:28:35Z"
    - latency: 888.276µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:27:35Z"
    - latency: 863.258µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:26:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-105.ec2.internal
      uid: 8a2dd7df-3e66-4952-86da-d68b14b01390
    resourceVersion: "24497"
    uid: 8a75bed1-3b10-4aef-933b-5c2353241c18
  spec:
    sourcePod: network-check-source-6947749cfc-h9d46
    targetEndpoint: a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T20:31:35Z"
      message: 'load-balancer-api-external: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.511523ms
      message: 'load-balancer-api-external: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:31:35Z"
    - latency: 9.3001ms
      message: 'load-balancer-api-external: resolved host name a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:31:35Z"
    - latency: 4.862867ms
      message: 'load-balancer-api-external: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:30:35Z"
    - latency: 9.802117ms
      message: 'load-balancer-api-external: resolved host name a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:30:35Z"
    - latency: 5.854176ms
      message: 'load-balancer-api-external: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:29:35Z"
    - latency: 8.187906ms
      message: 'load-balancer-api-external: resolved host name a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:29:35Z"
    - latency: 5.229085ms
      message: 'load-balancer-api-external: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:28:35Z"
    - latency: 8.293431ms
      message: 'load-balancer-api-external: resolved host name a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:28:35Z"
    - latency: 4.711042ms
      message: 'load-balancer-api-external: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:27:35Z"
    - latency: 9.340768ms
      message: 'load-balancer-api-external: resolved host name a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:27:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-105.ec2.internal
      uid: 8a2dd7df-3e66-4952-86da-d68b14b01390
    resourceVersion: "24496"
    uid: e56138e5-4321-4281-a735-6bbc8bdf5c91
  spec:
    sourcePod: network-check-source-6947749cfc-h9d46
    targetEndpoint: a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T20:31:35Z"
      message: 'load-balancer-api-internal: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.397781ms
      message: 'load-balancer-api-internal: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:31:35Z"
    - latency: 9.352149ms
      message: 'load-balancer-api-internal: resolved host name a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:31:35Z"
    - latency: 4.693012ms
      message: 'load-balancer-api-internal: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:30:35Z"
    - latency: 9.699426ms
      message: 'load-balancer-api-internal: resolved host name a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:30:35Z"
    - latency: 5.011925ms
      message: 'load-balancer-api-internal: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:29:35Z"
    - latency: 8.152486ms
      message: 'load-balancer-api-internal: resolved host name a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:29:35Z"
    - latency: 5.21691ms
      message: 'load-balancer-api-internal: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:28:35Z"
    - latency: 8.234677ms
      message: 'load-balancer-api-internal: resolved host name a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:28:35Z"
    - latency: 3.819685ms
      message: 'load-balancer-api-internal: tcp connection to a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:27:35Z"
    - latency: 9.38063ms
      message: 'load-balancer-api-internal: resolved host name a7e34f1ad0140441d994f0a1cae89b8c-7185bcd94965986d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:27:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-105-to-network-check-target-ip-10-0-129-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-105.ec2.internal
      uid: 8a2dd7df-3e66-4952-86da-d68b14b01390
    resourceVersion: "25735"
    uid: 3ac2a1cb-3d53-4249-a7d3-a85bcb8b48ed
  spec:
    sourcePod: network-check-source-6947749cfc-h9d46
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T20:32:35Z"
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.393321ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:32:35Z"
    - latency: 1.887314ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:31:35Z"
    - latency: 1.950006ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:30:35Z"
    - latency: 2.288119ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:29:35Z"
    - latency: 1.682955ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:28:35Z"
    - latency: 2.611613ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:27:35Z"
    - latency: 2.11702ms
      message: 'network-check-target-ip-10-0-129-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:26:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-105-to-network-check-target-ip-10-0-132-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-105.ec2.internal
      uid: 8a2dd7df-3e66-4952-86da-d68b14b01390
    resourceVersion: "25734"
    uid: 0bb2e53a-e0ee-4a13-bcca-1e51075720a7
  spec:
    sourcePod: network-check-source-6947749cfc-h9d46
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T20:32:35Z"
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.89686ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:32:35Z"
    - latency: 1.632753ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:31:35Z"
    - latency: 2.489ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:30:35Z"
    - latency: 1.930732ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:29:35Z"
    - latency: 1.931053ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:28:35Z"
    - latency: 2.591793ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:27:35Z"
    - latency: 1.997206ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:26:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-105-to-network-check-target-ip-10-0-137-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-105.ec2.internal
      uid: 8a2dd7df-3e66-4952-86da-d68b14b01390
    resourceVersion: "25733"
    uid: 62c2956e-b01d-4ec0-ac70-8e3735a477d8
  spec:
    sourcePod: network-check-source-6947749cfc-h9d46
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T20:32:35Z"
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026267ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:32:35Z"
    - latency: 1.032618ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:31:35Z"
    - latency: 1.555335ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:30:35Z"
    - latency: 818.072µs
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:29:35Z"
    - latency: 962.985µs
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:28:35Z"
    - latency: 840.856µs
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:27:35Z"
    - latency: 1.019538ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:26:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T20:25:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-105.ec2.internal
      uid: 8a2dd7df-3e66-4952-86da-d68b14b01390
    resourceVersion: "24495"
    uid: 23517a11-b475-4290-9008-12f021f47049
  spec:
    sourcePod: network-check-source-6947749cfc-h9d46
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T20:31:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.107µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:31:35Z"
    - latency: 1.877826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:31:35Z"
    - latency: 1.102126ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:30:35Z"
    - latency: 2.320538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:30:35Z"
    - latency: 1.105353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:29:35Z"
    - latency: 1.703045ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:29:35Z"
    - latency: 884.309µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:28:35Z"
    - latency: 1.626077ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:28:35Z"
    - latency: 759.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T20:27:35Z"
    - latency: 2.528066ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T20:27:35Z"
kind: List
metadata:
  resourceVersion: ""