apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:00:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-204.ec2.internal
      uid: 63e3499f-1300-468f-9d74-552934a242b1
    resourceVersion: "15851"
    uid: 395114d7-d3c5-4fa5-a3fe-675fc089402b
  spec:
    sourcePod: network-check-source-7d88cb55d8-784x5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:07:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.035748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:07:30Z"
    - latency: 1.004246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:06:30Z"
    - latency: 1.406844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:05:30Z"
    - latency: 851.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:04:30Z"
    - latency: 1.155677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:03:30Z"
    - latency: 1.011973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:02:30Z"
    - latency: 1.622583ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:01:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:00:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-204.ec2.internal
      uid: 63e3499f-1300-468f-9d74-552934a242b1
    resourceVersion: "15519"
    uid: c0e36537-8141-417c-b65e-3a0fdcb69a3c
  spec:
    sourcePod: network-check-source-7d88cb55d8-784x5
    targetEndpoint: a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:06:30Z"
      message: 'load-balancer-api-external: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.035935ms
      message: 'load-balancer-api-external: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:06:30Z"
    - latency: 8.410097ms
      message: 'load-balancer-api-external: resolved host name a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:06:30Z"
    - latency: 5.139492ms
      message: 'load-balancer-api-external: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:05:30Z"
    - latency: 8.461551ms
      message: 'load-balancer-api-external: resolved host name a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:05:30Z"
    - latency: 6.571507ms
      message: 'load-balancer-api-external: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:04:30Z"
    - latency: 8.408505ms
      message: 'load-balancer-api-external: resolved host name a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:04:30Z"
    - latency: 5.186499ms
      message: 'load-balancer-api-external: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:03:30Z"
    - latency: 9.620477ms
      message: 'load-balancer-api-external: resolved host name a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:03:30Z"
    - latency: 5.658847ms
      message: 'load-balancer-api-external: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:02:30Z"
    - latency: 9.160798ms
      message: 'load-balancer-api-external: resolved host name a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:02:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:00:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-204.ec2.internal
      uid: 63e3499f-1300-468f-9d74-552934a242b1
    resourceVersion: "15518"
    uid: a3218683-db34-43ab-ad00-00ff72c3aa41
  spec:
    sourcePod: network-check-source-7d88cb55d8-784x5
    targetEndpoint: a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:06:30Z"
      message: 'load-balancer-api-internal: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.019639ms
      message: 'load-balancer-api-internal: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:06:30Z"
    - latency: 8.384647ms
      message: 'load-balancer-api-internal: resolved host name a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:06:30Z"
    - latency: 5.664453ms
      message: 'load-balancer-api-internal: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:05:30Z"
    - latency: 8.402039ms
      message: 'load-balancer-api-internal: resolved host name a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:05:30Z"
    - latency: 6.282719ms
      message: 'load-balancer-api-internal: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:04:30Z"
    - latency: 8.485003ms
      message: 'load-balancer-api-internal: resolved host name a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:04:30Z"
    - latency: 5.17767ms
      message: 'load-balancer-api-internal: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:03:30Z"
    - latency: 9.50711ms
      message: 'load-balancer-api-internal: resolved host name a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:03:30Z"
    - latency: 4.704274ms
      message: 'load-balancer-api-internal: tcp connection to a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:02:30Z"
    - latency: 9.276845ms
      message: 'load-balancer-api-internal: resolved host name a0a04fb9c8cab442f804037a4d21e399-a6156787d1d06227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:02:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:00:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-204-to-network-check-target-ip-10-0-128-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-204.ec2.internal
      uid: 63e3499f-1300-468f-9d74-552934a242b1
    resourceVersion: "15848"
    uid: ee6ac3aa-ece1-4db7-a91b-397ee71fb27d
  spec:
    sourcePod: network-check-source-7d88cb55d8-784x5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:07:30Z"
      message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.355µs
      message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:07:30Z"
    - latency: 1.444948ms
      message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:06:30Z"
    - latency: 1.235701ms
      message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:05:30Z"
    - latency: 918.282µs
      message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:04:30Z"
    - latency: 910.253µs
      message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:03:30Z"
    - latency: 994.548µs
      message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:02:30Z"
    - latency: 2.161222ms
      message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:01:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:00:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-204-to-network-check-target-ip-10-0-138-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-204.ec2.internal
      uid: 63e3499f-1300-468f-9d74-552934a242b1
    resourceVersion: "15849"
    uid: d7010c3b-11d0-48b1-98e1-a42db808f0c9
  spec:
    sourcePod: network-check-source-7d88cb55d8-784x5
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:07:30Z"
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.378233ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:07:30Z"
    - latency: 2.469045ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:06:30Z"
    - latency: 2.149917ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:05:30Z"
    - latency: 2.499166ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:04:30Z"
    - latency: 2.470407ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:03:30Z"
    - latency: 2.240967ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:02:30Z"
    - latency: 3.23829ms
      message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:01:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:00:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-204-to-network-check-target-ip-10-0-142-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-204.ec2.internal
      uid: 63e3499f-1300-468f-9d74-552934a242b1
    resourceVersion: "15850"
    uid: 99b450d0-2cd9-448c-9785-4faa1f19cec4
  spec:
    sourcePod: network-check-source-7d88cb55d8-784x5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:07:30Z"
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.470933ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:07:30Z"
    - latency: 2.802577ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:06:30Z"
    - latency: 2.7599ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:05:30Z"
    - latency: 2.35884ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:04:30Z"
    - latency: 2.370468ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:03:30Z"
    - latency: 2.313777ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:02:30Z"
    - latency: 2.551268ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:01:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:00:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-204.ec2.internal
      uid: 63e3499f-1300-468f-9d74-552934a242b1
    resourceVersion: "15517"
    uid: 75ad3e92-b8f5-4af1-99ea-c994e532c279
  spec:
    sourcePod: network-check-source-7d88cb55d8-784x5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:06:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.181399ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:06:30Z"
    - latency: 1.774708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:06:30Z"
    - latency: 919.845µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:05:30Z"
    - latency: 1.77369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:05:30Z"
    - latency: 983.485µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:04:30Z"
    - latency: 2.054285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:04:30Z"
    - latency: 1.188987ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:03:30Z"
    - latency: 1.902746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:03:30Z"
    - latency: 1.157203ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:02:30Z"
    - latency: 1.699326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:02:30Z"
kind: List
metadata:
  resourceVersion: ""