apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-7-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-7.ec2.internal
      uid: fa459cad-3285-4ef3-82f8-5773afa68b64
    resourceVersion: "21555"
    uid: 31d4d8e6-0241-413b-b1d8-919a748ee548
  spec:
    sourcePod: network-check-source-6f8b768455-vpbkv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:59:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.211076ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:59:02Z"
    - latency: 1.410663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:58:02Z"
    - latency: 1.012999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:57:02Z"
    - latency: 961.263µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:02Z"
    - latency: 980.733µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:02Z"
    - latency: 1.116158ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:02Z"
    - latency: 1.126205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-7-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-7.ec2.internal
      uid: fa459cad-3285-4ef3-82f8-5773afa68b64
    resourceVersion: "20951"
    uid: 22bf8e2c-a104-4543-9cfd-03e716ba383e
  spec:
    sourcePod: network-check-source-6f8b768455-vpbkv
    targetEndpoint: a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:58:02Z"
      message: 'load-balancer-api-external: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.077488ms
      message: 'load-balancer-api-external: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:58:02Z"
    - latency: 6.671917ms
      message: 'load-balancer-api-external: resolved host name a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:58:02Z"
    - latency: 3.654172ms
      message: 'load-balancer-api-external: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:57:02Z"
    - latency: 7.259585ms
      message: 'load-balancer-api-external: resolved host name a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:57:02Z"
    - latency: 4.053171ms
      message: 'load-balancer-api-external: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:02Z"
    - latency: 6.480946ms
      message: 'load-balancer-api-external: resolved host name a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:56:02Z"
    - latency: 4.742484ms
      message: 'load-balancer-api-external: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:02Z"
    - latency: 7.035901ms
      message: 'load-balancer-api-external: resolved host name a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:55:02Z"
    - latency: 4.11559ms
      message: 'load-balancer-api-external: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:02Z"
    - latency: 6.075811ms
      message: 'load-balancer-api-external: resolved host name a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-7-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-7.ec2.internal
      uid: fa459cad-3285-4ef3-82f8-5773afa68b64
    resourceVersion: "20950"
    uid: da090a1c-9bd8-4bd4-989e-b0f7869cb7ed
  spec:
    sourcePod: network-check-source-6f8b768455-vpbkv
    targetEndpoint: a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:58:02Z"
      message: 'load-balancer-api-internal: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.086412ms
      message: 'load-balancer-api-internal: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:58:02Z"
    - latency: 6.642007ms
      message: 'load-balancer-api-internal: resolved host name a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:58:02Z"
    - latency: 8.92997ms
      message: 'load-balancer-api-internal: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:57:02Z"
    - latency: 7.226531ms
      message: 'load-balancer-api-internal: resolved host name a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:57:02Z"
    - latency: 4.043757ms
      message: 'load-balancer-api-internal: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:02Z"
    - latency: 6.464046ms
      message: 'load-balancer-api-internal: resolved host name a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:56:02Z"
    - latency: 4.777868ms
      message: 'load-balancer-api-internal: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:02Z"
    - latency: 6.997365ms
      message: 'load-balancer-api-internal: resolved host name a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:55:02Z"
    - latency: 4.142365ms
      message: 'load-balancer-api-internal: tcp connection to a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:02Z"
    - latency: 6.05289ms
      message: 'load-balancer-api-internal: resolved host name a08b8bad6824048dcbb41610719272df-fee8bb49815dbfde.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-7-to-network-check-target-ip-10-0-128-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-7.ec2.internal
      uid: fa459cad-3285-4ef3-82f8-5773afa68b64
    resourceVersion: "21552"
    uid: 5536d263-ecdd-41d3-9880-ca5260144994
  spec:
    sourcePod: network-check-source-6f8b768455-vpbkv
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:59:02Z"
      message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 805.607µs
      message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:59:02Z"
    - latency: 1.315941ms
      message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:58:02Z"
    - latency: 961.039µs
      message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:57:02Z"
    - latency: 1.37922ms
      message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:02Z"
    - latency: 1.343233ms
      message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:02Z"
    - latency: 825.391µs
      message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:02Z"
    - latency: 1.210657ms
      message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-7-to-network-check-target-ip-10-0-133-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-7.ec2.internal
      uid: fa459cad-3285-4ef3-82f8-5773afa68b64
    resourceVersion: "21554"
    uid: daa966a7-678c-4686-bc0a-cbac1cce7c8f
  spec:
    sourcePod: network-check-source-6f8b768455-vpbkv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:59:02Z"
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.880227ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:59:02Z"
    - latency: 2.069524ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:58:02Z"
    - latency: 2.033322ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:57:02Z"
    - latency: 2.149506ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:02Z"
    - latency: 1.796254ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:02Z"
    - latency: 1.72876ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:02Z"
    - latency: 1.890112ms
      message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-7-to-network-check-target-ip-10-0-142-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-7.ec2.internal
      uid: fa459cad-3285-4ef3-82f8-5773afa68b64
    resourceVersion: "21553"
    uid: 0432985f-b332-454f-afd8-c3172478a437
  spec:
    sourcePod: network-check-source-6f8b768455-vpbkv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:59:02Z"
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.922561ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:59:02Z"
    - latency: 2.197557ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:58:02Z"
    - latency: 2.328016ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:57:02Z"
    - latency: 1.869363ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:02Z"
    - latency: 2.099384ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:02Z"
    - latency: 2.064684ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:02Z"
    - latency: 2.335081ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-7-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-7.ec2.internal
      uid: fa459cad-3285-4ef3-82f8-5773afa68b64
    resourceVersion: "20949"
    uid: 623a682b-6a61-453a-aea0-a582ab92c6b1
  spec:
    sourcePod: network-check-source-6f8b768455-vpbkv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:58:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.215µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:58:02Z"
    - latency: 1.727747ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:58:02Z"
    - latency: 808.18µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:57:02Z"
    - latency: 2.422862ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:57:02Z"
    - latency: 853.965µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:02Z"
    - latency: 1.619268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:56:02Z"
    - latency: 1.079149ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:02Z"
    - latency: 1.840889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:55:02Z"
    - latency: 836.28µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:02Z"
    - latency: 1.775537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:02Z"
kind: List
metadata:
  resourceVersion: ""