apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:01:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 79922ebf-fd22-46d9-8201-d729d5064bf6
    resourceVersion: "14398"
    uid: a03b64ab-f57e-4d32-9bc8-ce12e46b95c2
  spec:
    sourcePod: network-check-source-56d84b9f44-5ctz2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:08:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 862.381µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:08:14Z"
    - latency: 1.655272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:14Z"
    - latency: 952.044µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:14Z"
    - latency: 991.945µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:14Z"
    - latency: 1.020066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:14Z"
    - latency: 1.270203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:14Z"
    - latency: 1.021569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:01:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 79922ebf-fd22-46d9-8201-d729d5064bf6
    resourceVersion: "14067"
    uid: b7fe74a4-8918-4444-8e12-c852af2d7f84
  spec:
    sourcePod: network-check-source-56d84b9f44-5ctz2
    targetEndpoint: a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:07:14Z"
      message: 'load-balancer-api-external: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.530041ms
      message: 'load-balancer-api-external: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:14Z"
    - latency: 11.364291ms
      message: 'load-balancer-api-external: resolved host name a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:07:14Z"
    - latency: 5.214172ms
      message: 'load-balancer-api-external: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:14Z"
    - latency: 7.494243ms
      message: 'load-balancer-api-external: resolved host name a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:06:14Z"
    - latency: 5.046633ms
      message: 'load-balancer-api-external: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:14Z"
    - latency: 6.411718ms
      message: 'load-balancer-api-external: resolved host name a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:05:14Z"
    - latency: 4.396092ms
      message: 'load-balancer-api-external: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:14Z"
    - latency: 10.509686ms
      message: 'load-balancer-api-external: resolved host name a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:04:14Z"
    - latency: 6.72184ms
      message: 'load-balancer-api-external: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:14Z"
    - latency: 6.772122ms
      message: 'load-balancer-api-external: resolved host name a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:03:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:01:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 79922ebf-fd22-46d9-8201-d729d5064bf6
    resourceVersion: "14068"
    uid: 18db865a-841d-4a79-bc39-446cf437225d
  spec:
    sourcePod: network-check-source-56d84b9f44-5ctz2
    targetEndpoint: a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:07:14Z"
      message: 'load-balancer-api-internal: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.174152ms
      message: 'load-balancer-api-internal: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:14Z"
    - latency: 11.420678ms
      message: 'load-balancer-api-internal: resolved host name a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:07:14Z"
    - latency: 5.230696ms
      message: 'load-balancer-api-internal: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:14Z"
    - latency: 7.295385ms
      message: 'load-balancer-api-internal: resolved host name a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:06:14Z"
    - latency: 4.273445ms
      message: 'load-balancer-api-internal: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:14Z"
    - latency: 6.488484ms
      message: 'load-balancer-api-internal: resolved host name a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:05:14Z"
    - latency: 4.439356ms
      message: 'load-balancer-api-internal: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:14Z"
    - latency: 10.483008ms
      message: 'load-balancer-api-internal: resolved host name a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:04:14Z"
    - latency: 4.878503ms
      message: 'load-balancer-api-internal: tcp connection to a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:14Z"
    - latency: 6.854931ms
      message: 'load-balancer-api-internal: resolved host name a2d0546a30c0e4d98b2c9e2e1a884b7e-6ac10639c3607aef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:03:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:01:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-128-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 79922ebf-fd22-46d9-8201-d729d5064bf6
    resourceVersion: "14396"
    uid: 0fbeb89d-56e3-46f7-8d18-ada408f7d298
  spec:
    sourcePod: network-check-source-56d84b9f44-5ctz2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:08:14Z"
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.508674ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:08:14Z"
    - latency: 918.198µs
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:14Z"
    - latency: 1.576097ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:14Z"
    - latency: 1.445219ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:14Z"
    - latency: 838.915µs
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:14Z"
    - latency: 1.572775ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:14Z"
    - latency: 1.507204ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:01:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-134-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 79922ebf-fd22-46d9-8201-d729d5064bf6
    resourceVersion: "14397"
    uid: c3963182-049e-4262-8148-6e0558c9aeb4
  spec:
    sourcePod: network-check-source-56d84b9f44-5ctz2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:08:14Z"
      message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.501234ms
      message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:08:14Z"
    - latency: 2.596145ms
      message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:14Z"
    - latency: 2.324314ms
      message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:14Z"
    - latency: 2.327433ms
      message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:14Z"
    - latency: 2.168983ms
      message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:14Z"
    - latency: 1.980183ms
      message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:14Z"
    - latency: 2.358374ms
      message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:01:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-138-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 79922ebf-fd22-46d9-8201-d729d5064bf6
    resourceVersion: "14395"
    uid: 3866e5d4-a52d-483f-8e4c-6b4e11659067
  spec:
    sourcePod: network-check-source-56d84b9f44-5ctz2
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:08:14Z"
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.419739ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:08:14Z"
    - latency: 2.033807ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:14Z"
    - latency: 2.216649ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:14Z"
    - latency: 2.083559ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:14Z"
    - latency: 2.290815ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:14Z"
    - latency: 2.087537ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:14Z"
    - latency: 2.249422ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:01:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 79922ebf-fd22-46d9-8201-d729d5064bf6
    resourceVersion: "14066"
    uid: 5df6c675-aa8f-43e6-8476-d687ec853406
  spec:
    sourcePod: network-check-source-56d84b9f44-5ctz2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:07:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.307797ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:14Z"
    - latency: 2.519923ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:07:14Z"
    - latency: 926.194µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:14Z"
    - latency: 2.137821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:06:14Z"
    - latency: 814.069µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:14Z"
    - latency: 2.029142ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:05:14Z"
    - latency: 830.183µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:14Z"
    - latency: 1.675328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:04:14Z"
    - latency: 1.120377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:14Z"
    - latency: 1.698941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:03:14Z"
kind: List
metadata:
  resourceVersion: ""