apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: d447570a-3a6a-4e14-9543-8d6184c8c152
    resourceVersion: "10830"
    uid: 80f3dc7f-6ac4-4bd4-b6f7-3d1cd26f21e9
  spec:
    sourcePod: network-check-source-65bdbbff45-dm9rx
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: d447570a-3a6a-4e14-9543-8d6184c8c152
    resourceVersion: "14415"
    uid: 38bd81e4-769f-42b6-8ab3-420781988af0
  spec:
    sourcePod: network-check-source-65bdbbff45-dm9rx
    targetEndpoint: a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T13:03:31Z"
      message: 'load-balancer-api-external: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.778461ms
      message: 'load-balancer-api-external: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:03:31Z"
    - latency: 8.852184ms
      message: 'load-balancer-api-external: resolved host name a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:03:31Z"
    - latency: 4.835808ms
      message: 'load-balancer-api-external: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:02:31Z"
    - latency: 9.195544ms
      message: 'load-balancer-api-external: resolved host name a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:02:31Z"
    - latency: 5.273437ms
      message: 'load-balancer-api-external: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:01:31Z"
    - latency: 7.889433ms
      message: 'load-balancer-api-external: resolved host name a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:01:31Z"
    - latency: 4.880826ms
      message: 'load-balancer-api-external: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:00:31Z"
    - latency: 12.447772ms
      message: 'load-balancer-api-external: resolved host name a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:00:31Z"
    - latency: 4.891183ms
      message: 'load-balancer-api-external: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T12:59:31Z"
    - latency: 9.551227ms
      message: 'load-balancer-api-external: resolved host name a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T12:59:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: d447570a-3a6a-4e14-9543-8d6184c8c152
    resourceVersion: "14416"
    uid: 524f6366-5fd1-418a-8a75-99a2db62bd69
  spec:
    sourcePod: network-check-source-65bdbbff45-dm9rx
    targetEndpoint: a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T13:03:31Z"
      message: 'load-balancer-api-internal: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.133937ms
      message: 'load-balancer-api-internal: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:03:31Z"
    - latency: 8.881752ms
      message: 'load-balancer-api-internal: resolved host name a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:03:31Z"
    - latency: 4.811724ms
      message: 'load-balancer-api-internal: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:02:31Z"
    - latency: 9.13449ms
      message: 'load-balancer-api-internal: resolved host name a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:02:31Z"
    - latency: 5.093716ms
      message: 'load-balancer-api-internal: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:01:31Z"
    - latency: 7.838625ms
      message: 'load-balancer-api-internal: resolved host name a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:01:31Z"
    - latency: 4.916474ms
      message: 'load-balancer-api-internal: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:00:31Z"
    - latency: 12.397894ms
      message: 'load-balancer-api-internal: resolved host name a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:00:31Z"
    - latency: 4.686098ms
      message: 'load-balancer-api-internal: tcp connection to a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T12:59:31Z"
    - latency: 9.50605ms
      message: 'load-balancer-api-internal: resolved host name a782b7d8762584159902455f14627f17-e68cbf5db38314a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T12:59:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-ip-10-0-131-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: d447570a-3a6a-4e14-9543-8d6184c8c152
    resourceVersion: "10826"
    uid: aa11666b-763e-4061-8fdd-89d5b1a3095d
  spec:
    sourcePod: network-check-source-65bdbbff45-dm9rx
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-ip-10-0-133-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: d447570a-3a6a-4e14-9543-8d6184c8c152
    resourceVersion: "10828"
    uid: 1d605d8e-1354-4895-a097-114992359cc7
  spec:
    sourcePod: network-check-source-65bdbbff45-dm9rx
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-ip-10-0-142-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: d447570a-3a6a-4e14-9543-8d6184c8c152
    resourceVersion: "10827"
    uid: bbe0ecfb-4ab3-4a7a-9cff-f393781caace
  spec:
    sourcePod: network-check-source-65bdbbff45-dm9rx
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T12:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: d447570a-3a6a-4e14-9543-8d6184c8c152
    resourceVersion: "14413"
    uid: 36a5e278-5a49-4e36-ab47-b2df071b6274
  spec:
    sourcePod: network-check-source-65bdbbff45-dm9rx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T13:03:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.3µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:03:31Z"
    - latency: 1.545748ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:03:31Z"
    - latency: 877.559µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:02:31Z"
    - latency: 2.204852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:02:31Z"
    - latency: 858.779µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:01:31Z"
    - latency: 1.740746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:01:31Z"
    - latency: 848.645µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T13:00:31Z"
    - latency: 5.093131ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T13:00:31Z"
    - latency: 1.1371ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T12:59:31Z"
    - latency: 1.671727ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T12:59:31Z"
kind: List
metadata:
  resourceVersion: ""