apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: af2e0bee-3522-4491-8780-ee75a5347547
    resourceVersion: "11329"
    uid: 6ce9c62f-50dd-44ad-8e6b-0ffb9eae1850
  spec:
    sourcePod: network-check-source-dbd9cf844-8nxwr
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: af2e0bee-3522-4491-8780-ee75a5347547
    resourceVersion: "14709"
    uid: dcdde2ed-7408-492f-857b-1f805fb44e2a
  spec:
    sourcePod: network-check-source-dbd9cf844-8nxwr
    targetEndpoint: ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:12:11Z"
      message: 'load-balancer-api-external: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.178938ms
      message: 'load-balancer-api-external: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:12:11Z"
    - latency: 7.703723ms
      message: 'load-balancer-api-external: resolved host name ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:12:11Z"
    - latency: 4.799774ms
      message: 'load-balancer-api-external: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:11:11Z"
    - latency: 9.066649ms
      message: 'load-balancer-api-external: resolved host name ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:11:11Z"
    - latency: 5.9995ms
      message: 'load-balancer-api-external: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:10:11Z"
    - latency: 8.277952ms
      message: 'load-balancer-api-external: resolved host name ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:10:11Z"
    - latency: 6.089944ms
      message: 'load-balancer-api-external: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:09:11Z"
    - latency: 8.711186ms
      message: 'load-balancer-api-external: resolved host name ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:09:11Z"
    - latency: 5.362319ms
      message: 'load-balancer-api-external: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:08:11Z"
    - latency: 8.118815ms
      message: 'load-balancer-api-external: resolved host name ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:08:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: af2e0bee-3522-4491-8780-ee75a5347547
    resourceVersion: "14708"
    uid: 116f08a5-df91-401d-a140-943abf163b57
  spec:
    sourcePod: network-check-source-dbd9cf844-8nxwr
    targetEndpoint: ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:12:11Z"
      message: 'load-balancer-api-internal: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.493833ms
      message: 'load-balancer-api-internal: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:12:11Z"
    - latency: 7.762011ms
      message: 'load-balancer-api-internal: resolved host name ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:12:11Z"
    - latency: 5.994112ms
      message: 'load-balancer-api-internal: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:11:11Z"
    - latency: 9.157661ms
      message: 'load-balancer-api-internal: resolved host name ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:11:11Z"
    - latency: 5.992997ms
      message: 'load-balancer-api-internal: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:10:11Z"
    - latency: 8.340119ms
      message: 'load-balancer-api-internal: resolved host name ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:10:11Z"
    - latency: 5.494064ms
      message: 'load-balancer-api-internal: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:09:11Z"
    - latency: 8.772227ms
      message: 'load-balancer-api-internal: resolved host name ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:09:11Z"
    - latency: 5.720674ms
      message: 'load-balancer-api-internal: tcp connection to ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:08:11Z"
    - latency: 8.189872ms
      message: 'load-balancer-api-internal: resolved host name ac9f198c2187d4605ba0bfacf786c7eb-5510a277857462b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:08:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-network-check-target-ip-10-0-130-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: af2e0bee-3522-4491-8780-ee75a5347547
    resourceVersion: "11325"
    uid: 30ad0a7c-dfd3-4572-82e6-f362a69dd0eb
  spec:
    sourcePod: network-check-source-dbd9cf844-8nxwr
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-network-check-target-ip-10-0-137-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: af2e0bee-3522-4491-8780-ee75a5347547
    resourceVersion: "11327"
    uid: 6de7eecb-50ed-4eea-90c5-768d3f296c78
  spec:
    sourcePod: network-check-source-dbd9cf844-8nxwr
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-network-check-target-ip-10-0-138-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: af2e0bee-3522-4491-8780-ee75a5347547
    resourceVersion: "11328"
    uid: c96825a0-5f7b-4c54-b861-e418e6275992
  spec:
    sourcePod: network-check-source-dbd9cf844-8nxwr
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-204.ec2.internal
      uid: af2e0bee-3522-4491-8780-ee75a5347547
    resourceVersion: "14707"
    uid: ab3bd000-70d9-4abc-8f19-6512cecc02c3
  spec:
    sourcePod: network-check-source-dbd9cf844-8nxwr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:12:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 798.091µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:12:11Z"
    - latency: 2.040739ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:12:11Z"
    - latency: 2.022781ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:11:11Z"
    - latency: 1.598777ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:11:11Z"
    - latency: 793.251µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:10:11Z"
    - latency: 1.990023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:10:11Z"
    - latency: 785.141µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:09:11Z"
    - latency: 1.980964ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:09:11Z"
    - latency: 849.722µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:08:11Z"
    - latency: 1.641913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:08:11Z"
kind: List
metadata:
  resourceVersion: ""