apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T10:25:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 0367fe62-88e5-462b-987b-5b1eb5e6a3c2
    resourceVersion: "15673"
    uid: b80b638e-1463-42b3-ace3-b5699ba1d723
  spec:
    sourcePod: network-check-source-dbd9cf844-rf2js
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T10:32:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.098424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:32:40Z"
    - latency: 1.388045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:31:40Z"
    - latency: 1.077953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:30:40Z"
    - latency: 865.854µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:29:40Z"
    - latency: 982.888µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:28:40Z"
    - latency: 1.441293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:27:40Z"
    - latency: 955.998µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:26:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T10:25:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 0367fe62-88e5-462b-987b-5b1eb5e6a3c2
    resourceVersion: "15328"
    uid: 60aa6fa9-a55d-41e7-a563-a26db8df0021
  spec:
    sourcePod: network-check-source-dbd9cf844-rf2js
    targetEndpoint: a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T10:31:40Z"
      message: 'load-balancer-api-external: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.843122ms
      message: 'load-balancer-api-external: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:31:40Z"
    - latency: 8.794931ms
      message: 'load-balancer-api-external: resolved host name a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:31:40Z"
    - latency: 4.17791ms
      message: 'load-balancer-api-external: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:30:40Z"
    - latency: 8.387114ms
      message: 'load-balancer-api-external: resolved host name a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:30:40Z"
    - latency: 5.221574ms
      message: 'load-balancer-api-external: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:29:40Z"
    - latency: 8.594931ms
      message: 'load-balancer-api-external: resolved host name a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:29:40Z"
    - latency: 5.227412ms
      message: 'load-balancer-api-external: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:28:40Z"
    - latency: 8.921528ms
      message: 'load-balancer-api-external: resolved host name a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:28:40Z"
    - latency: 5.595145ms
      message: 'load-balancer-api-external: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:27:40Z"
    - latency: 10.354654ms
      message: 'load-balancer-api-external: resolved host name a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:27:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T10:25:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 0367fe62-88e5-462b-987b-5b1eb5e6a3c2
    resourceVersion: "15327"
    uid: f40174f6-38a0-4fa3-aab7-b4c8e44a663f
  spec:
    sourcePod: network-check-source-dbd9cf844-rf2js
    targetEndpoint: a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T10:31:40Z"
      message: 'load-balancer-api-internal: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.797483ms
      message: 'load-balancer-api-internal: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:31:40Z"
    - latency: 8.851011ms
      message: 'load-balancer-api-internal: resolved host name a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:31:40Z"
    - latency: 4.192796ms
      message: 'load-balancer-api-internal: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:30:40Z"
    - latency: 8.500957ms
      message: 'load-balancer-api-internal: resolved host name a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:30:40Z"
    - latency: 5.13992ms
      message: 'load-balancer-api-internal: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:29:40Z"
    - latency: 8.657012ms
      message: 'load-balancer-api-internal: resolved host name a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:29:40Z"
    - latency: 5.077665ms
      message: 'load-balancer-api-internal: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:28:40Z"
    - latency: 8.945645ms
      message: 'load-balancer-api-internal: resolved host name a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:28:40Z"
    - latency: 5.616499ms
      message: 'load-balancer-api-internal: tcp connection to a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:27:40Z"
    - latency: 10.132106ms
      message: 'load-balancer-api-internal: resolved host name a5f3341b6c2f54b81a0bc72961afda3c-bad735bb4ed6266b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:27:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T10:25:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-network-check-target-ip-10-0-132-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 0367fe62-88e5-462b-987b-5b1eb5e6a3c2
    resourceVersion: "15672"
    uid: 50494cdb-5e41-484e-87a1-bcae9e966dcd
  spec:
    sourcePod: network-check-source-dbd9cf844-rf2js
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T10:32:40Z"
      message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.175639ms
      message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:32:40Z"
    - latency: 2.157732ms
      message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:31:40Z"
    - latency: 2.233714ms
      message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:30:40Z"
    - latency: 2.010899ms
      message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:29:40Z"
    - latency: 2.046268ms
      message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:28:40Z"
    - latency: 2.259902ms
      message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:27:40Z"
    - latency: 1.980925ms
      message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:26:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T10:25:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-network-check-target-ip-10-0-132-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 0367fe62-88e5-462b-987b-5b1eb5e6a3c2
    resourceVersion: "15670"
    uid: 30a3d833-f8b1-43d9-a858-138321b948ee
  spec:
    sourcePod: network-check-source-dbd9cf844-rf2js
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T10:32:40Z"
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.009499ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:32:40Z"
    - latency: 1.829709ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:31:40Z"
    - latency: 2.179162ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:30:40Z"
    - latency: 2.336162ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:29:40Z"
    - latency: 2.167033ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:28:40Z"
    - latency: 2.425641ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:27:40Z"
    - latency: 2.383023ms
      message: 'network-check-target-ip-10-0-132-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:26:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T10:25:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-network-check-target-ip-10-0-142-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 0367fe62-88e5-462b-987b-5b1eb5e6a3c2
    resourceVersion: "15671"
    uid: 148564e5-e6b1-40dd-ac19-01fad0496668
  spec:
    sourcePod: network-check-source-dbd9cf844-rf2js
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T10:32:40Z"
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.61µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:32:40Z"
    - latency: 1.46782ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:31:40Z"
    - latency: 775.329µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:30:40Z"
    - latency: 1.558765ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:29:40Z"
    - latency: 949.516µs
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:28:40Z"
    - latency: 1.651202ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:27:40Z"
    - latency: 1.315834ms
      message: 'network-check-target-ip-10-0-142-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:26:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T10:25:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-211-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-211.ec2.internal
      uid: 0367fe62-88e5-462b-987b-5b1eb5e6a3c2
    resourceVersion: "15326"
    uid: ea091b85-cd77-4e5c-991b-493f067f787c
  spec:
    sourcePod: network-check-source-dbd9cf844-rf2js
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T10:31:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 746.018µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:31:40Z"
    - latency: 2.106243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:31:40Z"
    - latency: 749.83µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:30:40Z"
    - latency: 1.534187ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:30:40Z"
    - latency: 821.095µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:29:40Z"
    - latency: 1.654452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:29:40Z"
    - latency: 799.32µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:28:40Z"
    - latency: 1.782004ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:28:40Z"
    - latency: 1.19296ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T10:27:40Z"
    - latency: 2.479802ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T10:27:40Z"
kind: List
metadata:
  resourceVersion: ""