apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:12:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-239-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-239.ec2.internal
      uid: f57b3fb9-33a8-4088-8f09-ee3b125bc16e
    resourceVersion: "10966"
    uid: 57f6b11e-31fd-49ad-bc38-2b4ac474369e
  spec:
    sourcePod: network-check-source-685456655f-7bg7x
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:12:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-239-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-239.ec2.internal
      uid: f57b3fb9-33a8-4088-8f09-ee3b125bc16e
    resourceVersion: "14286"
    uid: 779def6a-3e44-49a1-a9d1-e258433d8917
  spec:
    sourcePod: network-check-source-685456655f-7bg7x
    targetEndpoint: af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T03:18:36Z"
      message: 'load-balancer-api-external: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.610068ms
      message: 'load-balancer-api-external: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:18:36Z"
    - latency: 7.536172ms
      message: 'load-balancer-api-external: resolved host name af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:18:36Z"
    - latency: 5.937618ms
      message: 'load-balancer-api-external: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:17:36Z"
    - latency: 8.689618ms
      message: 'load-balancer-api-external: resolved host name af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:17:36Z"
    - latency: 5.265229ms
      message: 'load-balancer-api-external: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:16:36Z"
    - latency: 8.827851ms
      message: 'load-balancer-api-external: resolved host name af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:16:36Z"
    - latency: 3.58515ms
      message: 'load-balancer-api-external: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:15:36Z"
    - latency: 8.884982ms
      message: 'load-balancer-api-external: resolved host name af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:15:36Z"
    - latency: 4.768148ms
      message: 'load-balancer-api-external: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:14:36Z"
    - latency: 12.862479ms
      message: 'load-balancer-api-external: resolved host name af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:14:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:12:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-239-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-239.ec2.internal
      uid: f57b3fb9-33a8-4088-8f09-ee3b125bc16e
    resourceVersion: "14285"
    uid: a04d27e8-48aa-4070-9af9-1bd7b24c5efa
  spec:
    sourcePod: network-check-source-685456655f-7bg7x
    targetEndpoint: af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T03:18:36Z"
      message: 'load-balancer-api-internal: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.291525ms
      message: 'load-balancer-api-internal: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:18:36Z"
    - latency: 7.660839ms
      message: 'load-balancer-api-internal: resolved host name af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:18:36Z"
    - latency: 5.579ms
      message: 'load-balancer-api-internal: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:17:36Z"
    - latency: 8.722745ms
      message: 'load-balancer-api-internal: resolved host name af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:17:36Z"
    - latency: 5.005655ms
      message: 'load-balancer-api-internal: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:16:36Z"
    - latency: 8.879908ms
      message: 'load-balancer-api-internal: resolved host name af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:16:36Z"
    - latency: 3.557545ms
      message: 'load-balancer-api-internal: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:15:36Z"
    - latency: 9.062942ms
      message: 'load-balancer-api-internal: resolved host name af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:15:36Z"
    - latency: 4.737518ms
      message: 'load-balancer-api-internal: tcp connection to af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:14:36Z"
    - latency: 12.955089ms
      message: 'load-balancer-api-internal: resolved host name af0e0198d3cc945f3847b320e31096fc-a5858c6bb6e356fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:14:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:12:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-239-to-network-check-target-ip-10-0-129-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-239.ec2.internal
      uid: f57b3fb9-33a8-4088-8f09-ee3b125bc16e
    resourceVersion: "10971"
    uid: 54e0dfa8-a02d-43a3-920e-93fa6281801c
  spec:
    sourcePod: network-check-source-685456655f-7bg7x
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:12:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-239-to-network-check-target-ip-10-0-136-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-239.ec2.internal
      uid: f57b3fb9-33a8-4088-8f09-ee3b125bc16e
    resourceVersion: "10972"
    uid: f44a78b6-2964-47a0-a084-1053d7d1ee72
  spec:
    sourcePod: network-check-source-685456655f-7bg7x
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:12:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-239-to-network-check-target-ip-10-0-143-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-239.ec2.internal
      uid: f57b3fb9-33a8-4088-8f09-ee3b125bc16e
    resourceVersion: "10973"
    uid: 7b9b5b76-9292-4e1c-a610-e02e0d2f5c83
  spec:
    sourcePod: network-check-source-685456655f-7bg7x
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T03:12:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-239-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-239.ec2.internal
      uid: f57b3fb9-33a8-4088-8f09-ee3b125bc16e
    resourceVersion: "14284"
    uid: d7f5a728-762a-43a8-8b99-8bbdbb9b8163
  spec:
    sourcePod: network-check-source-685456655f-7bg7x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T03:18:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.548µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:18:36Z"
    - latency: 1.698867ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:18:36Z"
    - latency: 875.093µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:17:36Z"
    - latency: 2.087206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:17:36Z"
    - latency: 868.004µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:16:36Z"
    - latency: 1.839665ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:16:36Z"
    - latency: 1.056204ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:15:36Z"
    - latency: 2.141677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:15:36Z"
    - latency: 813.558µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:14:36Z"
    - latency: 6.231946ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:14:36Z"
kind: List
metadata:
  resourceVersion: ""