apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T16:28:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6d8b93c5-686f-4022-85ef-680629d13f22
    resourceVersion: "23501"
    uid: 9a02ee23-da82-460b-b3af-9559cea96754
  spec:
    sourcePod: network-check-source-8894fc9bd-vwzmz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T16:35:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.444µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:35:03Z"
    - latency: 875.684µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:34:03Z"
    - latency: 868.535µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:33:03Z"
    - latency: 1.043677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:32:03Z"
    - latency: 990.468µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:31:03Z"
    - latency: 840.955µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:30:03Z"
    - latency: 986.632µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:29:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T16:28:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6d8b93c5-686f-4022-85ef-680629d13f22
    resourceVersion: "22355"
    uid: bf1da366-2b05-4a83-a3fd-f9b83b29d696
  spec:
    sourcePod: network-check-source-8894fc9bd-vwzmz
    targetEndpoint: a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T16:34:03Z"
      message: 'load-balancer-api-external: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.623812ms
      message: 'load-balancer-api-external: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:34:03Z"
    - latency: 6.452814ms
      message: 'load-balancer-api-external: resolved host name a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:34:03Z"
    - latency: 3.276632ms
      message: 'load-balancer-api-external: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:33:03Z"
    - latency: 6.73018ms
      message: 'load-balancer-api-external: resolved host name a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:33:03Z"
    - latency: 4.299676ms
      message: 'load-balancer-api-external: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:32:03Z"
    - latency: 7.081919ms
      message: 'load-balancer-api-external: resolved host name a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:32:03Z"
    - latency: 4.800523ms
      message: 'load-balancer-api-external: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:31:03Z"
    - latency: 7.413702ms
      message: 'load-balancer-api-external: resolved host name a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:31:03Z"
    - latency: 5.155831ms
      message: 'load-balancer-api-external: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:30:03Z"
    - latency: 7.307355ms
      message: 'load-balancer-api-external: resolved host name a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:30:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T16:28:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6d8b93c5-686f-4022-85ef-680629d13f22
    resourceVersion: "22354"
    uid: 517b467e-34ae-4f76-87d6-ec2fbe80103a
  spec:
    sourcePod: network-check-source-8894fc9bd-vwzmz
    targetEndpoint: a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T16:34:03Z"
      message: 'load-balancer-api-internal: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.644944ms
      message: 'load-balancer-api-internal: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:34:03Z"
    - latency: 6.50488ms
      message: 'load-balancer-api-internal: resolved host name a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:34:03Z"
    - latency: 3.478657ms
      message: 'load-balancer-api-internal: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:33:03Z"
    - latency: 6.760048ms
      message: 'load-balancer-api-internal: resolved host name a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:33:03Z"
    - latency: 4.284589ms
      message: 'load-balancer-api-internal: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:32:03Z"
    - latency: 7.094175ms
      message: 'load-balancer-api-internal: resolved host name a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:32:03Z"
    - latency: 4.787999ms
      message: 'load-balancer-api-internal: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:31:03Z"
    - latency: 7.471766ms
      message: 'load-balancer-api-internal: resolved host name a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:31:03Z"
    - latency: 4.727924ms
      message: 'load-balancer-api-internal: tcp connection to a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:30:03Z"
    - latency: 7.393314ms
      message: 'load-balancer-api-internal: resolved host name a528fa2d42f26401d900f5ea810edbaf-5318e32148c508b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:30:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T16:28:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-130-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6d8b93c5-686f-4022-85ef-680629d13f22
    resourceVersion: "23500"
    uid: 74494d1f-1b68-4ca0-bd0e-67bded10b9d9
  spec:
    sourcePod: network-check-source-8894fc9bd-vwzmz
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T16:35:03Z"
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.228962ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:35:03Z"
    - latency: 1.88712ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:34:03Z"
    - latency: 2.266822ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:33:03Z"
    - latency: 2.244681ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:32:03Z"
    - latency: 2.405082ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:31:03Z"
    - latency: 2.266561ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:30:03Z"
    - latency: 2.170004ms
      message: 'network-check-target-ip-10-0-130-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:29:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T16:28:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-135-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6d8b93c5-686f-4022-85ef-680629d13f22
    resourceVersion: "23498"
    uid: e1216ccc-bfcc-4f05-94da-3d70cc484c21
  spec:
    sourcePod: network-check-source-8894fc9bd-vwzmz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T16:35:03Z"
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.752µs
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:35:03Z"
    - latency: 827.903µs
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:34:03Z"
    - latency: 895.6µs
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:33:03Z"
    - latency: 1.039131ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:32:03Z"
    - latency: 752.939µs
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:31:03Z"
    - latency: 1.094472ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:30:03Z"
    - latency: 1.662577ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:29:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T16:28:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-142-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6d8b93c5-686f-4022-85ef-680629d13f22
    resourceVersion: "23499"
    uid: 3cff3983-2652-4cb6-9b7a-e32510f70a73
  spec:
    sourcePod: network-check-source-8894fc9bd-vwzmz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T16:35:03Z"
      message: 'network-check-target-ip-10-0-142-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.230208ms
      message: 'network-check-target-ip-10-0-142-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:35:03Z"
    - latency: 1.974196ms
      message: 'network-check-target-ip-10-0-142-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:34:03Z"
    - latency: 2.298864ms
      message: 'network-check-target-ip-10-0-142-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:33:03Z"
    - latency: 2.811054ms
      message: 'network-check-target-ip-10-0-142-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:32:03Z"
    - latency: 2.732406ms
      message: 'network-check-target-ip-10-0-142-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:31:03Z"
    - latency: 2.0893ms
      message: 'network-check-target-ip-10-0-142-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:30:03Z"
    - latency: 2.696718ms
      message: 'network-check-target-ip-10-0-142-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:29:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T16:28:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6d8b93c5-686f-4022-85ef-680629d13f22
    resourceVersion: "22353"
    uid: e2935c6b-2c2f-4fb7-8eed-58dfad4e08b9
  spec:
    sourcePod: network-check-source-8894fc9bd-vwzmz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T16:34:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.697µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:34:03Z"
    - latency: 1.670516ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:34:03Z"
    - latency: 910.157µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:33:03Z"
    - latency: 1.817086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:33:03Z"
    - latency: 923.808µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:32:03Z"
    - latency: 2.025304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:32:03Z"
    - latency: 794.981µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:31:03Z"
    - latency: 1.665913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:31:03Z"
    - latency: 851.467µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T16:30:03Z"
    - latency: 1.921478ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T16:30:03Z"
kind: List
metadata:
  resourceVersion: ""