apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-87-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-87.ec2.internal
      uid: ebd03a5e-6f10-4fd6-a4b3-8f4254bc3e5f
    resourceVersion: "22144"
    uid: eebdece1-0309-48bf-b840-a2e3e46c97bd
  spec:
    sourcePod: network-check-source-6f8b768455-b6hh4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:38:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.446261ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:38:42Z"
    - latency: 1.123865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:37:42Z"
    - latency: 1.195534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:36:42Z"
    - latency: 1.325495ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:35:42Z"
    - latency: 1.352919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:34:42Z"
    - latency: 1.081457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:33:42Z"
    - latency: 1.371099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:32:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-87-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-87.ec2.internal
      uid: ebd03a5e-6f10-4fd6-a4b3-8f4254bc3e5f
    resourceVersion: "21521"
    uid: 783cc610-4506-46f9-87d1-33b194b69691
  spec:
    sourcePod: network-check-source-6f8b768455-b6hh4
    targetEndpoint: a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:37:42Z"
      message: 'load-balancer-api-external: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.760129ms
      message: 'load-balancer-api-external: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:37:42Z"
    - latency: 6.783738ms
      message: 'load-balancer-api-external: resolved host name a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:37:42Z"
    - latency: 3.391619ms
      message: 'load-balancer-api-external: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:36:42Z"
    - latency: 10.21929ms
      message: 'load-balancer-api-external: resolved host name a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:36:42Z"
    - latency: 2.414914ms
      message: 'load-balancer-api-external: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:35:42Z"
    - latency: 9.878398ms
      message: 'load-balancer-api-external: resolved host name a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:35:42Z"
    - latency: 4.067904ms
      message: 'load-balancer-api-external: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:34:42Z"
    - latency: 8.945779ms
      message: 'load-balancer-api-external: resolved host name a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:34:42Z"
    - latency: 3.083151ms
      message: 'load-balancer-api-external: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:33:42Z"
    - latency: 7.520124ms
      message: 'load-balancer-api-external: resolved host name a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:33:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-87-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-87.ec2.internal
      uid: ebd03a5e-6f10-4fd6-a4b3-8f4254bc3e5f
    resourceVersion: "21522"
    uid: 64aeb5a1-bb69-4e1e-a9de-227807300b8b
  spec:
    sourcePod: network-check-source-6f8b768455-b6hh4
    targetEndpoint: a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:37:42Z"
      message: 'load-balancer-api-internal: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.758129ms
      message: 'load-balancer-api-internal: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:37:42Z"
    - latency: 6.840594ms
      message: 'load-balancer-api-internal: resolved host name a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:37:42Z"
    - latency: 2.64266ms
      message: 'load-balancer-api-internal: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:36:42Z"
    - latency: 10.187334ms
      message: 'load-balancer-api-internal: resolved host name a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:36:42Z"
    - latency: 2.936927ms
      message: 'load-balancer-api-internal: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:35:42Z"
    - latency: 9.770511ms
      message: 'load-balancer-api-internal: resolved host name a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:35:42Z"
    - latency: 4.772301ms
      message: 'load-balancer-api-internal: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:34:42Z"
    - latency: 8.846085ms
      message: 'load-balancer-api-internal: resolved host name a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:34:42Z"
    - latency: 3.749359ms
      message: 'load-balancer-api-internal: tcp connection to a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:33:42Z"
    - latency: 7.461874ms
      message: 'load-balancer-api-internal: resolved host name a91b5379cfae54c38850b6b83d8d1270-964a8b2efb7112fb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:33:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-87-to-network-check-target-ip-10-0-130-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-87.ec2.internal
      uid: ebd03a5e-6f10-4fd6-a4b3-8f4254bc3e5f
    resourceVersion: "22142"
    uid: cdac3d2c-e2c6-4d98-a213-82f7363525b3
  spec:
    sourcePod: network-check-source-6f8b768455-b6hh4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:38:42Z"
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.326483ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:38:42Z"
    - latency: 1.114028ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:37:42Z"
    - latency: 950.67µs
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:36:42Z"
    - latency: 925.65µs
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:35:42Z"
    - latency: 1.744986ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:34:42Z"
    - latency: 1.197577ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:33:42Z"
    - latency: 1.19809ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:32:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-87-to-network-check-target-ip-10-0-136-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-87.ec2.internal
      uid: ebd03a5e-6f10-4fd6-a4b3-8f4254bc3e5f
    resourceVersion: "22143"
    uid: eee63986-5681-46f3-b352-27ee8fa5f215
  spec:
    sourcePod: network-check-source-6f8b768455-b6hh4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:38:42Z"
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.534691ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:38:42Z"
    - latency: 2.245296ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:37:42Z"
    - latency: 2.34238ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:36:42Z"
    - latency: 2.157056ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:35:42Z"
    - latency: 2.2339ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:34:42Z"
    - latency: 2.190161ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:33:42Z"
    - latency: 2.421945ms
      message: 'network-check-target-ip-10-0-136-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:32:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-87-to-network-check-target-ip-10-0-136-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-87.ec2.internal
      uid: ebd03a5e-6f10-4fd6-a4b3-8f4254bc3e5f
    resourceVersion: "22141"
    uid: 44f072ce-319c-46be-b5a9-4b246476c877
  spec:
    sourcePod: network-check-source-6f8b768455-b6hh4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:38:42Z"
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.99441ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:38:42Z"
    - latency: 1.897006ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:37:42Z"
    - latency: 2.088882ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:36:42Z"
    - latency: 2.113151ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:35:42Z"
    - latency: 2.147569ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:34:42Z"
    - latency: 1.93872ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:33:42Z"
    - latency: 1.898417ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:32:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:31:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-87-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-87.ec2.internal
      uid: ebd03a5e-6f10-4fd6-a4b3-8f4254bc3e5f
    resourceVersion: "21520"
    uid: f848ace2-314a-48e2-a1bc-f362c76380b8
  spec:
    sourcePod: network-check-source-6f8b768455-b6hh4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:37:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.837µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:37:42Z"
    - latency: 1.979638ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:37:42Z"
    - latency: 889.035µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:36:42Z"
    - latency: 2.484826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:36:42Z"
    - latency: 951.969µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:35:42Z"
    - latency: 1.869818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:35:42Z"
    - latency: 996.413µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:34:42Z"
    - latency: 1.718888ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:34:42Z"
    - latency: 1.010046ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T09:33:42Z"
    - latency: 1.764234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T09:33:42Z"
kind: List
metadata:
  resourceVersion: ""