apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-155-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-155.ec2.internal
      uid: 244ad645-95f2-4d43-be69-bb5c0d9f76a3
    resourceVersion: "14925"
    uid: 8173c1db-2da0-4863-bec7-93dcafc942f3
  spec:
    sourcePod: network-check-source-dbd9cf844-5mp6x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:14:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.034124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:14:56Z"
    - latency: 1.389763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:13:56Z"
    - latency: 986.32µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:12:56Z"
    - latency: 964.7µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:11:56Z"
    - latency: 1.144961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:10:56Z"
    - latency: 1.374296ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:09:56Z"
    - latency: 1.337888ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:08:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-155-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-155.ec2.internal
      uid: 244ad645-95f2-4d43-be69-bb5c0d9f76a3
    resourceVersion: "17123"
    uid: 2898048f-21ce-406e-8092-1fe94d74176c
  spec:
    sourcePod: network-check-source-dbd9cf844-5mp6x
    targetEndpoint: a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:13:56Z"
      message: 'load-balancer-api-external: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.258617ms
      message: 'load-balancer-api-external: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:19:56Z"
    - latency: 6.589768ms
      message: 'load-balancer-api-external: resolved host name a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:19:56Z"
    - latency: 5.271795ms
      message: 'load-balancer-api-external: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:18:56Z"
    - latency: 6.849018ms
      message: 'load-balancer-api-external: resolved host name a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:18:56Z"
    - latency: 6.386787ms
      message: 'load-balancer-api-external: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:17:56Z"
    - latency: 6.900266ms
      message: 'load-balancer-api-external: resolved host name a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:17:56Z"
    - latency: 4.941887ms
      message: 'load-balancer-api-external: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:16:56Z"
    - latency: 6.22462ms
      message: 'load-balancer-api-external: resolved host name a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:16:56Z"
    - latency: 4.642009ms
      message: 'load-balancer-api-external: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:15:56Z"
    - latency: 6.919266ms
      message: 'load-balancer-api-external: resolved host name a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:15:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-155-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-155.ec2.internal
      uid: 244ad645-95f2-4d43-be69-bb5c0d9f76a3
    resourceVersion: "17122"
    uid: 25dd986a-87f7-49f2-bb43-628a40233a80
  spec:
    sourcePod: network-check-source-dbd9cf844-5mp6x
    targetEndpoint: a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:13:56Z"
      message: 'load-balancer-api-internal: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.294673ms
      message: 'load-balancer-api-internal: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:19:56Z"
    - latency: 6.603552ms
      message: 'load-balancer-api-internal: resolved host name a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:19:56Z"
    - latency: 5.227882ms
      message: 'load-balancer-api-internal: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:18:56Z"
    - latency: 6.887999ms
      message: 'load-balancer-api-internal: resolved host name a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:18:56Z"
    - latency: 4.07281ms
      message: 'load-balancer-api-internal: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:17:56Z"
    - latency: 6.867836ms
      message: 'load-balancer-api-internal: resolved host name a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:17:56Z"
    - latency: 4.892785ms
      message: 'load-balancer-api-internal: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:16:56Z"
    - latency: 6.286456ms
      message: 'load-balancer-api-internal: resolved host name a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:16:56Z"
    - latency: 4.009374ms
      message: 'load-balancer-api-internal: tcp connection to a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:15:56Z"
    - latency: 6.909406ms
      message: 'load-balancer-api-internal: resolved host name a16be189717b84a5793505a224cd1665-64e46aff75dada94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:15:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-155-to-network-check-target-ip-10-0-128-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-155.ec2.internal
      uid: 244ad645-95f2-4d43-be69-bb5c0d9f76a3
    resourceVersion: "14924"
    uid: 44ba6450-3b5f-43ba-b7ec-caf2c58d5528
  spec:
    sourcePod: network-check-source-dbd9cf844-5mp6x
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:14:56Z"
      message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.203925ms
      message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:14:56Z"
    - latency: 2.305338ms
      message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:13:56Z"
    - latency: 2.916303ms
      message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:12:56Z"
    - latency: 2.230493ms
      message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:11:56Z"
    - latency: 2.181155ms
      message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:10:56Z"
    - latency: 2.240962ms
      message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:09:56Z"
    - latency: 2.513636ms
      message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:08:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-155-to-network-check-target-ip-10-0-130-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-155.ec2.internal
      uid: 244ad645-95f2-4d43-be69-bb5c0d9f76a3
    resourceVersion: "14922"
    uid: 35f392e6-dc9f-4256-bf32-de2dfd418293
  spec:
    sourcePod: network-check-source-dbd9cf844-5mp6x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:14:56Z"
      message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.555µs
      message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:14:56Z"
    - latency: 943.502µs
      message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:13:56Z"
    - latency: 1.426318ms
      message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:12:56Z"
    - latency: 864.55µs
      message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:11:56Z"
    - latency: 900.599µs
      message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:10:56Z"
    - latency: 881.153µs
      message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:09:56Z"
    - latency: 1.786771ms
      message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:08:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-155-to-network-check-target-ip-10-0-135-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-155.ec2.internal
      uid: 244ad645-95f2-4d43-be69-bb5c0d9f76a3
    resourceVersion: "14923"
    uid: 6ce1ed50-6712-45c0-b57e-1d4c6a61962a
  spec:
    sourcePod: network-check-source-dbd9cf844-5mp6x
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:14:56Z"
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.208392ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:14:56Z"
    - latency: 2.367204ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:13:56Z"
    - latency: 2.928744ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:12:56Z"
    - latency: 2.11787ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:11:56Z"
    - latency: 2.053204ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:10:56Z"
    - latency: 2.154193ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:09:56Z"
    - latency: 2.112671ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:08:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:07:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-155-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-155.ec2.internal
      uid: 244ad645-95f2-4d43-be69-bb5c0d9f76a3
    resourceVersion: "17121"
    uid: 11513363-0f6e-419d-ae47-09870a0eefee
  spec:
    sourcePod: network-check-source-dbd9cf844-5mp6x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:13:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.839µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:19:56Z"
    - latency: 1.784748ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:19:56Z"
    - latency: 894.122µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:18:56Z"
    - latency: 1.836356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:18:56Z"
    - latency: 1.026401ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:17:56Z"
    - latency: 1.695253ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:17:56Z"
    - latency: 1.082599ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:16:56Z"
    - latency: 1.937876ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:16:56Z"
    - latency: 818.664µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:15:56Z"
    - latency: 1.777931ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:15:56Z"
kind: List
metadata:
  resourceVersion: ""