apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 32cd7da1-8cb8-428c-8e03-2c374896f5cb
    resourceVersion: "10690"
    uid: d207d865-bffe-4263-b7d4-aafd91c9400d
  spec:
    sourcePod: network-check-source-7d88cb55d8-w5qcp
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 32cd7da1-8cb8-428c-8e03-2c374896f5cb
    resourceVersion: "21588"
    uid: 421d2bbe-a8b1-45dc-b761-bf175994df84
  spec:
    sourcePod: network-check-source-7d88cb55d8-w5qcp
    targetEndpoint: aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:44:36Z"
      message: 'load-balancer-api-external: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.019996ms
      message: 'load-balancer-api-external: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:44:36Z"
    - latency: 7.988253ms
      message: 'load-balancer-api-external: resolved host name aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:44:36Z"
    - latency: 4.650977ms
      message: 'load-balancer-api-external: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:43:36Z"
    - latency: 8.925267ms
      message: 'load-balancer-api-external: resolved host name aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:43:36Z"
    - latency: 4.306825ms
      message: 'load-balancer-api-external: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:42:36Z"
    - latency: 8.318626ms
      message: 'load-balancer-api-external: resolved host name aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:42:36Z"
    - latency: 3.733758ms
      message: 'load-balancer-api-external: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:41:36Z"
    - latency: 9.054016ms
      message: 'load-balancer-api-external: resolved host name aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:41:36Z"
    - latency: 4.481257ms
      message: 'load-balancer-api-external: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:40:36Z"
    - latency: 8.227719ms
      message: 'load-balancer-api-external: resolved host name aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:40:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 32cd7da1-8cb8-428c-8e03-2c374896f5cb
    resourceVersion: "21587"
    uid: e8164ed6-1984-44b7-a5fd-0fceeda9892e
  spec:
    sourcePod: network-check-source-7d88cb55d8-w5qcp
    targetEndpoint: aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:44:36Z"
      message: 'load-balancer-api-internal: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.222245ms
      message: 'load-balancer-api-internal: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:44:36Z"
    - latency: 7.966618ms
      message: 'load-balancer-api-internal: resolved host name aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:44:36Z"
    - latency: 4.179059ms
      message: 'load-balancer-api-internal: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:43:36Z"
    - latency: 9.050852ms
      message: 'load-balancer-api-internal: resolved host name aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:43:36Z"
    - latency: 4.922203ms
      message: 'load-balancer-api-internal: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:42:36Z"
    - latency: 8.393944ms
      message: 'load-balancer-api-internal: resolved host name aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:42:36Z"
    - latency: 3.290945ms
      message: 'load-balancer-api-internal: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:41:36Z"
    - latency: 9.099017ms
      message: 'load-balancer-api-internal: resolved host name aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:41:36Z"
    - latency: 4.97439ms
      message: 'load-balancer-api-internal: tcp connection to aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:40:36Z"
    - latency: 8.263266ms
      message: 'load-balancer-api-internal: resolved host name aaf2256664e7f46e087d1a9d1576c153-1b6ff62b023bf01a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:40:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-network-check-target-ip-10-0-129-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 32cd7da1-8cb8-428c-8e03-2c374896f5cb
    resourceVersion: "10696"
    uid: 50b1844c-fcff-4c5d-8f65-dc0c8779aa54
  spec:
    sourcePod: network-check-source-7d88cb55d8-w5qcp
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-network-check-target-ip-10-0-130-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 32cd7da1-8cb8-428c-8e03-2c374896f5cb
    resourceVersion: "10697"
    uid: 8fe1c78a-4435-439d-b94c-bb9ede2c005d
  spec:
    sourcePod: network-check-source-7d88cb55d8-w5qcp
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-network-check-target-ip-10-0-130-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 32cd7da1-8cb8-428c-8e03-2c374896f5cb
    resourceVersion: "10695"
    uid: 82cecab0-8929-4e87-9916-77b7da4c3df3
  spec:
    sourcePod: network-check-source-7d88cb55d8-w5qcp
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:38:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 32cd7da1-8cb8-428c-8e03-2c374896f5cb
    resourceVersion: "21586"
    uid: b60c1430-cc35-4bca-88ac-14ef0a16f7f0
  spec:
    sourcePod: network-check-source-7d88cb55d8-w5qcp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:44:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.014997ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:44:36Z"
    - latency: 1.803785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:44:36Z"
    - latency: 908.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:43:36Z"
    - latency: 1.679719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:43:36Z"
    - latency: 891.253µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:42:36Z"
    - latency: 1.684172ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:42:36Z"
    - latency: 849.938µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:41:36Z"
    - latency: 1.70063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:41:36Z"
    - latency: 867.023µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:40:36Z"
    - latency: 1.587091ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:40:36Z"
kind: List
metadata:
  resourceVersion: ""