apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:32:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-227-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-227.ec2.internal
      uid: f46a7ae7-9db7-44d3-b8d2-06daccc34f59
    resourceVersion: "10785"
    uid: 3a75f83a-bcba-440d-965e-d15f6167a676
  spec:
    sourcePod: network-check-source-869dcfcdcd-5nbqs
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:32:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-227-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-227.ec2.internal
      uid: f46a7ae7-9db7-44d3-b8d2-06daccc34f59
    resourceVersion: "13591"
    uid: f5986192-2713-4474-84d0-0a24eab7743b
  spec:
    sourcePod: network-check-source-869dcfcdcd-5nbqs
    targetEndpoint: a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:38:24Z"
      message: 'load-balancer-api-external: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.937761ms
      message: 'load-balancer-api-external: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:38:24Z"
    - latency: 8.483ms
      message: 'load-balancer-api-external: resolved host name a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:38:24Z"
    - latency: 4.623094ms
      message: 'load-balancer-api-external: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:37:24Z"
    - latency: 8.340262ms
      message: 'load-balancer-api-external: resolved host name a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:37:24Z"
    - latency: 5.3829ms
      message: 'load-balancer-api-external: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:36:24Z"
    - latency: 9.840506ms
      message: 'load-balancer-api-external: resolved host name a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:36:24Z"
    - latency: 4.691116ms
      message: 'load-balancer-api-external: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:35:24Z"
    - latency: 8.822152ms
      message: 'load-balancer-api-external: resolved host name a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:35:24Z"
    - latency: 5.441978ms
      message: 'load-balancer-api-external: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:34:24Z"
    - latency: 7.557324ms
      message: 'load-balancer-api-external: resolved host name a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:34:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:32:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-227-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-227.ec2.internal
      uid: f46a7ae7-9db7-44d3-b8d2-06daccc34f59
    resourceVersion: "13590"
    uid: 25eb874d-2de1-4ac9-a76a-78bc5c6c9345
  spec:
    sourcePod: network-check-source-869dcfcdcd-5nbqs
    targetEndpoint: a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:38:24Z"
      message: 'load-balancer-api-internal: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.96132ms
      message: 'load-balancer-api-internal: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:38:24Z"
    - latency: 8.429685ms
      message: 'load-balancer-api-internal: resolved host name a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:38:24Z"
    - latency: 4.884462ms
      message: 'load-balancer-api-internal: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:37:24Z"
    - latency: 8.289499ms
      message: 'load-balancer-api-internal: resolved host name a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:37:24Z"
    - latency: 5.435272ms
      message: 'load-balancer-api-internal: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:36:24Z"
    - latency: 9.170652ms
      message: 'load-balancer-api-internal: resolved host name a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:36:24Z"
    - latency: 4.409272ms
      message: 'load-balancer-api-internal: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:35:24Z"
    - latency: 8.766155ms
      message: 'load-balancer-api-internal: resolved host name a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:35:24Z"
    - latency: 5.435229ms
      message: 'load-balancer-api-internal: tcp connection to a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:34:24Z"
    - latency: 7.506504ms
      message: 'load-balancer-api-internal: resolved host name a3f65d879f4db40c085786f5b4f81de3-8615e58607db62f1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:34:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:32:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-227-to-network-check-target-ip-10-0-135-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-227.ec2.internal
      uid: f46a7ae7-9db7-44d3-b8d2-06daccc34f59
    resourceVersion: "10792"
    uid: 055ecb83-3a1c-4d4c-9541-7ca8dc6693bd
  spec:
    sourcePod: network-check-source-869dcfcdcd-5nbqs
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:32:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-227-to-network-check-target-ip-10-0-139-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-227.ec2.internal
      uid: f46a7ae7-9db7-44d3-b8d2-06daccc34f59
    resourceVersion: "10791"
    uid: 3c07409b-bb93-4d6a-bdf3-92492805f8ad
  spec:
    sourcePod: network-check-source-869dcfcdcd-5nbqs
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:32:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-227-to-network-check-target-ip-10-0-141-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-227.ec2.internal
      uid: f46a7ae7-9db7-44d3-b8d2-06daccc34f59
    resourceVersion: "10790"
    uid: abd49e1d-1686-426a-aa1d-de422094bb88
  spec:
    sourcePod: network-check-source-869dcfcdcd-5nbqs
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:32:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-227-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-227.ec2.internal
      uid: f46a7ae7-9db7-44d3-b8d2-06daccc34f59
    resourceVersion: "13589"
    uid: a868b322-a6db-40dd-8787-dda05bfc927c
  spec:
    sourcePod: network-check-source-869dcfcdcd-5nbqs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:38:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.43556ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:38:24Z"
    - latency: 1.71449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:38:24Z"
    - latency: 1.163861ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:37:24Z"
    - latency: 1.900758ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:37:24Z"
    - latency: 1.369253ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:36:24Z"
    - latency: 1.744465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:36:24Z"
    - latency: 907.058µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:35:24Z"
    - latency: 1.764884ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:35:24Z"
    - latency: 988.119µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:34:24Z"
    - latency: 1.959254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T11:34:24Z"
kind: List
metadata:
  resourceVersion: ""