apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:58:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-58-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-58.ec2.internal
      uid: 61027d54-bd16-4d64-afca-06a22b6984f5
    resourceVersion: "21518"
    uid: 2cc64016-c131-4ab2-aa81-288d72145850
  spec:
    sourcePod: network-check-source-6f78d59f99-zstwr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:05:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.989µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:05:03Z"
    - latency: 833.395µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:04:03Z"
    - latency: 882.602µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:03:03Z"
    - latency: 842.402µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:02:03Z"
    - latency: 991.267µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:01:03Z"
    - latency: 800.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:00:03Z"
    - latency: 837.168µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:59:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:58:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-58-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-58.ec2.internal
      uid: 61027d54-bd16-4d64-afca-06a22b6984f5
    resourceVersion: "19453"
    uid: e80e8f47-0781-4326-b749-408311341b8c
  spec:
    sourcePod: network-check-source-6f78d59f99-zstwr
    targetEndpoint: a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:04:03Z"
      message: 'load-balancer-api-external: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.425952ms
      message: 'load-balancer-api-external: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:04:03Z"
    - latency: 6.443108ms
      message: 'load-balancer-api-external: resolved host name a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:04:03Z"
    - latency: 19.570912ms
      message: 'load-balancer-api-external: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:03:03Z"
    - latency: 6.302054ms
      message: 'load-balancer-api-external: resolved host name a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:03:03Z"
    - latency: 18.49144ms
      message: 'load-balancer-api-external: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:02:03Z"
    - latency: 6.666358ms
      message: 'load-balancer-api-external: resolved host name a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:02:03Z"
    - latency: 17.333808ms
      message: 'load-balancer-api-external: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:01:03Z"
    - latency: 9.741254ms
      message: 'load-balancer-api-external: resolved host name a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:01:03Z"
    - latency: 17.069825ms
      message: 'load-balancer-api-external: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:00:03Z"
    - latency: 5.984381ms
      message: 'load-balancer-api-external: resolved host name a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:00:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:58:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-58-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-58.ec2.internal
      uid: 61027d54-bd16-4d64-afca-06a22b6984f5
    resourceVersion: "19454"
    uid: 2ed0185a-45d9-4629-9e0b-a43ccb7840e4
  spec:
    sourcePod: network-check-source-6f78d59f99-zstwr
    targetEndpoint: a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:04:03Z"
      message: 'load-balancer-api-internal: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.720023ms
      message: 'load-balancer-api-internal: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:04:03Z"
    - latency: 6.418583ms
      message: 'load-balancer-api-internal: resolved host name a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:04:03Z"
    - latency: 17.946046ms
      message: 'load-balancer-api-internal: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:03:03Z"
    - latency: 6.314827ms
      message: 'load-balancer-api-internal: resolved host name a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:03:03Z"
    - latency: 18.457434ms
      message: 'load-balancer-api-internal: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:02:03Z"
    - latency: 6.650065ms
      message: 'load-balancer-api-internal: resolved host name a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:02:03Z"
    - latency: 17.208318ms
      message: 'load-balancer-api-internal: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:01:03Z"
    - latency: 9.771802ms
      message: 'load-balancer-api-internal: resolved host name a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:01:03Z"
    - latency: 18.731288ms
      message: 'load-balancer-api-internal: tcp connection to a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:00:03Z"
    - latency: 6.018162ms
      message: 'load-balancer-api-internal: resolved host name a4d0980005d6249c191812bbde85e644-5c8b8bdc9f04a0b4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:00:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:58:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-58-to-network-check-target-ip-10-0-130-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-58.ec2.internal
      uid: 61027d54-bd16-4d64-afca-06a22b6984f5
    resourceVersion: "21523"
    uid: df0b0575-7556-4662-97bd-2ffad8ba0b4b
  spec:
    sourcePod: network-check-source-6f78d59f99-zstwr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:05:03Z"
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.709098ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:05:03Z"
    - latency: 1.685665ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:04:03Z"
    - latency: 1.647042ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:03:03Z"
    - latency: 1.886033ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:02:03Z"
    - latency: 779.008µs
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:01:03Z"
    - latency: 1.807842ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:00:03Z"
    - latency: 2.158872ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:59:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:58:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-58-to-network-check-target-ip-10-0-140-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-58.ec2.internal
      uid: 61027d54-bd16-4d64-afca-06a22b6984f5
    resourceVersion: "21524"
    uid: 9d0cdfa3-d1ee-4feb-91c3-df45bbe1764b
  spec:
    sourcePod: network-check-source-6f78d59f99-zstwr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:05:03Z"
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.047203ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:05:03Z"
    - latency: 767.608µs
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:04:03Z"
    - latency: 672.264µs
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:03:03Z"
    - latency: 2.077876ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:02:03Z"
    - latency: 2.266579ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:01:03Z"
    - latency: 2.040708ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:00:03Z"
    - latency: 2.261364ms
      message: 'network-check-target-ip-10-0-140-44: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:59:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:58:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-58-to-network-check-target-ip-10-0-142-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-58.ec2.internal
      uid: 61027d54-bd16-4d64-afca-06a22b6984f5
    resourceVersion: "21522"
    uid: c577ff51-06c0-4483-bd6e-4630a01a0645
  spec:
    sourcePod: network-check-source-6f78d59f99-zstwr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:05:03Z"
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 553.29µs
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:05:03Z"
    - latency: 906.824µs
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:04:03Z"
    - latency: 1.048001ms
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:03:03Z"
    - latency: 741.782µs
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:02:03Z"
    - latency: 715.131µs
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:01:03Z"
    - latency: 601.444µs
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:00:03Z"
    - latency: 860.048µs
      message: 'network-check-target-ip-10-0-142-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:59:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:58:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-58-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-58.ec2.internal
      uid: 61027d54-bd16-4d64-afca-06a22b6984f5
    resourceVersion: "19455"
    uid: a23125b3-0adb-4411-8ded-5137750e26e7
  spec:
    sourcePod: network-check-source-6f78d59f99-zstwr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:04:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.230226ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:04:03Z"
    - latency: 629.003µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:04:03Z"
    - latency: 2.07232ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:03:03Z"
    - latency: 807.818µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:03:03Z"
    - latency: 1.019024ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:02:03Z"
    - latency: 553.789µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:02:03Z"
    - latency: 1.632012ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:01:03Z"
    - latency: 597.587µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:01:03Z"
    - latency: 1.118085ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:00:03Z"
    - latency: 463.573µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:00:03Z"
kind: List
metadata:
  resourceVersion: ""