apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:53:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: b83d45eb-f0dc-4c98-a14d-68740c5d7036
    resourceVersion: "11146"
    uid: c8b21b6e-2af7-4722-b5ba-ab0758963de9
  spec:
    sourcePod: network-check-source-7f44b6dd87-czcjs
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:53:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: b83d45eb-f0dc-4c98-a14d-68740c5d7036
    resourceVersion: "14735"
    uid: 82e691cc-2600-4ef6-8e17-1bb541d67df8
  spec:
    sourcePod: network-check-source-7f44b6dd87-czcjs
    targetEndpoint: a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T11:59:37Z"
      message: 'load-balancer-api-external: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.9959ms
      message: 'load-balancer-api-external: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:59:37Z"
    - latency: 6.549711ms
      message: 'load-balancer-api-external: resolved host name a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:59:37Z"
    - latency: 4.858329ms
      message: 'load-balancer-api-external: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:58:37Z"
    - latency: 6.419609ms
      message: 'load-balancer-api-external: resolved host name a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:58:37Z"
    - latency: 5.095904ms
      message: 'load-balancer-api-external: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:57:37Z"
    - latency: 6.229202ms
      message: 'load-balancer-api-external: resolved host name a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:57:37Z"
    - latency: 4.294634ms
      message: 'load-balancer-api-external: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:56:37Z"
    - latency: 6.896671ms
      message: 'load-balancer-api-external: resolved host name a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:56:37Z"
    - latency: 4.789071ms
      message: 'load-balancer-api-external: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:55:37Z"
    - latency: 6.473536ms
      message: 'load-balancer-api-external: resolved host name a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:55:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:53:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: b83d45eb-f0dc-4c98-a14d-68740c5d7036
    resourceVersion: "14734"
    uid: 063fd613-7c28-4418-87ef-7f1e385a12c3
  spec:
    sourcePod: network-check-source-7f44b6dd87-czcjs
    targetEndpoint: a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T11:59:37Z"
      message: 'load-balancer-api-internal: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.302128ms
      message: 'load-balancer-api-internal: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:59:37Z"
    - latency: 6.509847ms
      message: 'load-balancer-api-internal: resolved host name a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:59:37Z"
    - latency: 5.373024ms
      message: 'load-balancer-api-internal: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:58:37Z"
    - latency: 6.363885ms
      message: 'load-balancer-api-internal: resolved host name a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:58:37Z"
    - latency: 5.072893ms
      message: 'load-balancer-api-internal: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:57:37Z"
    - latency: 6.155702ms
      message: 'load-balancer-api-internal: resolved host name a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:57:37Z"
    - latency: 5.017528ms
      message: 'load-balancer-api-internal: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:56:37Z"
    - latency: 6.822608ms
      message: 'load-balancer-api-internal: resolved host name a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:56:37Z"
    - latency: 4.257058ms
      message: 'load-balancer-api-internal: tcp connection to a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:55:37Z"
    - latency: 6.512252ms
      message: 'load-balancer-api-internal: resolved host name a07cb93ede5ea438c91934511db1cbbb-8e0635fe3bc0d832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:55:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:53:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-network-check-target-ip-10-0-132-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: b83d45eb-f0dc-4c98-a14d-68740c5d7036
    resourceVersion: "11153"
    uid: 1be792dd-9d72-4db2-b9ed-f8ca23f8eb79
  spec:
    sourcePod: network-check-source-7f44b6dd87-czcjs
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:53:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-network-check-target-ip-10-0-140-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: b83d45eb-f0dc-4c98-a14d-68740c5d7036
    resourceVersion: "11152"
    uid: 8d3199f5-1b75-445e-81b1-92354a893d96
  spec:
    sourcePod: network-check-source-7f44b6dd87-czcjs
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:53:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-network-check-target-ip-10-0-142-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: b83d45eb-f0dc-4c98-a14d-68740c5d7036
    resourceVersion: "11151"
    uid: 177b58a7-ef43-4dd4-8193-83571b2b3b61
  spec:
    sourcePod: network-check-source-7f44b6dd87-czcjs
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:53:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-74-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-74.ec2.internal
      uid: b83d45eb-f0dc-4c98-a14d-68740c5d7036
    resourceVersion: "14733"
    uid: 541e246f-8a7b-410b-9243-69f83bd75be2
  spec:
    sourcePod: network-check-source-7f44b6dd87-czcjs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T11:59:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.163204ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:59:37Z"
    - latency: 1.839465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:59:37Z"
    - latency: 1.10461ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:58:37Z"
    - latency: 1.575217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:58:37Z"
    - latency: 925.986µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:57:37Z"
    - latency: 1.736281ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:57:37Z"
    - latency: 962.584µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:56:37Z"
    - latency: 1.836282ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:56:37Z"
    - latency: 905.511µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:55:37Z"
    - latency: 1.677521ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:55:37Z"
kind: List
metadata:
  resourceVersion: ""