apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:39:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: 850b2ba7-6a8e-45a8-ae17-128d8153e177
    resourceVersion: "15129"
    uid: 2deeca2d-dee4-4172-bc18-475c07e88a36
  spec:
    sourcePod: network-check-source-6f8b768455-fjjgw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:46:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.456069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:46:33Z"
    - latency: 875.474µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:45:33Z"
    - latency: 1.101942ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:44:33Z"
    - latency: 1.197069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:43:33Z"
    - latency: 1.091621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:42:33Z"
    - latency: 1.003616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:41:33Z"
    - latency: 1.214905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:40:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:39:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: 850b2ba7-6a8e-45a8-ae17-128d8153e177
    resourceVersion: "14670"
    uid: 41764e7d-6b61-4f4f-aab4-2afa157aed91
  spec:
    sourcePod: network-check-source-6f8b768455-fjjgw
    targetEndpoint: a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:45:33Z"
      message: 'load-balancer-api-external: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.703405ms
      message: 'load-balancer-api-external: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:45:33Z"
    - latency: 7.536276ms
      message: 'load-balancer-api-external: resolved host name a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:45:33Z"
    - latency: 5.210831ms
      message: 'load-balancer-api-external: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:44:33Z"
    - latency: 8.8273ms
      message: 'load-balancer-api-external: resolved host name a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:44:33Z"
    - latency: 4.097703ms
      message: 'load-balancer-api-external: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:43:33Z"
    - latency: 9.087341ms
      message: 'load-balancer-api-external: resolved host name a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:43:33Z"
    - latency: 4.079161ms
      message: 'load-balancer-api-external: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:42:33Z"
    - latency: 10.826294ms
      message: 'load-balancer-api-external: resolved host name a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:42:33Z"
    - latency: 5.302343ms
      message: 'load-balancer-api-external: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:41:33Z"
    - latency: 7.930375ms
      message: 'load-balancer-api-external: resolved host name a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:41:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:39:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: 850b2ba7-6a8e-45a8-ae17-128d8153e177
    resourceVersion: "14671"
    uid: 054a3aa7-a626-4b56-a67a-fe9450aaa443
  spec:
    sourcePod: network-check-source-6f8b768455-fjjgw
    targetEndpoint: a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:45:33Z"
      message: 'load-balancer-api-internal: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.710053ms
      message: 'load-balancer-api-internal: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:45:33Z"
    - latency: 7.471064ms
      message: 'load-balancer-api-internal: resolved host name a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:45:33Z"
    - latency: 5.321395ms
      message: 'load-balancer-api-internal: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:44:33Z"
    - latency: 8.744757ms
      message: 'load-balancer-api-internal: resolved host name a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:44:33Z"
    - latency: 4.114263ms
      message: 'load-balancer-api-internal: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:43:33Z"
    - latency: 9.014654ms
      message: 'load-balancer-api-internal: resolved host name a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:43:33Z"
    - latency: 3.929129ms
      message: 'load-balancer-api-internal: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:42:33Z"
    - latency: 10.899917ms
      message: 'load-balancer-api-internal: resolved host name a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:42:33Z"
    - latency: 4.923846ms
      message: 'load-balancer-api-internal: tcp connection to a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:41:33Z"
    - latency: 7.964398ms
      message: 'load-balancer-api-internal: resolved host name a3e6cf03d5c6a4da384dc04cb17c2621-89d9668545b169f0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:41:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:39:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-network-check-target-ip-10-0-134-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: 850b2ba7-6a8e-45a8-ae17-128d8153e177
    resourceVersion: "15128"
    uid: 00b10afa-398d-43f6-b097-61da06371e2c
  spec:
    sourcePod: network-check-source-6f8b768455-fjjgw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:46:33Z"
      message: 'network-check-target-ip-10-0-134-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.344558ms
      message: 'network-check-target-ip-10-0-134-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:46:33Z"
    - latency: 2.025339ms
      message: 'network-check-target-ip-10-0-134-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:45:33Z"
    - latency: 2.207845ms
      message: 'network-check-target-ip-10-0-134-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:44:33Z"
    - latency: 2.071352ms
      message: 'network-check-target-ip-10-0-134-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:43:33Z"
    - latency: 2.152025ms
      message: 'network-check-target-ip-10-0-134-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:42:33Z"
    - latency: 2.107321ms
      message: 'network-check-target-ip-10-0-134-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:41:33Z"
    - latency: 2.460228ms
      message: 'network-check-target-ip-10-0-134-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:40:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:39:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-network-check-target-ip-10-0-137-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: 850b2ba7-6a8e-45a8-ae17-128d8153e177
    resourceVersion: "15127"
    uid: 75302ba3-bb77-49b4-b4c3-6107b5928264
  spec:
    sourcePod: network-check-source-6f8b768455-fjjgw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:46:33Z"
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.905729ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:46:33Z"
    - latency: 1.67519ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:45:33Z"
    - latency: 2.051985ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:44:33Z"
    - latency: 1.87418ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:43:33Z"
    - latency: 1.767997ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:42:33Z"
    - latency: 1.897708ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:41:33Z"
    - latency: 1.826548ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:40:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:39:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-network-check-target-ip-10-0-139-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: 850b2ba7-6a8e-45a8-ae17-128d8153e177
    resourceVersion: "15126"
    uid: 9adeb473-0d96-4174-aa15-70253776c242
  spec:
    sourcePod: network-check-source-6f8b768455-fjjgw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:46:33Z"
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.010347ms
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:46:33Z"
    - latency: 898.199µs
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:45:33Z"
    - latency: 1.534334ms
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:44:33Z"
    - latency: 1.290602ms
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:43:33Z"
    - latency: 787.124µs
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:42:33Z"
    - latency: 958.206µs
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:41:33Z"
    - latency: 1.836142ms
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:40:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:39:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: 850b2ba7-6a8e-45a8-ae17-128d8153e177
    resourceVersion: "14669"
    uid: bd3193bf-31cf-4033-a316-7e19c1684489
  spec:
    sourcePod: network-check-source-6f8b768455-fjjgw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:45:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 860.799µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:45:33Z"
    - latency: 1.658459ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:45:33Z"
    - latency: 977.12µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:44:33Z"
    - latency: 1.645715ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:44:33Z"
    - latency: 1.065005ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:43:33Z"
    - latency: 1.837839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:43:33Z"
    - latency: 790.281µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:42:33Z"
    - latency: 2.147063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:42:33Z"
    - latency: 767.429µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:41:33Z"
    - latency: 1.684652ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:41:33Z"
kind: List
metadata:
  resourceVersion: ""