apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:51:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 4bc3dffe-b6c8-4771-a547-f2a96e25136d
    resourceVersion: "11500"
    uid: 424eb1f0-dcde-44bf-8a0a-b1e6ae75849f
  spec:
    sourcePod: network-check-source-65bdbbff45-dcwld
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:51:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 4bc3dffe-b6c8-4771-a547-f2a96e25136d
    resourceVersion: "15008"
    uid: f161c318-a060-4952-b59e-4c6912b353dc
  spec:
    sourcePod: network-check-source-65bdbbff45-dcwld
    targetEndpoint: adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T03:57:13Z"
      message: 'load-balancer-api-external: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.194241ms
      message: 'load-balancer-api-external: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:57:13Z"
    - latency: 6.512354ms
      message: 'load-balancer-api-external: resolved host name adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:57:13Z"
    - latency: 5.247642ms
      message: 'load-balancer-api-external: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:56:13Z"
    - latency: 6.273037ms
      message: 'load-balancer-api-external: resolved host name adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:56:13Z"
    - latency: 3.609418ms
      message: 'load-balancer-api-external: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:55:13Z"
    - latency: 6.569628ms
      message: 'load-balancer-api-external: resolved host name adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:55:13Z"
    - latency: 5.786667ms
      message: 'load-balancer-api-external: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:54:13Z"
    - latency: 6.658713ms
      message: 'load-balancer-api-external: resolved host name adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:54:13Z"
    - latency: 4.845715ms
      message: 'load-balancer-api-external: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:53:13Z"
    - latency: 6.180221ms
      message: 'load-balancer-api-external: resolved host name adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:53:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:51:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 4bc3dffe-b6c8-4771-a547-f2a96e25136d
    resourceVersion: "15009"
    uid: 654f1652-62e4-42f0-889f-da041878f71e
  spec:
    sourcePod: network-check-source-65bdbbff45-dcwld
    targetEndpoint: adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T03:57:13Z"
      message: 'load-balancer-api-internal: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.789004ms
      message: 'load-balancer-api-internal: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:57:13Z"
    - latency: 6.4665ms
      message: 'load-balancer-api-internal: resolved host name adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:57:13Z"
    - latency: 5.236302ms
      message: 'load-balancer-api-internal: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:56:13Z"
    - latency: 6.321588ms
      message: 'load-balancer-api-internal: resolved host name adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:56:13Z"
    - latency: 4.916536ms
      message: 'load-balancer-api-internal: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:55:13Z"
    - latency: 6.536324ms
      message: 'load-balancer-api-internal: resolved host name adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:55:13Z"
    - latency: 5.763685ms
      message: 'load-balancer-api-internal: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:54:13Z"
    - latency: 6.708801ms
      message: 'load-balancer-api-internal: resolved host name adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:54:13Z"
    - latency: 4.874074ms
      message: 'load-balancer-api-internal: tcp connection to adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:53:13Z"
    - latency: 6.130136ms
      message: 'load-balancer-api-internal: resolved host name adcacec54bdb64374a82541613baa67a-2977bdb05b5c678d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:53:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:51:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-ip-10-0-128-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 4bc3dffe-b6c8-4771-a547-f2a96e25136d
    resourceVersion: "11507"
    uid: 94f6a6fd-f510-490e-a33a-8cd11383c3a7
  spec:
    sourcePod: network-check-source-65bdbbff45-dcwld
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:51:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-ip-10-0-129-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 4bc3dffe-b6c8-4771-a547-f2a96e25136d
    resourceVersion: "11505"
    uid: abdc717f-ed7b-4f12-81ed-cdc9fcb65a31
  spec:
    sourcePod: network-check-source-65bdbbff45-dcwld
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:51:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-ip-10-0-143-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 4bc3dffe-b6c8-4771-a547-f2a96e25136d
    resourceVersion: "11504"
    uid: b463ca5a-6d37-470d-b661-65635d030c18
  spec:
    sourcePod: network-check-source-65bdbbff45-dcwld
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:51:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 4bc3dffe-b6c8-4771-a547-f2a96e25136d
    resourceVersion: "15007"
    uid: 8a5873ed-da25-4e08-a4b5-93cc36331eb8
  spec:
    sourcePod: network-check-source-65bdbbff45-dcwld
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T03:57:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 787.282µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:57:13Z"
    - latency: 1.697536ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:57:13Z"
    - latency: 763.13µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:56:13Z"
    - latency: 1.713145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:56:13Z"
    - latency: 1.254506ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:55:13Z"
    - latency: 1.996101ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:55:13Z"
    - latency: 806.046µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:54:13Z"
    - latency: 1.761564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:54:13Z"
    - latency: 793.592µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:53:13Z"
    - latency: 1.57772ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:53:13Z"
kind: List
metadata:
  resourceVersion: ""