apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T20:13:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-28-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-28.ec2.internal
      uid: f56c7d0e-f86c-4697-a3d3-d87be563b7e3
    resourceVersion: "11858"
    uid: d8505b7a-67a3-4d12-bfcf-b4c200b6fe39
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mc9sg
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T20:13:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-28-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-28.ec2.internal
      uid: f56c7d0e-f86c-4697-a3d3-d87be563b7e3
    resourceVersion: "15296"
    uid: 49584d02-c89c-4358-a862-62957aa0d997
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mc9sg
    targetEndpoint: ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T20:19:21Z"
      message: 'load-balancer-api-external: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.535036ms
      message: 'load-balancer-api-external: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:19:21Z"
    - latency: 6.873472ms
      message: 'load-balancer-api-external: resolved host name ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:19:21Z"
    - latency: 6.780198ms
      message: 'load-balancer-api-external: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:18:21Z"
    - latency: 7.135277ms
      message: 'load-balancer-api-external: resolved host name ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:18:21Z"
    - latency: 4.921979ms
      message: 'load-balancer-api-external: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:17:21Z"
    - latency: 6.070472ms
      message: 'load-balancer-api-external: resolved host name ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:17:21Z"
    - latency: 4.804367ms
      message: 'load-balancer-api-external: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:16:21Z"
    - latency: 7.553051ms
      message: 'load-balancer-api-external: resolved host name ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:16:21Z"
    - latency: 4.985009ms
      message: 'load-balancer-api-external: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:15:21Z"
    - latency: 6.414356ms
      message: 'load-balancer-api-external: resolved host name ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:15:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T20:13:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-28-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-28.ec2.internal
      uid: f56c7d0e-f86c-4697-a3d3-d87be563b7e3
    resourceVersion: "15295"
    uid: 75361f6a-be42-4dda-a8de-9720697bec5d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mc9sg
    targetEndpoint: ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T20:19:21Z"
      message: 'load-balancer-api-internal: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.074561ms
      message: 'load-balancer-api-internal: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:19:21Z"
    - latency: 6.837254ms
      message: 'load-balancer-api-internal: resolved host name ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:19:21Z"
    - latency: 6.179385ms
      message: 'load-balancer-api-internal: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:18:21Z"
    - latency: 7.228377ms
      message: 'load-balancer-api-internal: resolved host name ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:18:21Z"
    - latency: 3.942703ms
      message: 'load-balancer-api-internal: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:17:21Z"
    - latency: 6.185982ms
      message: 'load-balancer-api-internal: resolved host name ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:17:21Z"
    - latency: 4.073218ms
      message: 'load-balancer-api-internal: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:16:21Z"
    - latency: 7.483393ms
      message: 'load-balancer-api-internal: resolved host name ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:16:21Z"
    - latency: 4.278948ms
      message: 'load-balancer-api-internal: tcp connection to ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:15:21Z"
    - latency: 6.343588ms
      message: 'load-balancer-api-internal: resolved host name ac917133951d242a98385c69a9528abb-1c788b4c22712d3a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:15:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T20:13:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-28-to-network-check-target-ip-10-0-129-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-28.ec2.internal
      uid: f56c7d0e-f86c-4697-a3d3-d87be563b7e3
    resourceVersion: "11863"
    uid: a4cb352c-85f5-4c67-adc1-dbb27b5c8351
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mc9sg
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T20:13:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-28-to-network-check-target-ip-10-0-139-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-28.ec2.internal
      uid: f56c7d0e-f86c-4697-a3d3-d87be563b7e3
    resourceVersion: "11864"
    uid: 3e1218b1-9c94-45ee-a400-f88a3942175a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mc9sg
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T20:13:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-28-to-network-check-target-ip-10-0-142-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-28.ec2.internal
      uid: f56c7d0e-f86c-4697-a3d3-d87be563b7e3
    resourceVersion: "11865"
    uid: 4063712b-e19e-4779-886b-0dfb75919a9a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mc9sg
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T20:13:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-28-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-28.ec2.internal
      uid: f56c7d0e-f86c-4697-a3d3-d87be563b7e3
    resourceVersion: "15294"
    uid: 53a9e219-967f-42d5-9cd7-6ce0b0ce56fe
  spec:
    sourcePod: network-check-source-7bc5b6bf85-mc9sg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T20:19:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 986.104µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:19:21Z"
    - latency: 1.997314ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:19:21Z"
    - latency: 866.902µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:18:21Z"
    - latency: 1.983385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:18:21Z"
    - latency: 1.062898ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:17:21Z"
    - latency: 1.686005ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:17:21Z"
    - latency: 937.124µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:16:21Z"
    - latency: 1.865582ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:16:21Z"
    - latency: 1.069924ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T20:15:21Z"
    - latency: 1.767557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T20:15:21Z"
kind: List
metadata:
  resourceVersion: ""