apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:04:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-133-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-133.ec2.internal
      uid: c7418153-4f01-4e30-a902-dd399a73dec2
    resourceVersion: "22686"
    uid: 03e28f04-8940-4b49-a102-4f0b80b013b7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8pzsd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T10:11:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.202115ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:11:31Z"
    - latency: 880.613µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:10:31Z"
    - latency: 1.450825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:09:31Z"
    - latency: 1.100518ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:08:31Z"
    - latency: 1.113745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:07:31Z"
    - latency: 740.266µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:06:31Z"
    - latency: 1.053373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:05:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:04:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-133-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-133.ec2.internal
      uid: c7418153-4f01-4e30-a902-dd399a73dec2
    resourceVersion: "21260"
    uid: d6a4b9a0-600b-4165-a7a7-828a833778cf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8pzsd
    targetEndpoint: a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T10:10:31Z"
      message: 'load-balancer-api-external: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.00133ms
      message: 'load-balancer-api-external: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:10:31Z"
    - latency: 6.897482ms
      message: 'load-balancer-api-external: resolved host name a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:10:31Z"
    - latency: 4.892617ms
      message: 'load-balancer-api-external: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:09:31Z"
    - latency: 8.442464ms
      message: 'load-balancer-api-external: resolved host name a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:09:31Z"
    - latency: 4.924932ms
      message: 'load-balancer-api-external: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:08:31Z"
    - latency: 6.826145ms
      message: 'load-balancer-api-external: resolved host name a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:08:31Z"
    - latency: 7.115444ms
      message: 'load-balancer-api-external: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:07:31Z"
    - latency: 7.687632ms
      message: 'load-balancer-api-external: resolved host name a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:07:31Z"
    - latency: 7.5132ms
      message: 'load-balancer-api-external: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:06:31Z"
    - latency: 6.696154ms
      message: 'load-balancer-api-external: resolved host name a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:06:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:04:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-133-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-133.ec2.internal
      uid: c7418153-4f01-4e30-a902-dd399a73dec2
    resourceVersion: "21261"
    uid: af6d564e-d5f4-4b7b-8930-81bf1a096533
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8pzsd
    targetEndpoint: a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T10:10:31Z"
      message: 'load-balancer-api-internal: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.90737ms
      message: 'load-balancer-api-internal: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:10:31Z"
    - latency: 6.921483ms
      message: 'load-balancer-api-internal: resolved host name a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:10:31Z"
    - latency: 4.69708ms
      message: 'load-balancer-api-internal: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:09:31Z"
    - latency: 8.536188ms
      message: 'load-balancer-api-internal: resolved host name a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:09:31Z"
    - latency: 5.106741ms
      message: 'load-balancer-api-internal: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:08:31Z"
    - latency: 6.890058ms
      message: 'load-balancer-api-internal: resolved host name a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:08:31Z"
    - latency: 7.033178ms
      message: 'load-balancer-api-internal: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:07:31Z"
    - latency: 7.723525ms
      message: 'load-balancer-api-internal: resolved host name a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:07:31Z"
    - latency: 5.745237ms
      message: 'load-balancer-api-internal: tcp connection to a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:06:31Z"
    - latency: 6.751972ms
      message: 'load-balancer-api-internal: resolved host name a415892068fe643aab31fee825ae0443-b351ca342e0d063a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:06:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:04:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-133-to-network-check-target-ip-10-0-128-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-133.ec2.internal
      uid: c7418153-4f01-4e30-a902-dd399a73dec2
    resourceVersion: "22683"
    uid: 23ebb676-dbf0-4a97-8777-9c50332bf58e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8pzsd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T10:11:31Z"
      message: 'network-check-target-ip-10-0-128-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.079121ms
      message: 'network-check-target-ip-10-0-128-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:11:31Z"
    - latency: 835.172µs
      message: 'network-check-target-ip-10-0-128-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:10:31Z"
    - latency: 1.885546ms
      message: 'network-check-target-ip-10-0-128-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:09:31Z"
    - latency: 1.42317ms
      message: 'network-check-target-ip-10-0-128-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:08:31Z"
    - latency: 911.206µs
      message: 'network-check-target-ip-10-0-128-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:07:31Z"
    - latency: 738.213µs
      message: 'network-check-target-ip-10-0-128-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:06:31Z"
    - latency: 1.771645ms
      message: 'network-check-target-ip-10-0-128-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:05:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:04:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-133-to-network-check-target-ip-10-0-131-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-133.ec2.internal
      uid: c7418153-4f01-4e30-a902-dd399a73dec2
    resourceVersion: "22684"
    uid: 5291b392-839e-49d3-8152-c2d0da140125
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8pzsd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T10:11:31Z"
      message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.943819ms
      message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:11:31Z"
    - latency: 1.728908ms
      message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:10:31Z"
    - latency: 1.706032ms
      message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:09:31Z"
    - latency: 2.022924ms
      message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:08:31Z"
    - latency: 2.003107ms
      message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:07:31Z"
    - latency: 1.803458ms
      message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:06:31Z"
    - latency: 2.142512ms
      message: 'network-check-target-ip-10-0-131-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:05:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:04:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-133-to-network-check-target-ip-10-0-140-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-133.ec2.internal
      uid: c7418153-4f01-4e30-a902-dd399a73dec2
    resourceVersion: "22685"
    uid: 515b1071-e3d4-45e4-ad81-7baf8323458d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8pzsd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T10:11:31Z"
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.379631ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:11:31Z"
    - latency: 1.865679ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:10:31Z"
    - latency: 2.17264ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:09:31Z"
    - latency: 1.967546ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:08:31Z"
    - latency: 2.151636ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:07:31Z"
    - latency: 2.090262ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:06:31Z"
    - latency: 2.386016ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:05:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T10:04:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-133-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-133.ec2.internal
      uid: c7418153-4f01-4e30-a902-dd399a73dec2
    resourceVersion: "21259"
    uid: db601bdf-a98f-4755-9bd3-b49a6e57a86a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-8pzsd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T10:10:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.66µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:10:31Z"
    - latency: 1.830541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:10:31Z"
    - latency: 967.208µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:09:31Z"
    - latency: 1.724304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:09:31Z"
    - latency: 826.552µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:08:31Z"
    - latency: 1.737901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:08:31Z"
    - latency: 917.115µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:07:31Z"
    - latency: 1.756945ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:07:31Z"
    - latency: 1.144754ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T10:06:31Z"
    - latency: 1.958015ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T10:06:31Z"
kind: List
metadata:
  resourceVersion: ""