apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T17:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: 8c752d91-6711-4476-bd19-5a302351df35
    resourceVersion: "24742"
    uid: f03a71b5-92c3-4e10-ba26-2c1638690473
  spec:
    sourcePod: network-check-source-dbd9cf844-lv6vl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T17:46:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.074314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:46:55Z"
    - latency: 1.317194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:45:55Z"
    - latency: 1.099557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:44:55Z"
    - latency: 968.802µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:43:55Z"
    - latency: 1.540469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:42:55Z"
    - latency: 959.141µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:41:55Z"
    - latency: 1.561327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:40:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T17:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: 8c752d91-6711-4476-bd19-5a302351df35
    resourceVersion: "23857"
    uid: 74ffa15d-2535-4aa4-aeca-1abb91f92021
  spec:
    sourcePod: network-check-source-dbd9cf844-lv6vl
    targetEndpoint: ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T17:45:55Z"
      message: 'load-balancer-api-external: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.20173ms
      message: 'load-balancer-api-external: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:45:55Z"
    - latency: 10.844135ms
      message: 'load-balancer-api-external: resolved host name ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:45:55Z"
    - latency: 3.61573ms
      message: 'load-balancer-api-external: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:44:55Z"
    - latency: 8.248239ms
      message: 'load-balancer-api-external: resolved host name ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:44:55Z"
    - latency: 4.597587ms
      message: 'load-balancer-api-external: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:43:55Z"
    - latency: 8.857154ms
      message: 'load-balancer-api-external: resolved host name ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:43:55Z"
    - latency: 5.476398ms
      message: 'load-balancer-api-external: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:42:55Z"
    - latency: 7.390428ms
      message: 'load-balancer-api-external: resolved host name ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:42:55Z"
    - latency: 5.947955ms
      message: 'load-balancer-api-external: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:41:55Z"
    - latency: 22.089352ms
      message: 'load-balancer-api-external: resolved host name ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:41:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T17:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: 8c752d91-6711-4476-bd19-5a302351df35
    resourceVersion: "23858"
    uid: 7185f461-3d9c-401d-9d8a-ccdedbb06a4e
  spec:
    sourcePod: network-check-source-dbd9cf844-lv6vl
    targetEndpoint: ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T17:45:55Z"
      message: 'load-balancer-api-internal: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.282898ms
      message: 'load-balancer-api-internal: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:45:55Z"
    - latency: 10.776259ms
      message: 'load-balancer-api-internal: resolved host name ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:45:55Z"
    - latency: 3.653601ms
      message: 'load-balancer-api-internal: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:44:55Z"
    - latency: 8.183865ms
      message: 'load-balancer-api-internal: resolved host name ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:44:55Z"
    - latency: 4.612131ms
      message: 'load-balancer-api-internal: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:43:55Z"
    - latency: 8.84916ms
      message: 'load-balancer-api-internal: resolved host name ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:43:55Z"
    - latency: 5.330065ms
      message: 'load-balancer-api-internal: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:42:55Z"
    - latency: 7.452108ms
      message: 'load-balancer-api-internal: resolved host name ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:42:55Z"
    - latency: 6.963648ms
      message: 'load-balancer-api-internal: tcp connection to ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:41:55Z"
    - latency: 22.19597ms
      message: 'load-balancer-api-internal: resolved host name ae2571a585a6c4567a6e8fedc2d26c38-1cf083f2bd8a0010.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:41:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T17:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-ip-10-0-136-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: 8c752d91-6711-4476-bd19-5a302351df35
    resourceVersion: "24740"
    uid: f698cd57-1179-48fa-a1c7-d5b7a9f9d8ca
  spec:
    sourcePod: network-check-source-dbd9cf844-lv6vl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T17:46:55Z"
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.104797ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:46:55Z"
    - latency: 2.205971ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:45:55Z"
    - latency: 2.754817ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:44:55Z"
    - latency: 2.282796ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:43:55Z"
    - latency: 2.182113ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:42:55Z"
    - latency: 2.192871ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:41:55Z"
    - latency: 2.301944ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:40:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T17:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-ip-10-0-143-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: 8c752d91-6711-4476-bd19-5a302351df35
    resourceVersion: "24739"
    uid: 6ac876ea-809d-493f-b5fe-abd9cfb0e336
  spec:
    sourcePod: network-check-source-dbd9cf844-lv6vl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T17:46:55Z"
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.414544ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:46:55Z"
    - latency: 1.12167ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:45:55Z"
    - latency: 958.453µs
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:44:55Z"
    - latency: 895.5µs
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:43:55Z"
    - latency: 842.399µs
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:42:55Z"
    - latency: 907.846µs
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:41:55Z"
    - latency: 1.147001ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:40:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T17:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-ip-10-0-143-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: 8c752d91-6711-4476-bd19-5a302351df35
    resourceVersion: "24741"
    uid: 95539ec6-56eb-46ab-b724-1b40217c257e
  spec:
    sourcePod: network-check-source-dbd9cf844-lv6vl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T17:46:55Z"
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.325681ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:46:55Z"
    - latency: 2.084683ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:45:55Z"
    - latency: 2.340726ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:44:55Z"
    - latency: 2.689966ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:43:55Z"
    - latency: 2.276164ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:42:55Z"
    - latency: 2.147296ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:41:55Z"
    - latency: 2.349256ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:40:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T17:39:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: 8c752d91-6711-4476-bd19-5a302351df35
    resourceVersion: "23856"
    uid: d8ffaa1a-92c1-423a-b47f-57bb53c269d1
  spec:
    sourcePod: network-check-source-dbd9cf844-lv6vl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T17:45:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.283893ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:45:55Z"
    - latency: 1.818805ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:45:55Z"
    - latency: 873.78µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:44:55Z"
    - latency: 1.951034ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:44:55Z"
    - latency: 999.838µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:43:55Z"
    - latency: 2.03689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:43:55Z"
    - latency: 864.504µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:42:55Z"
    - latency: 1.710528ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:42:55Z"
    - latency: 14.011951ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T17:41:55Z"
    - latency: 1.680007ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T17:41:55Z"
kind: List
metadata:
  resourceVersion: ""