apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-251-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-251.ec2.internal
      uid: a2cb58be-8fff-4f15-ac0f-845e94b5e5c0
    resourceVersion: "10814"
    uid: 152459bd-af1a-44d7-9f45-6c48423a1cce
  spec:
    sourcePod: network-check-source-7d88cb55d8-jq2z2
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-251-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-251.ec2.internal
      uid: a2cb58be-8fff-4f15-ac0f-845e94b5e5c0
    resourceVersion: "14305"
    uid: 25901df4-0e9b-46e9-9cb5-a44043ad2ae2
  spec:
    sourcePod: network-check-source-7d88cb55d8-jq2z2
    targetEndpoint: ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:09:56Z"
      message: 'load-balancer-api-external: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.313057ms
      message: 'load-balancer-api-external: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:09:56Z"
    - latency: 6.628856ms
      message: 'load-balancer-api-external: resolved host name ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:09:56Z"
    - latency: 4.609894ms
      message: 'load-balancer-api-external: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:08:56Z"
    - latency: 7.840384ms
      message: 'load-balancer-api-external: resolved host name ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:08:56Z"
    - latency: 6.778746ms
      message: 'load-balancer-api-external: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:07:56Z"
    - latency: 7.835837ms
      message: 'load-balancer-api-external: resolved host name ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:07:56Z"
    - latency: 5.361703ms
      message: 'load-balancer-api-external: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:06:56Z"
    - latency: 7.163967ms
      message: 'load-balancer-api-external: resolved host name ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:06:56Z"
    - latency: 5.745925ms
      message: 'load-balancer-api-external: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:05:56Z"
    - latency: 6.7745ms
      message: 'load-balancer-api-external: resolved host name ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:05:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-251-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-251.ec2.internal
      uid: a2cb58be-8fff-4f15-ac0f-845e94b5e5c0
    resourceVersion: "14304"
    uid: c4788ee3-273d-4d60-b96b-eaaa3f9b3059
  spec:
    sourcePod: network-check-source-7d88cb55d8-jq2z2
    targetEndpoint: ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:09:56Z"
      message: 'load-balancer-api-internal: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.28312ms
      message: 'load-balancer-api-internal: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:09:56Z"
    - latency: 6.648356ms
      message: 'load-balancer-api-internal: resolved host name ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:09:56Z"
    - latency: 4.641692ms
      message: 'load-balancer-api-internal: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:08:56Z"
    - latency: 7.772838ms
      message: 'load-balancer-api-internal: resolved host name ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:08:56Z"
    - latency: 6.792404ms
      message: 'load-balancer-api-internal: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:07:56Z"
    - latency: 7.759244ms
      message: 'load-balancer-api-internal: resolved host name ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:07:56Z"
    - latency: 5.401802ms
      message: 'load-balancer-api-internal: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:06:56Z"
    - latency: 7.146262ms
      message: 'load-balancer-api-internal: resolved host name ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:06:56Z"
    - latency: 5.802488ms
      message: 'load-balancer-api-internal: tcp connection to ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:05:56Z"
    - latency: 6.855069ms
      message: 'load-balancer-api-internal: resolved host name ac98d2d6e07ec49e2a24d56da782157f-351af9460d0f026a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:05:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-251-to-network-check-target-ip-10-0-140-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-251.ec2.internal
      uid: a2cb58be-8fff-4f15-ac0f-845e94b5e5c0
    resourceVersion: "10819"
    uid: 14014e75-f48c-4b44-a2a0-3fb227ec3d8c
  spec:
    sourcePod: network-check-source-7d88cb55d8-jq2z2
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-251-to-network-check-target-ip-10-0-142-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-251.ec2.internal
      uid: a2cb58be-8fff-4f15-ac0f-845e94b5e5c0
    resourceVersion: "10820"
    uid: 6c5610c5-a854-4961-abbd-136628f77eb8
  spec:
    sourcePod: network-check-source-7d88cb55d8-jq2z2
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-251-to-network-check-target-ip-10-0-143-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-251.ec2.internal
      uid: a2cb58be-8fff-4f15-ac0f-845e94b5e5c0
    resourceVersion: "10821"
    uid: dec201ef-0abf-4bf1-9507-ccb791697912
  spec:
    sourcePod: network-check-source-7d88cb55d8-jq2z2
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:03:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-251-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-251.ec2.internal
      uid: a2cb58be-8fff-4f15-ac0f-845e94b5e5c0
    resourceVersion: "14303"
    uid: 4c9a8f4a-96de-4ac1-8164-e99582f47555
  spec:
    sourcePod: network-check-source-7d88cb55d8-jq2z2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:09:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.240864ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:09:56Z"
    - latency: 1.637698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:09:56Z"
    - latency: 926.815µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:08:56Z"
    - latency: 2.312376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:08:56Z"
    - latency: 1.142776ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:07:56Z"
    - latency: 1.774528ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:07:56Z"
    - latency: 895.178µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:06:56Z"
    - latency: 1.656991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:06:56Z"
    - latency: 833.749µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:05:56Z"
    - latency: 1.813907ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:05:56Z"
kind: List
metadata:
  resourceVersion: ""