apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:03:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-178-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-178.ec2.internal
      uid: 9cf6c842-94ba-4cc0-b7fc-3543536eda10
    resourceVersion: "13979"
    uid: 72f4c199-63ac-4402-b003-21581f10d241
  spec:
    sourcePod: network-check-source-7d88cb55d8-hbcj4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:10:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.908µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:10:51Z"
    - latency: 909.729µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:09:51Z"
    - latency: 969.292µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:51Z"
    - latency: 929.008µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:51Z"
    - latency: 1.026579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:51Z"
    - latency: 1.257794ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:51Z"
    - latency: 1.309055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:03:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-178-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-178.ec2.internal
      uid: 9cf6c842-94ba-4cc0-b7fc-3543536eda10
    resourceVersion: "15715"
    uid: 00e9c3de-507e-4694-a255-6cb9ee4a9dd2
  spec:
    sourcePod: network-check-source-7d88cb55d8-hbcj4
    targetEndpoint: a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:09:51Z"
      message: 'load-balancer-api-external: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.533055ms
      message: 'load-balancer-api-external: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:15:51Z"
    - latency: 6.562512ms
      message: 'load-balancer-api-external: resolved host name a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:15:51Z"
    - latency: 4.505133ms
      message: 'load-balancer-api-external: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:14:51Z"
    - latency: 7.868293ms
      message: 'load-balancer-api-external: resolved host name a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:14:51Z"
    - latency: 6.277105ms
      message: 'load-balancer-api-external: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:13:51Z"
    - latency: 6.425461ms
      message: 'load-balancer-api-external: resolved host name a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:13:51Z"
    - latency: 6.092404ms
      message: 'load-balancer-api-external: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:12:51Z"
    - latency: 8.096943ms
      message: 'load-balancer-api-external: resolved host name a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:12:51Z"
    - latency: 6.376877ms
      message: 'load-balancer-api-external: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:11:51Z"
    - latency: 7.207564ms
      message: 'load-balancer-api-external: resolved host name a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:11:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:03:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-178-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-178.ec2.internal
      uid: 9cf6c842-94ba-4cc0-b7fc-3543536eda10
    resourceVersion: "15716"
    uid: bb8f0dc8-8d0d-43ef-b688-f9b0f551f6e8
  spec:
    sourcePod: network-check-source-7d88cb55d8-hbcj4
    targetEndpoint: a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:09:51Z"
      message: 'load-balancer-api-internal: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.214374ms
      message: 'load-balancer-api-internal: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:15:51Z"
    - latency: 6.654378ms
      message: 'load-balancer-api-internal: resolved host name a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:15:51Z"
    - latency: 4.457135ms
      message: 'load-balancer-api-internal: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:14:51Z"
    - latency: 7.904458ms
      message: 'load-balancer-api-internal: resolved host name a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:14:51Z"
    - latency: 6.286291ms
      message: 'load-balancer-api-internal: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:13:51Z"
    - latency: 6.533471ms
      message: 'load-balancer-api-internal: resolved host name a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:13:51Z"
    - latency: 6.174716ms
      message: 'load-balancer-api-internal: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:12:51Z"
    - latency: 8.063832ms
      message: 'load-balancer-api-internal: resolved host name a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:12:51Z"
    - latency: 6.258243ms
      message: 'load-balancer-api-internal: tcp connection to a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:11:51Z"
    - latency: 7.366106ms
      message: 'load-balancer-api-internal: resolved host name a0480abfad3384507a92589d67169e80-04ffeaccd60c4df5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:11:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:03:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-178-to-network-check-target-ip-10-0-130-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-178.ec2.internal
      uid: 9cf6c842-94ba-4cc0-b7fc-3543536eda10
    resourceVersion: "13976"
    uid: f0b7a012-ed82-4db3-8201-df1e9e085058
  spec:
    sourcePod: network-check-source-7d88cb55d8-hbcj4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:10:51Z"
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.344µs
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:10:51Z"
    - latency: 783.808µs
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:09:51Z"
    - latency: 973.386µs
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:51Z"
    - latency: 988.994µs
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:51Z"
    - latency: 978.946µs
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:51Z"
    - latency: 1.032705ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:51Z"
    - latency: 1.719928ms
      message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:03:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-178-to-network-check-target-ip-10-0-134-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-178.ec2.internal
      uid: 9cf6c842-94ba-4cc0-b7fc-3543536eda10
    resourceVersion: "13977"
    uid: fbfcf55f-8111-4c0a-b4a6-73fc59ebfae1
  spec:
    sourcePod: network-check-source-7d88cb55d8-hbcj4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:10:51Z"
      message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.916844ms
      message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:10:51Z"
    - latency: 1.709421ms
      message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:09:51Z"
    - latency: 1.875693ms
      message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:51Z"
    - latency: 1.809136ms
      message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:51Z"
    - latency: 1.910708ms
      message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:51Z"
    - latency: 1.969835ms
      message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:51Z"
    - latency: 2.549784ms
      message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:03:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-178-to-network-check-target-ip-10-0-139-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-178.ec2.internal
      uid: 9cf6c842-94ba-4cc0-b7fc-3543536eda10
    resourceVersion: "13978"
    uid: 0485402c-9dff-44ce-84e8-29450c0ca4e9
  spec:
    sourcePod: network-check-source-7d88cb55d8-hbcj4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:10:51Z"
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.224961ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:10:51Z"
    - latency: 2.231637ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:09:51Z"
    - latency: 2.254388ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:51Z"
    - latency: 2.278997ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:51Z"
    - latency: 1.843373ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:51Z"
    - latency: 2.309539ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:51Z"
    - latency: 2.578101ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:03:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-178-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-178.ec2.internal
      uid: 9cf6c842-94ba-4cc0-b7fc-3543536eda10
    resourceVersion: "15714"
    uid: a0e70a6b-174b-4c28-8487-a6fb2edfb9d4
  spec:
    sourcePod: network-check-source-7d88cb55d8-hbcj4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:09:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.02982ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:15:51Z"
    - latency: 1.659804ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:15:51Z"
    - latency: 978.34µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:14:51Z"
    - latency: 1.823094ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:14:51Z"
    - latency: 957.5µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:13:51Z"
    - latency: 1.650396ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:13:51Z"
    - latency: 832.729µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:12:51Z"
    - latency: 2.227355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:12:51Z"
    - latency: 848.354µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:11:51Z"
    - latency: 1.939105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:11:51Z"
kind: List
metadata:
  resourceVersion: ""