apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T07:33:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: b49f7131-3412-4ee2-9cac-4338fd5f460f
    resourceVersion: "10827"
    uid: 099aeafc-9d16-4662-8370-ffcd1e2d8da1
  spec:
    sourcePod: network-check-source-56d84b9f44-glbs6
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T07:33:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: b49f7131-3412-4ee2-9cac-4338fd5f460f
    resourceVersion: "14283"
    uid: fb9ba004-32de-4936-b796-9981a30bf5f1
  spec:
    sourcePod: network-check-source-56d84b9f44-glbs6
    targetEndpoint: a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T07:39:07Z"
      message: 'load-balancer-api-external: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.476069ms
      message: 'load-balancer-api-external: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:39:07Z"
    - latency: 6.427935ms
      message: 'load-balancer-api-external: resolved host name a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:39:07Z"
    - latency: 3.949109ms
      message: 'load-balancer-api-external: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:38:07Z"
    - latency: 7.233847ms
      message: 'load-balancer-api-external: resolved host name a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:38:07Z"
    - latency: 4.665288ms
      message: 'load-balancer-api-external: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:37:07Z"
    - latency: 6.714081ms
      message: 'load-balancer-api-external: resolved host name a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:37:07Z"
    - latency: 4.915949ms
      message: 'load-balancer-api-external: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:36:07Z"
    - latency: 7.539439ms
      message: 'load-balancer-api-external: resolved host name a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:36:07Z"
    - latency: 5.419528ms
      message: 'load-balancer-api-external: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:35:07Z"
    - latency: 7.613107ms
      message: 'load-balancer-api-external: resolved host name a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:35:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T07:33:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: b49f7131-3412-4ee2-9cac-4338fd5f460f
    resourceVersion: "14284"
    uid: 0e322180-d5b0-415f-8bab-200d654d3f66
  spec:
    sourcePod: network-check-source-56d84b9f44-glbs6
    targetEndpoint: a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T07:39:07Z"
      message: 'load-balancer-api-internal: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.543316ms
      message: 'load-balancer-api-internal: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:39:07Z"
    - latency: 6.395615ms
      message: 'load-balancer-api-internal: resolved host name a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:39:07Z"
    - latency: 4.620436ms
      message: 'load-balancer-api-internal: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:38:07Z"
    - latency: 7.243223ms
      message: 'load-balancer-api-internal: resolved host name a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:38:07Z"
    - latency: 4.704798ms
      message: 'load-balancer-api-internal: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:37:07Z"
    - latency: 6.696839ms
      message: 'load-balancer-api-internal: resolved host name a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:37:07Z"
    - latency: 4.950162ms
      message: 'load-balancer-api-internal: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:36:07Z"
    - latency: 7.567947ms
      message: 'load-balancer-api-internal: resolved host name a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:36:07Z"
    - latency: 5.358743ms
      message: 'load-balancer-api-internal: tcp connection to a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:35:07Z"
    - latency: 7.677536ms
      message: 'load-balancer-api-internal: resolved host name a9e9c70f89fb44eb191a13d2c43a1f37-be83243453098983.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:35:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T07:33:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-network-check-target-ip-10-0-131-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: b49f7131-3412-4ee2-9cac-4338fd5f460f
    resourceVersion: "10826"
    uid: e5423290-cfd0-45c2-a1fe-13a305aef77b
  spec:
    sourcePod: network-check-source-56d84b9f44-glbs6
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T07:33:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-network-check-target-ip-10-0-136-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: b49f7131-3412-4ee2-9cac-4338fd5f460f
    resourceVersion: "10824"
    uid: ac32e01d-e4ab-419d-9c81-860dca352c64
  spec:
    sourcePod: network-check-source-56d84b9f44-glbs6
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T07:33:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-network-check-target-ip-10-0-137-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: b49f7131-3412-4ee2-9cac-4338fd5f460f
    resourceVersion: "10823"
    uid: 14324b24-a2ac-47ea-950d-9e96d9c216f2
  spec:
    sourcePod: network-check-source-56d84b9f44-glbs6
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T07:33:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-193-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-193.ec2.internal
      uid: b49f7131-3412-4ee2-9cac-4338fd5f460f
    resourceVersion: "14282"
    uid: 5fe94213-c64f-44cf-8d60-6d906ef07dbd
  spec:
    sourcePod: network-check-source-56d84b9f44-glbs6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T07:39:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 725.669µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:39:07Z"
    - latency: 1.436217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:39:07Z"
    - latency: 806.656µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:38:07Z"
    - latency: 2.080529ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:38:07Z"
    - latency: 762.253µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:37:07Z"
    - latency: 1.619838ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:37:07Z"
    - latency: 725.844µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:36:07Z"
    - latency: 1.460063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:36:07Z"
    - latency: 1.086651ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T07:35:07Z"
    - latency: 2.38705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T07:35:07Z"
kind: List
metadata:
  resourceVersion: ""