apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-213-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-213.ec2.internal
      uid: 22e66b30-c109-45f5-9800-8faa1768f7e4
    resourceVersion: "14352"
    uid: 6b75b1fd-2a29-44dc-b4fa-3607e5607e91
  spec:
    sourcePod: network-check-source-989f8b8dc-tnnql
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20: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.635107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:02Z"
    - latency: 920.196µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:02Z"
    - latency: 923.711µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:02Z"
    - latency: 903.161µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:02Z"
    - latency: 1.13048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:02Z"
    - latency: 914.625µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:02Z"
    - latency: 1.154854ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:53:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-213-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-213.ec2.internal
      uid: 22e66b30-c109-45f5-9800-8faa1768f7e4
    resourceVersion: "13893"
    uid: c7aaa852-884d-405a-bf00-214d5f5a7ed0
  spec:
    sourcePod: network-check-source-989f8b8dc-tnnql
    targetEndpoint: a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:58:02Z"
      message: 'load-balancer-api-external: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.386306ms
      message: 'load-balancer-api-external: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:02Z"
    - latency: 8.008586ms
      message: 'load-balancer-api-external: resolved host name a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:58:02Z"
    - latency: 5.938397ms
      message: 'load-balancer-api-external: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:02Z"
    - latency: 10.530458ms
      message: 'load-balancer-api-external: resolved host name a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:57:02Z"
    - latency: 3.625774ms
      message: 'load-balancer-api-external: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:02Z"
    - latency: 8.214647ms
      message: 'load-balancer-api-external: resolved host name a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:56:02Z"
    - latency: 5.527133ms
      message: 'load-balancer-api-external: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:02Z"
    - latency: 9.958245ms
      message: 'load-balancer-api-external: resolved host name a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:55:02Z"
    - latency: 5.631384ms
      message: 'load-balancer-api-external: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:02Z"
    - latency: 7.385683ms
      message: 'load-balancer-api-external: resolved host name a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:54:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-213-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-213.ec2.internal
      uid: 22e66b30-c109-45f5-9800-8faa1768f7e4
    resourceVersion: "13892"
    uid: 2bf2c27d-bea9-4702-9883-b8a5f72c26af
  spec:
    sourcePod: network-check-source-989f8b8dc-tnnql
    targetEndpoint: a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:58:02Z"
      message: 'load-balancer-api-internal: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.803389ms
      message: 'load-balancer-api-internal: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:02Z"
    - latency: 7.941076ms
      message: 'load-balancer-api-internal: resolved host name a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:58:02Z"
    - latency: 5.157496ms
      message: 'load-balancer-api-internal: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:02Z"
    - latency: 10.438608ms
      message: 'load-balancer-api-internal: resolved host name a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:57:02Z"
    - latency: 3.611283ms
      message: 'load-balancer-api-internal: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:02Z"
    - latency: 8.155992ms
      message: 'load-balancer-api-internal: resolved host name a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:56:02Z"
    - latency: 5.640705ms
      message: 'load-balancer-api-internal: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:02Z"
    - latency: 9.875125ms
      message: 'load-balancer-api-internal: resolved host name a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:55:02Z"
    - latency: 5.699674ms
      message: 'load-balancer-api-internal: tcp connection to a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:02Z"
    - latency: 7.396759ms
      message: 'load-balancer-api-internal: resolved host name a8cd689112fa4416a93b70a899707ca0-a9417907f1b44282.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:54:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-213-to-network-check-target-ip-10-0-131-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-213.ec2.internal
      uid: 22e66b30-c109-45f5-9800-8faa1768f7e4
    resourceVersion: "14350"
    uid: 984d771a-3988-4d9c-bbab-becb80bafd26
  spec:
    sourcePod: network-check-source-989f8b8dc-tnnql
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:59:02Z"
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.214268ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:02Z"
    - latency: 2.161835ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:02Z"
    - latency: 1.928051ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:02Z"
    - latency: 2.170044ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:02Z"
    - latency: 2.426894ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:02Z"
    - latency: 2.08898ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:02Z"
    - latency: 2.571815ms
      message: 'network-check-target-ip-10-0-131-233: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:53:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-213-to-network-check-target-ip-10-0-135-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-213.ec2.internal
      uid: 22e66b30-c109-45f5-9800-8faa1768f7e4
    resourceVersion: "14349"
    uid: e5656c82-3392-49e0-9702-71a8c9eb2955
  spec:
    sourcePod: network-check-source-989f8b8dc-tnnql
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:59:02Z"
      message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.768632ms
      message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:02Z"
    - latency: 797.562µs
      message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:02Z"
    - latency: 1.396718ms
      message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:02Z"
    - latency: 873.701µs
      message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:02Z"
    - latency: 1.563188ms
      message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:02Z"
    - latency: 857.434µs
      message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:02Z"
    - latency: 1.584197ms
      message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:53:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-213-to-network-check-target-ip-10-0-138-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-213.ec2.internal
      uid: 22e66b30-c109-45f5-9800-8faa1768f7e4
    resourceVersion: "14351"
    uid: 372694a7-abf9-48ea-b32b-a7b650e7ce73
  spec:
    sourcePod: network-check-source-989f8b8dc-tnnql
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:59:02Z"
      message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.322589ms
      message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:02Z"
    - latency: 1.831599ms
      message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:02Z"
    - latency: 2.306921ms
      message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:02Z"
    - latency: 2.489854ms
      message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:02Z"
    - latency: 2.468704ms
      message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:02Z"
    - latency: 2.025088ms
      message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:02Z"
    - latency: 2.581858ms
      message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:53:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:52:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-213-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-213.ec2.internal
      uid: 22e66b30-c109-45f5-9800-8faa1768f7e4
    resourceVersion: "13891"
    uid: 47408e5d-d9d6-41cf-a2a3-a93d559f330c
  spec:
    sourcePod: network-check-source-989f8b8dc-tnnql
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:58:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.297148ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:02Z"
    - latency: 1.684239ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:58:02Z"
    - latency: 1.332129ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:02Z"
    - latency: 2.124307ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:57:02Z"
    - latency: 904.6µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:02Z"
    - latency: 1.822471ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:56:02Z"
    - latency: 865.971µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:02Z"
    - latency: 2.308084ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:55:02Z"
    - latency: 797.417µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:02Z"
    - latency: 1.627558ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:54:02Z"
kind: List
metadata:
  resourceVersion: ""