apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:34:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-205-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-205.ec2.internal
      uid: ad49e0fb-a31b-4846-b24d-fb976f501d6f
    resourceVersion: "13661"
    uid: 9629168e-3caf-43f2-9cd4-8c09714da6c7
  spec:
    sourcePod: network-check-source-dbd9cf844-fcb6b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:41:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.079532ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:41:12Z"
    - latency: 1.037111ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:40:12Z"
    - latency: 933.904µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:39:12Z"
    - latency: 1.108439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:38:12Z"
    - latency: 1.091055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:37:12Z"
    - latency: 853.137µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:36:12Z"
    - latency: 1.404287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:35:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:34:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-205-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-205.ec2.internal
      uid: ad49e0fb-a31b-4846-b24d-fb976f501d6f
    resourceVersion: "13393"
    uid: 25eb5a6f-cc77-4722-a2cb-43592d7d8bd8
  spec:
    sourcePod: network-check-source-dbd9cf844-fcb6b
    targetEndpoint: a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:40:12Z"
      message: 'load-balancer-api-external: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.093446ms
      message: 'load-balancer-api-external: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:40:12Z"
    - latency: 7.645894ms
      message: 'load-balancer-api-external: resolved host name a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:40:12Z"
    - latency: 5.232654ms
      message: 'load-balancer-api-external: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:39:12Z"
    - latency: 6.496379ms
      message: 'load-balancer-api-external: resolved host name a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:39:12Z"
    - latency: 4.231129ms
      message: 'load-balancer-api-external: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:38:12Z"
    - latency: 7.272569ms
      message: 'load-balancer-api-external: resolved host name a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:38:12Z"
    - latency: 4.570733ms
      message: 'load-balancer-api-external: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:37:12Z"
    - latency: 8.436442ms
      message: 'load-balancer-api-external: resolved host name a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:37:12Z"
    - latency: 4.614282ms
      message: 'load-balancer-api-external: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:36:12Z"
    - latency: 6.788204ms
      message: 'load-balancer-api-external: resolved host name a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:36:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:34:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-205-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-205.ec2.internal
      uid: ad49e0fb-a31b-4846-b24d-fb976f501d6f
    resourceVersion: "13392"
    uid: e9515e12-6f77-4bc9-8b85-46d4d285af36
  spec:
    sourcePod: network-check-source-dbd9cf844-fcb6b
    targetEndpoint: a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:40:12Z"
      message: 'load-balancer-api-internal: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.085758ms
      message: 'load-balancer-api-internal: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:40:12Z"
    - latency: 7.669545ms
      message: 'load-balancer-api-internal: resolved host name a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:40:12Z"
    - latency: 5.242602ms
      message: 'load-balancer-api-internal: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:39:12Z"
    - latency: 6.414582ms
      message: 'load-balancer-api-internal: resolved host name a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:39:12Z"
    - latency: 4.710779ms
      message: 'load-balancer-api-internal: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:38:12Z"
    - latency: 7.34461ms
      message: 'load-balancer-api-internal: resolved host name a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:38:12Z"
    - latency: 4.431966ms
      message: 'load-balancer-api-internal: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:37:12Z"
    - latency: 8.46414ms
      message: 'load-balancer-api-internal: resolved host name a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:37:12Z"
    - latency: 4.602681ms
      message: 'load-balancer-api-internal: tcp connection to a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:36:12Z"
    - latency: 6.767188ms
      message: 'load-balancer-api-internal: resolved host name a3fa9a1fe8c0843fe93b3a56ffe6c74f-b1300910ae37879d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:36:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:34:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-205-to-network-check-target-ip-10-0-133-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-205.ec2.internal
      uid: ad49e0fb-a31b-4846-b24d-fb976f501d6f
    resourceVersion: "13659"
    uid: a8c7dd53-e980-40f1-9fa7-f87ae3093faa
  spec:
    sourcePod: network-check-source-dbd9cf844-fcb6b
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:41:12Z"
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.0338ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:41:12Z"
    - latency: 1.755526ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:40:12Z"
    - latency: 1.942395ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:39:12Z"
    - latency: 2.101198ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:38:12Z"
    - latency: 1.998543ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:37:12Z"
    - latency: 1.831619ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:36:12Z"
    - latency: 2.158279ms
      message: 'network-check-target-ip-10-0-133-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:35:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:34:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-205-to-network-check-target-ip-10-0-134-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-205.ec2.internal
      uid: ad49e0fb-a31b-4846-b24d-fb976f501d6f
    resourceVersion: "13658"
    uid: 3d0f6ead-d5a1-4305-ae65-de141cda9419
  spec:
    sourcePod: network-check-source-dbd9cf844-fcb6b
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:41:12Z"
      message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 862.92µs
      message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:41:12Z"
    - latency: 798.75µs
      message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:40:12Z"
    - latency: 811.069µs
      message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:39:12Z"
    - latency: 1.030502ms
      message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:38:12Z"
    - latency: 875.287µs
      message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:37:12Z"
    - latency: 843.263µs
      message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:36:12Z"
    - latency: 1.370902ms
      message: 'network-check-target-ip-10-0-134-205: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:35:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:34:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-205-to-network-check-target-ip-10-0-143-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-205.ec2.internal
      uid: ad49e0fb-a31b-4846-b24d-fb976f501d6f
    resourceVersion: "13660"
    uid: 0c3e121c-a24c-4a7e-a701-9ba20a9237b6
  spec:
    sourcePod: network-check-source-dbd9cf844-fcb6b
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:41:12Z"
      message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.355636ms
      message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:41:12Z"
    - latency: 2.077454ms
      message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:40:12Z"
    - latency: 2.308325ms
      message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:39:12Z"
    - latency: 2.100947ms
      message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:38:12Z"
    - latency: 2.210443ms
      message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:37:12Z"
    - latency: 1.858643ms
      message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:36:12Z"
    - latency: 2.181484ms
      message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:35:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T20:34:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-205-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-205.ec2.internal
      uid: ad49e0fb-a31b-4846-b24d-fb976f501d6f
    resourceVersion: "13391"
    uid: 7e4527e8-7585-4faf-af75-5b2c671ed0ba
  spec:
    sourcePod: network-check-source-dbd9cf844-fcb6b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T20:40:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 795.825µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:40:12Z"
    - latency: 1.802223ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:40:12Z"
    - latency: 872.095µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:39:12Z"
    - latency: 1.621097ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:39:12Z"
    - latency: 855.929µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:38:12Z"
    - latency: 2.279305ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:38:12Z"
    - latency: 880.511µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:37:12Z"
    - latency: 1.737502ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:37:12Z"
    - latency: 901.582µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T20:36:12Z"
    - latency: 2.074707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T20:36:12Z"
kind: List
metadata:
  resourceVersion: ""