apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:58:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-102.ec2.internal
      uid: 2f52ce9a-f3dd-4601-93c3-4644c556e956
    resourceVersion: "12114"
    uid: 66e3c6c4-56b0-4c81-b6e7-1ef6f1f1b614
  spec:
    sourcePod: network-check-source-7d88cb55d8-k9sp6
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:58:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-102.ec2.internal
      uid: 2f52ce9a-f3dd-4601-93c3-4644c556e956
    resourceVersion: "15831"
    uid: ed3e5050-b088-4fb0-913b-9851d5225561
  spec:
    sourcePod: network-check-source-7d88cb55d8-k9sp6
    targetEndpoint: af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T07:04:51Z"
      message: 'load-balancer-api-external: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.700614ms
      message: 'load-balancer-api-external: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:04:51Z"
    - latency: 11.958613ms
      message: 'load-balancer-api-external: resolved host name af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:04:51Z"
    - latency: 5.089737ms
      message: 'load-balancer-api-external: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:03:51Z"
    - latency: 9.066442ms
      message: 'load-balancer-api-external: resolved host name af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:03:51Z"
    - latency: 5.157374ms
      message: 'load-balancer-api-external: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:02:51Z"
    - latency: 21.383555ms
      message: 'load-balancer-api-external: resolved host name af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:02:51Z"
    - latency: 4.196591ms
      message: 'load-balancer-api-external: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:01:51Z"
    - latency: 9.513186ms
      message: 'load-balancer-api-external: resolved host name af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:01:51Z"
    - latency: 5.569743ms
      message: 'load-balancer-api-external: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:00:51Z"
    - latency: 8.833097ms
      message: 'load-balancer-api-external: resolved host name af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:00:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:58:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-102.ec2.internal
      uid: 2f52ce9a-f3dd-4601-93c3-4644c556e956
    resourceVersion: "15832"
    uid: c397bc42-ff27-484b-ae6a-de97311041b2
  spec:
    sourcePod: network-check-source-7d88cb55d8-k9sp6
    targetEndpoint: af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T07:04:51Z"
      message: 'load-balancer-api-internal: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.438798ms
      message: 'load-balancer-api-internal: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:04:51Z"
    - latency: 11.88569ms
      message: 'load-balancer-api-internal: resolved host name af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:04:51Z"
    - latency: 5.062402ms
      message: 'load-balancer-api-internal: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:03:51Z"
    - latency: 9.328364ms
      message: 'load-balancer-api-internal: resolved host name af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:03:51Z"
    - latency: 5.178296ms
      message: 'load-balancer-api-internal: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:02:51Z"
    - latency: 20.815641ms
      message: 'load-balancer-api-internal: resolved host name af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:02:51Z"
    - latency: 4.829583ms
      message: 'load-balancer-api-internal: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:01:51Z"
    - latency: 9.486402ms
      message: 'load-balancer-api-internal: resolved host name af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:01:51Z"
    - latency: 5.564925ms
      message: 'load-balancer-api-internal: tcp connection to af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:00:51Z"
    - latency: 8.854752ms
      message: 'load-balancer-api-internal: resolved host name af50aebea485242018b2194cc1acfcf3-fae1706c77f8c011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:00:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:58:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-102-to-network-check-target-ip-10-0-133-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-102.ec2.internal
      uid: 2f52ce9a-f3dd-4601-93c3-4644c556e956
    resourceVersion: "12113"
    uid: bdd1292b-a078-4be8-8020-0595fb6f1649
  spec:
    sourcePod: network-check-source-7d88cb55d8-k9sp6
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:58:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-102-to-network-check-target-ip-10-0-138-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-102.ec2.internal
      uid: 2f52ce9a-f3dd-4601-93c3-4644c556e956
    resourceVersion: "12111"
    uid: 96a41c91-02f7-4f0c-9009-0b3bbdadcf22
  spec:
    sourcePod: network-check-source-7d88cb55d8-k9sp6
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:58:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-102-to-network-check-target-ip-10-0-138-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-102.ec2.internal
      uid: 2f52ce9a-f3dd-4601-93c3-4644c556e956
    resourceVersion: "12112"
    uid: 3b92a2fa-3db7-4124-bae8-1da844ff5251
  spec:
    sourcePod: network-check-source-7d88cb55d8-k9sp6
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:58:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-102.ec2.internal
      uid: 2f52ce9a-f3dd-4601-93c3-4644c556e956
    resourceVersion: "15830"
    uid: 3b70ce54-1ca0-4bda-ab7b-6e4b1c6f317f
  spec:
    sourcePod: network-check-source-7d88cb55d8-k9sp6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T07:04:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.732683ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:04:51Z"
    - latency: 2.368362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:04:51Z"
    - latency: 906.049µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:03:51Z"
    - latency: 1.884316ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:03:51Z"
    - latency: 1.170184ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:02:51Z"
    - latency: 8.558474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:02:51Z"
    - latency: 876.187µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:01:51Z"
    - latency: 1.749674ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:01:51Z"
    - latency: 1.304052ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:00:51Z"
    - latency: 1.92177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:00:51Z"
kind: List
metadata:
  resourceVersion: ""