apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: febae85b-baf5-4544-9941-62e63fc91aac
    resourceVersion: "10654"
    uid: 573ab97b-0a55-4b1f-bd9a-badf4e006937
  spec:
    sourcePod: network-check-source-6f8b768455-jctnx
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: febae85b-baf5-4544-9941-62e63fc91aac
    resourceVersion: "14328"
    uid: 953ac3a6-48e1-4139-8c2f-83b5e1988fd8
  spec:
    sourcePod: network-check-source-6f8b768455-jctnx
    targetEndpoint: ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:51:05Z"
      message: 'load-balancer-api-external: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.333391ms
      message: 'load-balancer-api-external: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:05Z"
    - latency: 7.134427ms
      message: 'load-balancer-api-external: resolved host name ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:51:05Z"
    - latency: 5.064443ms
      message: 'load-balancer-api-external: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:50:05Z"
    - latency: 7.534553ms
      message: 'load-balancer-api-external: resolved host name ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:50:05Z"
    - latency: 7.280937ms
      message: 'load-balancer-api-external: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:49:05Z"
    - latency: 8.203878ms
      message: 'load-balancer-api-external: resolved host name ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:49:05Z"
    - latency: 4.95066ms
      message: 'load-balancer-api-external: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:48:05Z"
    - latency: 7.007448ms
      message: 'load-balancer-api-external: resolved host name ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:48:05Z"
    - latency: 5.451515ms
      message: 'load-balancer-api-external: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:47:05Z"
    - latency: 7.28642ms
      message: 'load-balancer-api-external: resolved host name ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:47:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: febae85b-baf5-4544-9941-62e63fc91aac
    resourceVersion: "14327"
    uid: d4160082-b5a1-45f2-a455-98db90632504
  spec:
    sourcePod: network-check-source-6f8b768455-jctnx
    targetEndpoint: ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:51:05Z"
      message: 'load-balancer-api-internal: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.119842ms
      message: 'load-balancer-api-internal: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:05Z"
    - latency: 7.266974ms
      message: 'load-balancer-api-internal: resolved host name ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:51:05Z"
    - latency: 5.068178ms
      message: 'load-balancer-api-internal: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:50:05Z"
    - latency: 7.615699ms
      message: 'load-balancer-api-internal: resolved host name ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:50:05Z"
    - latency: 5.399199ms
      message: 'load-balancer-api-internal: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:49:05Z"
    - latency: 8.311456ms
      message: 'load-balancer-api-internal: resolved host name ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:49:05Z"
    - latency: 4.910195ms
      message: 'load-balancer-api-internal: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:48:05Z"
    - latency: 7.140747ms
      message: 'load-balancer-api-internal: resolved host name ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:48:05Z"
    - latency: 5.439246ms
      message: 'load-balancer-api-internal: tcp connection to ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:47:05Z"
    - latency: 7.411229ms
      message: 'load-balancer-api-internal: resolved host name ab50471be0c9448238993e7f6f71ffba-4664cc82c36336fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:47:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:45:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-network-check-target-ip-10-0-130-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: febae85b-baf5-4544-9941-62e63fc91aac
    resourceVersion: "10659"
    uid: 99549eec-f5ba-428a-a1c5-6f06045872cb
  spec:
    sourcePod: network-check-source-6f8b768455-jctnx
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:45:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-network-check-target-ip-10-0-132-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: febae85b-baf5-4544-9941-62e63fc91aac
    resourceVersion: "10660"
    uid: c7d15ede-6b35-45b7-a08f-a6b38d20fbe8
  spec:
    sourcePod: network-check-source-6f8b768455-jctnx
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:45:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-network-check-target-ip-10-0-142-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: febae85b-baf5-4544-9941-62e63fc91aac
    resourceVersion: "10661"
    uid: 852b8c87-064f-407f-b96d-c00b5ea83532
  spec:
    sourcePod: network-check-source-6f8b768455-jctnx
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:45:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: febae85b-baf5-4544-9941-62e63fc91aac
    resourceVersion: "14326"
    uid: 47143ed3-6085-4366-881e-cd2555691b31
  spec:
    sourcePod: network-check-source-6f8b768455-jctnx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:51:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 758.72µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:05Z"
    - latency: 1.647585ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:51:05Z"
    - latency: 858.375µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:50:05Z"
    - latency: 2.03521ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:50:05Z"
    - latency: 866.996µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:49:05Z"
    - latency: 2.118356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:49:05Z"
    - latency: 957.569µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:48:05Z"
    - latency: 1.918713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:48:05Z"
    - latency: 825.129µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:47:05Z"
    - latency: 1.554473ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:47:05Z"
kind: List
metadata:
  resourceVersion: ""