apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T03:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-197-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-197.ec2.internal
      uid: eb5d1f06-22b6-456e-88f2-3a93eb070456
    resourceVersion: "10940"
    uid: 96473c62-6215-4598-8e8b-2e99f591706b
  spec:
    sourcePod: network-check-source-869dcfcdcd-lhbzj
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T03:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-197-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-197.ec2.internal
      uid: eb5d1f06-22b6-456e-88f2-3a93eb070456
    resourceVersion: "14457"
    uid: 2100f5e0-0086-4ac7-b88c-247fa4b8f9cc
  spec:
    sourcePod: network-check-source-869dcfcdcd-lhbzj
    targetEndpoint: a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T03:53:30Z"
      message: 'load-balancer-api-external: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.149939ms
      message: 'load-balancer-api-external: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:53:30Z"
    - latency: 7.816288ms
      message: 'load-balancer-api-external: resolved host name a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:53:30Z"
    - latency: 4.993257ms
      message: 'load-balancer-api-external: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:52:30Z"
    - latency: 7.470018ms
      message: 'load-balancer-api-external: resolved host name a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:52:30Z"
    - latency: 4.664152ms
      message: 'load-balancer-api-external: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:51:30Z"
    - latency: 8.302062ms
      message: 'load-balancer-api-external: resolved host name a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:51:30Z"
    - latency: 4.908664ms
      message: 'load-balancer-api-external: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:50:30Z"
    - latency: 7.322679ms
      message: 'load-balancer-api-external: resolved host name a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:50:30Z"
    - latency: 5.364559ms
      message: 'load-balancer-api-external: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:49:30Z"
    - latency: 7.243841ms
      message: 'load-balancer-api-external: resolved host name a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:49:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T03:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-197-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-197.ec2.internal
      uid: eb5d1f06-22b6-456e-88f2-3a93eb070456
    resourceVersion: "14456"
    uid: 1514ae67-04a2-467f-af58-76fc892e631f
  spec:
    sourcePod: network-check-source-869dcfcdcd-lhbzj
    targetEndpoint: a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T03:53:30Z"
      message: 'load-balancer-api-internal: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.131232ms
      message: 'load-balancer-api-internal: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:53:30Z"
    - latency: 7.897412ms
      message: 'load-balancer-api-internal: resolved host name a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:53:30Z"
    - latency: 4.974425ms
      message: 'load-balancer-api-internal: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:52:30Z"
    - latency: 7.555755ms
      message: 'load-balancer-api-internal: resolved host name a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:52:30Z"
    - latency: 5.179748ms
      message: 'load-balancer-api-internal: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:51:30Z"
    - latency: 8.389025ms
      message: 'load-balancer-api-internal: resolved host name a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:51:30Z"
    - latency: 4.881542ms
      message: 'load-balancer-api-internal: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:50:30Z"
    - latency: 7.419113ms
      message: 'load-balancer-api-internal: resolved host name a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:50:30Z"
    - latency: 5.378618ms
      message: 'load-balancer-api-internal: tcp connection to a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:49:30Z"
    - latency: 7.31699ms
      message: 'load-balancer-api-internal: resolved host name a4d3018f21dd84b55b18090b27a0d79b-e764b5e5b80b68de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:49:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T03:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-197-to-network-check-target-ip-10-0-130-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-197.ec2.internal
      uid: eb5d1f06-22b6-456e-88f2-3a93eb070456
    resourceVersion: "10947"
    uid: ad064159-8ab6-4054-bdbf-6d76652cdcaa
  spec:
    sourcePod: network-check-source-869dcfcdcd-lhbzj
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T03:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-197-to-network-check-target-ip-10-0-136-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-197.ec2.internal
      uid: eb5d1f06-22b6-456e-88f2-3a93eb070456
    resourceVersion: "10948"
    uid: b093aa8e-834f-4f39-99a6-c5efc2f1a65a
  spec:
    sourcePod: network-check-source-869dcfcdcd-lhbzj
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T03:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-197-to-network-check-target-ip-10-0-141-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-197.ec2.internal
      uid: eb5d1f06-22b6-456e-88f2-3a93eb070456
    resourceVersion: "10946"
    uid: d2a44241-1d39-4e2f-a864-a2d9894eca73
  spec:
    sourcePod: network-check-source-869dcfcdcd-lhbzj
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T03:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-197-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-197.ec2.internal
      uid: eb5d1f06-22b6-456e-88f2-3a93eb070456
    resourceVersion: "14455"
    uid: 0439f418-ef36-4fa8-b632-8b9836669b45
  spec:
    sourcePod: network-check-source-869dcfcdcd-lhbzj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T03:53:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 815.52µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:53:30Z"
    - latency: 1.550309ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:53:30Z"
    - latency: 864.609µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:52:30Z"
    - latency: 1.641692ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:52:30Z"
    - latency: 1.067697ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:51:30Z"
    - latency: 1.827063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:51:30Z"
    - latency: 888.779µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:50:30Z"
    - latency: 1.667599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:50:30Z"
    - latency: 1.093583ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T03:49:30Z"
    - latency: 1.548587ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T03:49:30Z"
kind: List
metadata:
  resourceVersion: ""