apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:07:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-17-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-17.ec2.internal
      uid: 0f508343-fe28-421e-991f-121857883919
    resourceVersion: "11962"
    uid: e08b3ba7-6f60-4a43-8c3f-994263add684
  spec:
    sourcePod: network-check-source-7d88cb55d8-kk6w6
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:07:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-17-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-17.ec2.internal
      uid: 0f508343-fe28-421e-991f-121857883919
    resourceVersion: "14315"
    uid: 78169d42-f697-4ee2-8045-0098f9b03728
  spec:
    sourcePod: network-check-source-7d88cb55d8-kk6w6
    targetEndpoint: ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:13:35Z"
      message: 'load-balancer-api-external: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.395156ms
      message: 'load-balancer-api-external: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:13:35Z"
    - latency: 7.900549ms
      message: 'load-balancer-api-external: resolved host name ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:13:35Z"
    - latency: 5.721744ms
      message: 'load-balancer-api-external: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:12:35Z"
    - latency: 8.023657ms
      message: 'load-balancer-api-external: resolved host name ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:12:35Z"
    - latency: 5.490457ms
      message: 'load-balancer-api-external: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:11:35Z"
    - latency: 8.423485ms
      message: 'load-balancer-api-external: resolved host name ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:11:35Z"
    - latency: 6.352539ms
      message: 'load-balancer-api-external: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:10:35Z"
    - latency: 8.181329ms
      message: 'load-balancer-api-external: resolved host name ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:10:35Z"
    - latency: 6.826611ms
      message: 'load-balancer-api-external: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:09:35Z"
    - latency: 10.79339ms
      message: 'load-balancer-api-external: resolved host name ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:09:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:07:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-17-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-17.ec2.internal
      uid: 0f508343-fe28-421e-991f-121857883919
    resourceVersion: "14316"
    uid: f2f092d3-36db-4fbc-ba02-4b526e534b65
  spec:
    sourcePod: network-check-source-7d88cb55d8-kk6w6
    targetEndpoint: ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:13:35Z"
      message: 'load-balancer-api-internal: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.1531ms
      message: 'load-balancer-api-internal: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:13:35Z"
    - latency: 7.94689ms
      message: 'load-balancer-api-internal: resolved host name ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:13:35Z"
    - latency: 5.730091ms
      message: 'load-balancer-api-internal: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:12:35Z"
    - latency: 8.00305ms
      message: 'load-balancer-api-internal: resolved host name ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:12:35Z"
    - latency: 5.978778ms
      message: 'load-balancer-api-internal: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:11:35Z"
    - latency: 8.480632ms
      message: 'load-balancer-api-internal: resolved host name ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:11:35Z"
    - latency: 6.299462ms
      message: 'load-balancer-api-internal: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:10:35Z"
    - latency: 8.274732ms
      message: 'load-balancer-api-internal: resolved host name ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:10:35Z"
    - latency: 5.98684ms
      message: 'load-balancer-api-internal: tcp connection to ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:09:35Z"
    - latency: 10.759973ms
      message: 'load-balancer-api-internal: resolved host name ac3722b6d62c34d7087696af33b06ec0-3da6a8a06bd2d47d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:09:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:07:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-17-to-network-check-target-ip-10-0-132-108
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-17.ec2.internal
      uid: 0f508343-fe28-421e-991f-121857883919
    resourceVersion: "11969"
    uid: af569719-7cbd-4ee6-ac9e-4ca0d0578e3a
  spec:
    sourcePod: network-check-source-7d88cb55d8-kk6w6
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:07:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-17-to-network-check-target-ip-10-0-138-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-17.ec2.internal
      uid: 0f508343-fe28-421e-991f-121857883919
    resourceVersion: "11968"
    uid: 5d8b775a-fb22-4832-9cd7-23b7bfb95614
  spec:
    sourcePod: network-check-source-7d88cb55d8-kk6w6
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:07:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-17-to-network-check-target-ip-10-0-140-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-17.ec2.internal
      uid: 0f508343-fe28-421e-991f-121857883919
    resourceVersion: "11967"
    uid: cfac4163-00c5-44bc-9d36-54c8d09c7abd
  spec:
    sourcePod: network-check-source-7d88cb55d8-kk6w6
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:07:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-17-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-17.ec2.internal
      uid: 0f508343-fe28-421e-991f-121857883919
    resourceVersion: "14314"
    uid: 50dec605-3f75-4b78-8a4c-8bb8fb4c5886
  spec:
    sourcePod: network-check-source-7d88cb55d8-kk6w6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:13:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 969.175µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:13:35Z"
    - latency: 1.63148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:13:35Z"
    - latency: 823.412µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:12:35Z"
    - latency: 1.464108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:12:35Z"
    - latency: 815.865µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:11:35Z"
    - latency: 1.796892ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:11:35Z"
    - latency: 984.618µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:10:35Z"
    - latency: 1.636385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:10:35Z"
    - latency: 1.307208ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T00:09:35Z"
    - latency: 1.935833ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T00:09:35Z"
kind: List
metadata:
  resourceVersion: ""