apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T11:28:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: 1c61e1a1-d9c3-4219-9fd3-df522bd86fe1
    resourceVersion: "14185"
    uid: 82f5b8b0-8c73-4020-8e02-a511dabc35df
  spec:
    sourcePod: network-check-source-869dcfcdcd-llb64
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T11:35:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 792.369µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:35:35Z"
    - latency: 1.381157ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:34:35Z"
    - latency: 927.011µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:33:35Z"
    - latency: 896.426µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:32:35Z"
    - latency: 706.361µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:35Z"
    - latency: 984.757µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:35Z"
    - latency: 959.013µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T11:28:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: 1c61e1a1-d9c3-4219-9fd3-df522bd86fe1
    resourceVersion: "13781"
    uid: acd22249-e466-4be4-bf93-65757d00ab5a
  spec:
    sourcePod: network-check-source-869dcfcdcd-llb64
    targetEndpoint: aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T11:34:35Z"
      message: 'load-balancer-api-external: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.894876ms
      message: 'load-balancer-api-external: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:34:35Z"
    - latency: 6.637658ms
      message: 'load-balancer-api-external: resolved host name aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:34:35Z"
    - latency: 4.445167ms
      message: 'load-balancer-api-external: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:33:35Z"
    - latency: 7.428856ms
      message: 'load-balancer-api-external: resolved host name aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:33:35Z"
    - latency: 4.913121ms
      message: 'load-balancer-api-external: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:32:35Z"
    - latency: 6.434417ms
      message: 'load-balancer-api-external: resolved host name aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:32:35Z"
    - latency: 4.480147ms
      message: 'load-balancer-api-external: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:35Z"
    - latency: 7.90256ms
      message: 'load-balancer-api-external: resolved host name aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:31:35Z"
    - latency: 5.502191ms
      message: 'load-balancer-api-external: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:35Z"
    - latency: 6.630764ms
      message: 'load-balancer-api-external: resolved host name aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:30:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T11:28:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: 1c61e1a1-d9c3-4219-9fd3-df522bd86fe1
    resourceVersion: "13782"
    uid: 512107c9-d78c-4d13-b0cf-fd1209d9b713
  spec:
    sourcePod: network-check-source-869dcfcdcd-llb64
    targetEndpoint: aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T11:34:35Z"
      message: 'load-balancer-api-internal: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.982174ms
      message: 'load-balancer-api-internal: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:34:35Z"
    - latency: 6.485102ms
      message: 'load-balancer-api-internal: resolved host name aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:34:35Z"
    - latency: 4.472111ms
      message: 'load-balancer-api-internal: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:33:35Z"
    - latency: 7.383324ms
      message: 'load-balancer-api-internal: resolved host name aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:33:35Z"
    - latency: 4.945853ms
      message: 'load-balancer-api-internal: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:32:35Z"
    - latency: 6.282226ms
      message: 'load-balancer-api-internal: resolved host name aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:32:35Z"
    - latency: 3.785376ms
      message: 'load-balancer-api-internal: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:35Z"
    - latency: 7.929362ms
      message: 'load-balancer-api-internal: resolved host name aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:31:35Z"
    - latency: 5.614022ms
      message: 'load-balancer-api-internal: tcp connection to aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:35Z"
    - latency: 6.55169ms
      message: 'load-balancer-api-internal: resolved host name aff534536405e4f79b3fa4d07d734bd4-f7091534592b2c49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:30:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T11:28:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-network-check-target-ip-10-0-135-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: 1c61e1a1-d9c3-4219-9fd3-df522bd86fe1
    resourceVersion: "14183"
    uid: fd68483a-cdcb-47cb-8d57-2b0094229ffe
  spec:
    sourcePod: network-check-source-869dcfcdcd-llb64
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T11:35:35Z"
      message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.929542ms
      message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:35:35Z"
    - latency: 1.928404ms
      message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:34:35Z"
    - latency: 2.892887ms
      message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:33:35Z"
    - latency: 1.835491ms
      message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:32:35Z"
    - latency: 1.592548ms
      message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:35Z"
    - latency: 2.087476ms
      message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:35Z"
    - latency: 2.205803ms
      message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T11:28:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-network-check-target-ip-10-0-137-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: 1c61e1a1-d9c3-4219-9fd3-df522bd86fe1
    resourceVersion: "14184"
    uid: ccd6496f-c811-43f6-bdc5-14d81680f798
  spec:
    sourcePod: network-check-source-869dcfcdcd-llb64
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T11:35:35Z"
      message: 'network-check-target-ip-10-0-137-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.917202ms
      message: 'network-check-target-ip-10-0-137-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:35:35Z"
    - latency: 2.42824ms
      message: 'network-check-target-ip-10-0-137-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:34:35Z"
    - latency: 2.672492ms
      message: 'network-check-target-ip-10-0-137-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:33:35Z"
    - latency: 2.083282ms
      message: 'network-check-target-ip-10-0-137-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:32:35Z"
    - latency: 1.894261ms
      message: 'network-check-target-ip-10-0-137-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:35Z"
    - latency: 2.068778ms
      message: 'network-check-target-ip-10-0-137-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:35Z"
    - latency: 2.002629ms
      message: 'network-check-target-ip-10-0-137-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T11:28:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-network-check-target-ip-10-0-142-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: 1c61e1a1-d9c3-4219-9fd3-df522bd86fe1
    resourceVersion: "14182"
    uid: 7f513ebf-e229-4ff9-9296-5b0bac7b354e
  spec:
    sourcePod: network-check-source-869dcfcdcd-llb64
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T11:35:35Z"
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 961.887µs
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:35:35Z"
    - latency: 953.225µs
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:34:35Z"
    - latency: 895.587µs
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:33:35Z"
    - latency: 1.472558ms
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:32:35Z"
    - latency: 965.276µs
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:35Z"
    - latency: 1.016995ms
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:35Z"
    - latency: 1.225439ms
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T11:28:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: 1c61e1a1-d9c3-4219-9fd3-df522bd86fe1
    resourceVersion: "13780"
    uid: 58837f23-17f1-4b21-8995-4fb6b63fa155
  spec:
    sourcePod: network-check-source-869dcfcdcd-llb64
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T11:34:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.060771ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:34:35Z"
    - latency: 1.901531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:34:35Z"
    - latency: 1.027435ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:33:35Z"
    - latency: 1.942298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:33:35Z"
    - latency: 947.295µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:32:35Z"
    - latency: 1.783307ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:32:35Z"
    - latency: 775.136µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:35Z"
    - latency: 1.671486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:31:35Z"
    - latency: 1.015929ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:35Z"
    - latency: 1.78902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:30:35Z"
kind: List
metadata:
  resourceVersion: ""