apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:24:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-115-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-115.ec2.internal
      uid: e0516150-d2e7-439a-a746-e69b49ed6066
    resourceVersion: "26060"
    uid: a83f10f9-5ee2-4af7-aa1b-7485a652537d
  spec:
    sourcePod: network-check-source-685456655f-9x9vj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:31:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.436113ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:31:07Z"
    - latency: 3.699295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:07Z"
    - latency: 1.091953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:07Z"
    - latency: 954.819µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:07Z"
    - latency: 1.079107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:07Z"
    - latency: 982.618µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:07Z"
    - latency: 1.247557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:24:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-115-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-115.ec2.internal
      uid: e0516150-d2e7-439a-a746-e69b49ed6066
    resourceVersion: "24730"
    uid: 974024a1-4e4f-4a20-bb81-60eef8b5c601
  spec:
    sourcePod: network-check-source-685456655f-9x9vj
    targetEndpoint: addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:30:07Z"
      message: 'load-balancer-api-external: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.29757ms
      message: 'load-balancer-api-external: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:07Z"
    - latency: 36.137702ms
      message: 'load-balancer-api-external: resolved host name addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:30:07Z"
    - latency: 7.022175ms
      message: 'load-balancer-api-external: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:07Z"
    - latency: 15.137148ms
      message: 'load-balancer-api-external: resolved host name addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:29:07Z"
    - latency: 4.187782ms
      message: 'load-balancer-api-external: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:07Z"
    - latency: 9.696201ms
      message: 'load-balancer-api-external: resolved host name addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:28:07Z"
    - latency: 4.938491ms
      message: 'load-balancer-api-external: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:07Z"
    - latency: 8.294598ms
      message: 'load-balancer-api-external: resolved host name addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:27:07Z"
    - latency: 4.649426ms
      message: 'load-balancer-api-external: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:07Z"
    - latency: 8.699541ms
      message: 'load-balancer-api-external: resolved host name addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:26:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:24:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-115-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-115.ec2.internal
      uid: e0516150-d2e7-439a-a746-e69b49ed6066
    resourceVersion: "24729"
    uid: 0ac79d59-1492-4fe9-9455-08b2e39f37d4
  spec:
    sourcePod: network-check-source-685456655f-9x9vj
    targetEndpoint: addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:30:07Z"
      message: 'load-balancer-api-internal: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.158594ms
      message: 'load-balancer-api-internal: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:07Z"
    - latency: 36.091512ms
      message: 'load-balancer-api-internal: resolved host name addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:30:07Z"
    - latency: 5.202274ms
      message: 'load-balancer-api-internal: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:07Z"
    - latency: 15.241448ms
      message: 'load-balancer-api-internal: resolved host name addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:29:07Z"
    - latency: 6.68122ms
      message: 'load-balancer-api-internal: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:07Z"
    - latency: 9.7106ms
      message: 'load-balancer-api-internal: resolved host name addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:28:07Z"
    - latency: 4.603541ms
      message: 'load-balancer-api-internal: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:07Z"
    - latency: 8.175378ms
      message: 'load-balancer-api-internal: resolved host name addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:27:07Z"
    - latency: 4.572735ms
      message: 'load-balancer-api-internal: tcp connection to addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:07Z"
    - latency: 8.730121ms
      message: 'load-balancer-api-internal: resolved host name addc66a19b3ac4b92b8edc9b8078c97f-7c51409ca0140733.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:26:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:24:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-115-to-network-check-target-ip-10-0-128-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-115.ec2.internal
      uid: e0516150-d2e7-439a-a746-e69b49ed6066
    resourceVersion: "26058"
    uid: e4efb0fe-8ba4-4300-a973-0b3fc8b2cac8
  spec:
    sourcePod: network-check-source-685456655f-9x9vj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:31:07Z"
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.417581ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:31:07Z"
    - latency: 3.272492ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:07Z"
    - latency: 2.304257ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:07Z"
    - latency: 2.279836ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:07Z"
    - latency: 2.385324ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:07Z"
    - latency: 2.382527ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:07Z"
    - latency: 2.52817ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:24:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-115-to-network-check-target-ip-10-0-133-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-115.ec2.internal
      uid: e0516150-d2e7-439a-a746-e69b49ed6066
    resourceVersion: "26059"
    uid: 2fdb4fe3-148b-43b7-89d3-114d5c3994b0
  spec:
    sourcePod: network-check-source-685456655f-9x9vj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:31:07Z"
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.945435ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:31:07Z"
    - latency: 2.833007ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:07Z"
    - latency: 2.394243ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:07Z"
    - latency: 2.388088ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:07Z"
    - latency: 2.354168ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:07Z"
    - latency: 2.194839ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:07Z"
    - latency: 2.500026ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:24:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-115-to-network-check-target-ip-10-0-137-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-115.ec2.internal
      uid: e0516150-d2e7-439a-a746-e69b49ed6066
    resourceVersion: "26057"
    uid: 1153524e-304e-435a-b4a4-8614d2c56f7e
  spec:
    sourcePod: network-check-source-685456655f-9x9vj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:31:07Z"
      message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.110426ms
      message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:31:07Z"
    - latency: 8.517784ms
      message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:07Z"
    - latency: 957.608µs
      message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:07Z"
    - latency: 894.08µs
      message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:07Z"
    - latency: 932.749µs
      message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:07Z"
    - latency: 947.855µs
      message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:07Z"
    - latency: 1.855806ms
      message: 'network-check-target-ip-10-0-137-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:24:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-115-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-115.ec2.internal
      uid: e0516150-d2e7-439a-a746-e69b49ed6066
    resourceVersion: "24728"
    uid: 9fa649ca-1dac-4010-b6d6-e291d1e96c4c
  spec:
    sourcePod: network-check-source-685456655f-9x9vj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:30:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.554875ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:30:07Z"
    - latency: 17.508891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:30:07Z"
    - latency: 990.157µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:29:07Z"
    - latency: 1.722644ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:29:07Z"
    - latency: 986.913µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:07Z"
    - latency: 2.190815ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:28:07Z"
    - latency: 883.934µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:07Z"
    - latency: 1.926558ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:27:07Z"
    - latency: 1.06528ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:07Z"
    - latency: 2.256491ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:26:07Z"
kind: List
metadata:
  resourceVersion: ""