apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:26:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-212-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-212.ec2.internal
      uid: 9a0edbe2-a068-4561-84a3-2f76374e8811
    resourceVersion: "15684"
    uid: 2f6fefa5-3a5a-4565-a020-ebf8581352cf
  spec:
    sourcePod: network-check-source-685456655f-gwd7f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:33:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.434µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:33:41Z"
    - latency: 1.367817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:32:41Z"
    - latency: 884.206µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:31:41Z"
    - latency: 1.019591ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:30:41Z"
    - latency: 1.32767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:29:41Z"
    - latency: 1.043562ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:28:41Z"
    - latency: 940.936µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:27:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:26:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-212-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-212.ec2.internal
      uid: 9a0edbe2-a068-4561-84a3-2f76374e8811
    resourceVersion: "15205"
    uid: e1b68ae8-e280-4ba3-a645-68412aa69f9a
  spec:
    sourcePod: network-check-source-685456655f-gwd7f
    targetEndpoint: a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:32:41Z"
      message: 'load-balancer-api-external: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.955636ms
      message: 'load-balancer-api-external: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:32:41Z"
    - latency: 8.678548ms
      message: 'load-balancer-api-external: resolved host name a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:32:41Z"
    - latency: 4.458189ms
      message: 'load-balancer-api-external: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:31:41Z"
    - latency: 7.981695ms
      message: 'load-balancer-api-external: resolved host name a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:31:41Z"
    - latency: 4.367581ms
      message: 'load-balancer-api-external: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:30:41Z"
    - latency: 8.614779ms
      message: 'load-balancer-api-external: resolved host name a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:30:41Z"
    - latency: 5.511672ms
      message: 'load-balancer-api-external: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:29:41Z"
    - latency: 7.614719ms
      message: 'load-balancer-api-external: resolved host name a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:29:41Z"
    - latency: 4.662114ms
      message: 'load-balancer-api-external: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:28:41Z"
    - latency: 12.086831ms
      message: 'load-balancer-api-external: resolved host name a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:28:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:26:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-212-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-212.ec2.internal
      uid: 9a0edbe2-a068-4561-84a3-2f76374e8811
    resourceVersion: "15206"
    uid: 0949cbf1-6a2e-4198-970a-110d19e9d0a8
  spec:
    sourcePod: network-check-source-685456655f-gwd7f
    targetEndpoint: a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:32:41Z"
      message: 'load-balancer-api-internal: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.94659ms
      message: 'load-balancer-api-internal: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:32:41Z"
    - latency: 8.742737ms
      message: 'load-balancer-api-internal: resolved host name a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:32:41Z"
    - latency: 4.181689ms
      message: 'load-balancer-api-internal: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:31:41Z"
    - latency: 7.863308ms
      message: 'load-balancer-api-internal: resolved host name a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:31:41Z"
    - latency: 4.359862ms
      message: 'load-balancer-api-internal: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:30:41Z"
    - latency: 8.656905ms
      message: 'load-balancer-api-internal: resolved host name a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:30:41Z"
    - latency: 5.461042ms
      message: 'load-balancer-api-internal: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:29:41Z"
    - latency: 7.601547ms
      message: 'load-balancer-api-internal: resolved host name a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:29:41Z"
    - latency: 4.64481ms
      message: 'load-balancer-api-internal: tcp connection to a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:28:41Z"
    - latency: 12.161605ms
      message: 'load-balancer-api-internal: resolved host name a89bc7def16f94a4c8517bf9de5259e2-652914e646fd23f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:28:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:26:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-212-to-network-check-target-ip-10-0-130-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-212.ec2.internal
      uid: 9a0edbe2-a068-4561-84a3-2f76374e8811
    resourceVersion: "15681"
    uid: c67a39ff-0d2e-4292-818e-e8890546e445
  spec:
    sourcePod: network-check-source-685456655f-gwd7f
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:33:41Z"
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.321712ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:33:41Z"
    - latency: 1.498598ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:32:41Z"
    - latency: 956.258µs
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:31:41Z"
    - latency: 949.645µs
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:30:41Z"
    - latency: 1.504894ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:29:41Z"
    - latency: 1.510594ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:28:41Z"
    - latency: 1.565185ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:27:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:26:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-212-to-network-check-target-ip-10-0-135-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-212.ec2.internal
      uid: 9a0edbe2-a068-4561-84a3-2f76374e8811
    resourceVersion: "15683"
    uid: 7796acd9-f26a-4ac9-9ab9-b676153132d6
  spec:
    sourcePod: network-check-source-685456655f-gwd7f
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:33:41Z"
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.239193ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:33:41Z"
    - latency: 2.744795ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:32:41Z"
    - latency: 2.484905ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:31:41Z"
    - latency: 2.360935ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:30:41Z"
    - latency: 2.667104ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:29:41Z"
    - latency: 2.442802ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:28:41Z"
    - latency: 2.303037ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:27:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:26:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-212-to-network-check-target-ip-10-0-141-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-212.ec2.internal
      uid: 9a0edbe2-a068-4561-84a3-2f76374e8811
    resourceVersion: "15682"
    uid: 2201f25a-be8d-4f6b-b510-95422f2f59a7
  spec:
    sourcePod: network-check-source-685456655f-gwd7f
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:33:41Z"
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.452317ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:33:41Z"
    - latency: 2.231131ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:32:41Z"
    - latency: 2.391508ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:31:41Z"
    - latency: 2.139082ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:30:41Z"
    - latency: 2.168724ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:29:41Z"
    - latency: 2.300082ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:28:41Z"
    - latency: 2.443581ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:27:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:26:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-212-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-212.ec2.internal
      uid: 9a0edbe2-a068-4561-84a3-2f76374e8811
    resourceVersion: "15204"
    uid: 79489b1e-3624-49cc-941f-d4811c5b9a99
  spec:
    sourcePod: network-check-source-685456655f-gwd7f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:32:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.777µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:32:41Z"
    - latency: 1.899642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:32:41Z"
    - latency: 862.592µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:31:41Z"
    - latency: 1.838283ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:31:41Z"
    - latency: 784.709µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:30:41Z"
    - latency: 1.789078ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:30:41Z"
    - latency: 858.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:29:41Z"
    - latency: 1.907127ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:29:41Z"
    - latency: 1.087943ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:28:41Z"
    - latency: 1.780517ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:28:41Z"
kind: List
metadata:
  resourceVersion: ""