apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-245-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-245.ec2.internal
      uid: ef040088-1cd2-47ac-ba38-8b54c02b0ff6
    resourceVersion: "11374"
    uid: b0ebb77e-4e8b-4610-8994-58cd59e7dc37
  spec:
    sourcePod: network-check-source-7d88cb55d8-rcfhv
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-245-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-245.ec2.internal
      uid: ef040088-1cd2-47ac-ba38-8b54c02b0ff6
    resourceVersion: "15019"
    uid: 73a6f9c4-142c-41dc-9ffe-817b1889d3a2
  spec:
    sourcePod: network-check-source-7d88cb55d8-rcfhv
    targetEndpoint: a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T09:45:43Z"
      message: 'load-balancer-api-external: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.709394ms
      message: 'load-balancer-api-external: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:45:43Z"
    - latency: 6.39769ms
      message: 'load-balancer-api-external: resolved host name a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:45:43Z"
    - latency: 4.844374ms
      message: 'load-balancer-api-external: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:44:43Z"
    - latency: 8.409017ms
      message: 'load-balancer-api-external: resolved host name a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:44:43Z"
    - latency: 4.576075ms
      message: 'load-balancer-api-external: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:43:43Z"
    - latency: 8.907478ms
      message: 'load-balancer-api-external: resolved host name a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:43:43Z"
    - latency: 4.254965ms
      message: 'load-balancer-api-external: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:42:43Z"
    - latency: 7.991156ms
      message: 'load-balancer-api-external: resolved host name a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:42:43Z"
    - latency: 5.170554ms
      message: 'load-balancer-api-external: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:41:43Z"
    - latency: 7.246954ms
      message: 'load-balancer-api-external: resolved host name a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:41:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-245-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-245.ec2.internal
      uid: ef040088-1cd2-47ac-ba38-8b54c02b0ff6
    resourceVersion: "15020"
    uid: 5c5e13f1-c6cb-4f4f-9e78-b5b426f2b9fe
  spec:
    sourcePod: network-check-source-7d88cb55d8-rcfhv
    targetEndpoint: a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T09:45:43Z"
      message: 'load-balancer-api-internal: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.916306ms
      message: 'load-balancer-api-internal: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:45:43Z"
    - latency: 6.331928ms
      message: 'load-balancer-api-internal: resolved host name a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:45:43Z"
    - latency: 4.625668ms
      message: 'load-balancer-api-internal: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:44:43Z"
    - latency: 8.471605ms
      message: 'load-balancer-api-internal: resolved host name a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:44:43Z"
    - latency: 4.661969ms
      message: 'load-balancer-api-internal: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:43:43Z"
    - latency: 8.867715ms
      message: 'load-balancer-api-internal: resolved host name a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:43:43Z"
    - latency: 4.189717ms
      message: 'load-balancer-api-internal: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:42:43Z"
    - latency: 8.057159ms
      message: 'load-balancer-api-internal: resolved host name a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:42:43Z"
    - latency: 5.188509ms
      message: 'load-balancer-api-internal: tcp connection to a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:41:43Z"
    - latency: 7.332665ms
      message: 'load-balancer-api-internal: resolved host name a890408f6b2a342b1aa22a5553970671-10d5c9c5891cb66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:41:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-245-to-network-check-target-ip-10-0-132-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-245.ec2.internal
      uid: ef040088-1cd2-47ac-ba38-8b54c02b0ff6
    resourceVersion: "11379"
    uid: 222b5413-cf26-4d44-bd1d-4b24e5e99b73
  spec:
    sourcePod: network-check-source-7d88cb55d8-rcfhv
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-245-to-network-check-target-ip-10-0-134-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-245.ec2.internal
      uid: ef040088-1cd2-47ac-ba38-8b54c02b0ff6
    resourceVersion: "11380"
    uid: 38cb31e7-17fe-4319-96d7-f6c0c2774e94
  spec:
    sourcePod: network-check-source-7d88cb55d8-rcfhv
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-245-to-network-check-target-ip-10-0-137-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-245.ec2.internal
      uid: ef040088-1cd2-47ac-ba38-8b54c02b0ff6
    resourceVersion: "11378"
    uid: f17085fb-1e71-478b-81b7-b546fe98349b
  spec:
    sourcePod: network-check-source-7d88cb55d8-rcfhv
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-245-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-245.ec2.internal
      uid: ef040088-1cd2-47ac-ba38-8b54c02b0ff6
    resourceVersion: "15018"
    uid: 199672e6-0259-42a4-8544-c58b64f38fa5
  spec:
    sourcePod: network-check-source-7d88cb55d8-rcfhv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T09:45:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067063ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:45:43Z"
    - latency: 1.850206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:45:43Z"
    - latency: 1.324096ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:44:43Z"
    - latency: 1.873334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:44:43Z"
    - latency: 876.868µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:43:43Z"
    - latency: 2.130723ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:43:43Z"
    - latency: 1.092179ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:42:43Z"
    - latency: 1.745057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:42:43Z"
    - latency: 1.027769ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:41:43Z"
    - latency: 1.705348ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:41:43Z"
kind: List
metadata:
  resourceVersion: ""