apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-139.ec2.internal
      uid: bf7a88c5-581d-461f-bbf5-d43a2d7aeb00
    resourceVersion: "11846"
    uid: 0ea7c2a0-0633-464f-81c7-ec0916340fca
  spec:
    sourcePod: network-check-source-7d88cb55d8-q998z
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-139.ec2.internal
      uid: bf7a88c5-581d-461f-bbf5-d43a2d7aeb00
    resourceVersion: "15457"
    uid: 7348c882-0976-467f-a40c-2dc221a8c202
  spec:
    sourcePod: network-check-source-7d88cb55d8-q998z
    targetEndpoint: a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:33:19Z"
      message: 'load-balancer-api-external: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.503261ms
      message: 'load-balancer-api-external: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:33:19Z"
    - latency: 7.920008ms
      message: 'load-balancer-api-external: resolved host name a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:33:19Z"
    - latency: 6.16256ms
      message: 'load-balancer-api-external: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:32:19Z"
    - latency: 9.053854ms
      message: 'load-balancer-api-external: resolved host name a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:32:19Z"
    - latency: 5.708576ms
      message: 'load-balancer-api-external: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:31:19Z"
    - latency: 6.652087ms
      message: 'load-balancer-api-external: resolved host name a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:31:19Z"
    - latency: 5.886158ms
      message: 'load-balancer-api-external: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:30:19Z"
    - latency: 8.973744ms
      message: 'load-balancer-api-external: resolved host name a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:30:19Z"
    - latency: 4.155366ms
      message: 'load-balancer-api-external: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:29:19Z"
    - latency: 8.597607ms
      message: 'load-balancer-api-external: resolved host name a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:29:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-139.ec2.internal
      uid: bf7a88c5-581d-461f-bbf5-d43a2d7aeb00
    resourceVersion: "15458"
    uid: 378e7d00-d535-403a-a089-7704a43e0158
  spec:
    sourcePod: network-check-source-7d88cb55d8-q998z
    targetEndpoint: a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:33:19Z"
      message: 'load-balancer-api-internal: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.488496ms
      message: 'load-balancer-api-internal: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:33:19Z"
    - latency: 7.832464ms
      message: 'load-balancer-api-internal: resolved host name a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:33:19Z"
    - latency: 5.810086ms
      message: 'load-balancer-api-internal: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:32:19Z"
    - latency: 9.012415ms
      message: 'load-balancer-api-internal: resolved host name a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:32:19Z"
    - latency: 5.858652ms
      message: 'load-balancer-api-internal: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:31:19Z"
    - latency: 6.573197ms
      message: 'load-balancer-api-internal: resolved host name a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:31:19Z"
    - latency: 5.077479ms
      message: 'load-balancer-api-internal: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:30:19Z"
    - latency: 8.89301ms
      message: 'load-balancer-api-internal: resolved host name a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:30:19Z"
    - latency: 4.940289ms
      message: 'load-balancer-api-internal: tcp connection to a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:29:19Z"
    - latency: 8.528539ms
      message: 'load-balancer-api-internal: resolved host name a705e04e7d8884b18b3c90aca5415bd7-e31311aa83d91b66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:29:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-139-to-network-check-target-ip-10-0-138-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-139.ec2.internal
      uid: bf7a88c5-581d-461f-bbf5-d43a2d7aeb00
    resourceVersion: "11850"
    uid: a0cc1256-b2eb-4fd4-8063-64f76c243a99
  spec:
    sourcePod: network-check-source-7d88cb55d8-q998z
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-139-to-network-check-target-ip-10-0-139-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-139.ec2.internal
      uid: bf7a88c5-581d-461f-bbf5-d43a2d7aeb00
    resourceVersion: "11853"
    uid: fee52183-2013-4c3d-b989-396577130631
  spec:
    sourcePod: network-check-source-7d88cb55d8-q998z
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-139-to-network-check-target-ip-10-0-141-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-139.ec2.internal
      uid: bf7a88c5-581d-461f-bbf5-d43a2d7aeb00
    resourceVersion: "11852"
    uid: a74bba01-76a6-4fe8-8f7b-f977fd52e69f
  spec:
    sourcePod: network-check-source-7d88cb55d8-q998z
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-139.ec2.internal
      uid: bf7a88c5-581d-461f-bbf5-d43a2d7aeb00
    resourceVersion: "15456"
    uid: 55ad5229-38a4-48c0-9a15-16b491dafc46
  spec:
    sourcePod: network-check-source-7d88cb55d8-q998z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:33:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.496µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:33:19Z"
    - latency: 1.618364ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:33:19Z"
    - latency: 1.114097ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:32:19Z"
    - latency: 2.036903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:32:19Z"
    - latency: 818.818µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:31:19Z"
    - latency: 2.060141ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:31:19Z"
    - latency: 824.516µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:30:19Z"
    - latency: 2.062037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:30:19Z"
    - latency: 842.521µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T10:29:19Z"
    - latency: 1.856024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T10:29:19Z"
kind: List
metadata:
  resourceVersion: ""