apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:45:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 31f6db36-ead3-4606-9e61-80c6a69870a1
    resourceVersion: "11478"
    uid: d0e18c14-9705-4317-9b1a-ac22de0c9bbb
  spec:
    sourcePod: network-check-source-7d88cb55d8-8tgh9
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:45:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 31f6db36-ead3-4606-9e61-80c6a69870a1
    resourceVersion: "15080"
    uid: 0f5a5d85-75af-4d13-9428-beac6b3d9aa5
  spec:
    sourcePod: network-check-source-7d88cb55d8-8tgh9
    targetEndpoint: a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T13:51:54Z"
      message: 'load-balancer-api-external: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.379678ms
      message: 'load-balancer-api-external: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:51:54Z"
    - latency: 12.451916ms
      message: 'load-balancer-api-external: resolved host name a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:51:54Z"
    - latency: 6.765521ms
      message: 'load-balancer-api-external: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:50:54Z"
    - latency: 10.697474ms
      message: 'load-balancer-api-external: resolved host name a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:50:54Z"
    - latency: 4.828732ms
      message: 'load-balancer-api-external: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:49:54Z"
    - latency: 7.566258ms
      message: 'load-balancer-api-external: resolved host name a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:49:54Z"
    - latency: 3.477143ms
      message: 'load-balancer-api-external: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:48:54Z"
    - latency: 8.243933ms
      message: 'load-balancer-api-external: resolved host name a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:48:54Z"
    - latency: 4.304913ms
      message: 'load-balancer-api-external: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:47:54Z"
    - latency: 11.683481ms
      message: 'load-balancer-api-external: resolved host name a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:47:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:45:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 31f6db36-ead3-4606-9e61-80c6a69870a1
    resourceVersion: "15079"
    uid: 37dec1f5-6c78-421e-a497-53f64aaf6afb
  spec:
    sourcePod: network-check-source-7d88cb55d8-8tgh9
    targetEndpoint: a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T13:51:54Z"
      message: 'load-balancer-api-internal: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.68374ms
      message: 'load-balancer-api-internal: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:51:54Z"
    - latency: 12.369422ms
      message: 'load-balancer-api-internal: resolved host name a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:51:54Z"
    - latency: 6.829553ms
      message: 'load-balancer-api-internal: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:50:54Z"
    - latency: 10.579489ms
      message: 'load-balancer-api-internal: resolved host name a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:50:54Z"
    - latency: 4.282125ms
      message: 'load-balancer-api-internal: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:49:54Z"
    - latency: 7.372376ms
      message: 'load-balancer-api-internal: resolved host name a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:49:54Z"
    - latency: 3.909592ms
      message: 'load-balancer-api-internal: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:48:54Z"
    - latency: 8.208805ms
      message: 'load-balancer-api-internal: resolved host name a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:48:54Z"
    - latency: 4.298687ms
      message: 'load-balancer-api-internal: tcp connection to a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:47:54Z"
    - latency: 11.636901ms
      message: 'load-balancer-api-internal: resolved host name a26f483eacada4a2f96f13d5f58c1a6a-51fe2011bb33230b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:47:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:45:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-network-check-target-ip-10-0-129-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 31f6db36-ead3-4606-9e61-80c6a69870a1
    resourceVersion: "11484"
    uid: 9c67320d-890d-4a18-9210-09866c5d3862
  spec:
    sourcePod: network-check-source-7d88cb55d8-8tgh9
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:45:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-network-check-target-ip-10-0-132-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 31f6db36-ead3-4606-9e61-80c6a69870a1
    resourceVersion: "11483"
    uid: 11b47ee1-c309-4c40-946c-a2597e5b7bf0
  spec:
    sourcePod: network-check-source-7d88cb55d8-8tgh9
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:45:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-network-check-target-ip-10-0-140-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 31f6db36-ead3-4606-9e61-80c6a69870a1
    resourceVersion: "11482"
    uid: 17260b13-8a92-4694-b078-5c69cc81aa4f
  spec:
    sourcePod: network-check-source-7d88cb55d8-8tgh9
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:45:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-205-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-205.ec2.internal
      uid: 31f6db36-ead3-4606-9e61-80c6a69870a1
    resourceVersion: "15078"
    uid: 573161a1-8037-4723-b611-9019467fa42b
  spec:
    sourcePod: network-check-source-7d88cb55d8-8tgh9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T13:51:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 828.692µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:51:54Z"
    - latency: 2.1823ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:51:54Z"
    - latency: 934.944µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:50:54Z"
    - latency: 1.98087ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:50:54Z"
    - latency: 789.114µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:49:54Z"
    - latency: 1.616057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:49:54Z"
    - latency: 941.478µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:48:54Z"
    - latency: 1.733506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:48:54Z"
    - latency: 1.012559ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:47:54Z"
    - latency: 1.603969ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:47:54Z"
kind: List
metadata:
  resourceVersion: ""