apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 820a30dd-543e-42a6-95fc-cf0b91818036
    resourceVersion: "11209"
    uid: 3b884ae8-8a7f-4cd8-a9f0-8b597500895e
  spec:
    sourcePod: network-check-source-989f8b8dc-tjt9h
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 820a30dd-543e-42a6-95fc-cf0b91818036
    resourceVersion: "22518"
    uid: 7c70e8e5-4c5e-4bb6-a166-fd9651e3075e
  spec:
    sourcePod: network-check-source-989f8b8dc-tjt9h
    targetEndpoint: ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:08:32Z"
      message: 'load-balancer-api-external: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.497549ms
      message: 'load-balancer-api-external: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:08:32Z"
    - latency: 8.264641ms
      message: 'load-balancer-api-external: resolved host name ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:08:32Z"
    - latency: 5.119426ms
      message: 'load-balancer-api-external: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:07:32Z"
    - latency: 8.818358ms
      message: 'load-balancer-api-external: resolved host name ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:07:32Z"
    - latency: 5.701569ms
      message: 'load-balancer-api-external: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:06:32Z"
    - latency: 11.166245ms
      message: 'load-balancer-api-external: resolved host name ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:06:32Z"
    - latency: 3.62359ms
      message: 'load-balancer-api-external: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:05:32Z"
    - latency: 8.278083ms
      message: 'load-balancer-api-external: resolved host name ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:05:32Z"
    - latency: 5.054352ms
      message: 'load-balancer-api-external: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:04:32Z"
    - latency: 10.492121ms
      message: 'load-balancer-api-external: resolved host name ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:04:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 820a30dd-543e-42a6-95fc-cf0b91818036
    resourceVersion: "22517"
    uid: f31cd82c-5a85-4da7-940c-bede0ab7bdc2
  spec:
    sourcePod: network-check-source-989f8b8dc-tjt9h
    targetEndpoint: ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:08:32Z"
      message: 'load-balancer-api-internal: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.498821ms
      message: 'load-balancer-api-internal: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:08:32Z"
    - latency: 8.138636ms
      message: 'load-balancer-api-internal: resolved host name ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:08:32Z"
    - latency: 5.096012ms
      message: 'load-balancer-api-internal: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:07:32Z"
    - latency: 8.755373ms
      message: 'load-balancer-api-internal: resolved host name ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:07:32Z"
    - latency: 5.708355ms
      message: 'load-balancer-api-internal: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:06:32Z"
    - latency: 11.136315ms
      message: 'load-balancer-api-internal: resolved host name ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:06:32Z"
    - latency: 3.637705ms
      message: 'load-balancer-api-internal: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:05:32Z"
    - latency: 8.258198ms
      message: 'load-balancer-api-internal: resolved host name ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:05:32Z"
    - latency: 4.494573ms
      message: 'load-balancer-api-internal: tcp connection to ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:04:32Z"
    - latency: 10.481046ms
      message: 'load-balancer-api-internal: resolved host name ae76e1c29efdb47e9b1f4a14708112b9-205aeee95da6eb33.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:04:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-network-check-target-ip-10-0-130-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 820a30dd-543e-42a6-95fc-cf0b91818036
    resourceVersion: "11207"
    uid: 220bfb1c-3c21-4750-ba4b-b72f9097a568
  spec:
    sourcePod: network-check-source-989f8b8dc-tjt9h
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-network-check-target-ip-10-0-137-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 820a30dd-543e-42a6-95fc-cf0b91818036
    resourceVersion: "11206"
    uid: bd04e537-d4ff-47ce-8d87-d7f72e041578
  spec:
    sourcePod: network-check-source-989f8b8dc-tjt9h
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:02:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-network-check-target-ip-10-0-142-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 820a30dd-543e-42a6-95fc-cf0b91818036
    resourceVersion: "11216"
    uid: 7c415152-a758-420a-be56-59593a0a29c1
  spec:
    sourcePod: network-check-source-989f8b8dc-tjt9h
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 820a30dd-543e-42a6-95fc-cf0b91818036
    resourceVersion: "22516"
    uid: c1e9856f-2a87-4a26-afd6-459f776b93aa
  spec:
    sourcePod: network-check-source-989f8b8dc-tjt9h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:08:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.655µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:08:32Z"
    - latency: 1.588137ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:08:32Z"
    - latency: 802.553µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:07:32Z"
    - latency: 2.008821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:07:32Z"
    - latency: 897.624µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:06:32Z"
    - latency: 2.028053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:06:32Z"
    - latency: 979.612µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:05:32Z"
    - latency: 1.725926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:05:32Z"
    - latency: 742.089µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:04:32Z"
    - latency: 1.775226ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:04:32Z"
kind: List
metadata:
  resourceVersion: ""