apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T15:59:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-161-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-161.ec2.internal
      uid: bf9256f7-d4d7-463a-b76d-0c5fa4d61326
    resourceVersion: "24585"
    uid: a8256f8f-e07c-4d56-a61e-e3ae4c7a35fe
  spec:
    sourcePod: network-check-source-6947749cfc-4n6j5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T16:06:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.154284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:06:41Z"
    - latency: 842.773µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:05:41Z"
    - latency: 1.044898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:04:41Z"
    - latency: 1.055944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:03:41Z"
    - latency: 887.971µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:02:41Z"
    - latency: 993.043µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:01:41Z"
    - latency: 1.375773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:00:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T15:59:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-161-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-161.ec2.internal
      uid: bf9256f7-d4d7-463a-b76d-0c5fa4d61326
    resourceVersion: "23950"
    uid: fbe78b2f-23e7-442b-9b4a-48d9b4b13fc2
  spec:
    sourcePod: network-check-source-6947749cfc-4n6j5
    targetEndpoint: a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T16:05:41Z"
      message: 'load-balancer-api-external: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.622561ms
      message: 'load-balancer-api-external: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:05:41Z"
    - latency: 6.981838ms
      message: 'load-balancer-api-external: resolved host name a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:05:41Z"
    - latency: 6.954258ms
      message: 'load-balancer-api-external: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:04:41Z"
    - latency: 8.27133ms
      message: 'load-balancer-api-external: resolved host name a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:04:41Z"
    - latency: 5.4426ms
      message: 'load-balancer-api-external: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:03:41Z"
    - latency: 8.757059ms
      message: 'load-balancer-api-external: resolved host name a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:03:41Z"
    - latency: 4.889763ms
      message: 'load-balancer-api-external: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:02:41Z"
    - latency: 9.104519ms
      message: 'load-balancer-api-external: resolved host name a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:02:41Z"
    - latency: 7.776535ms
      message: 'load-balancer-api-external: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:01:41Z"
    - latency: 7.743134ms
      message: 'load-balancer-api-external: resolved host name a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:01:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T15:59:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-161-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-161.ec2.internal
      uid: bf9256f7-d4d7-463a-b76d-0c5fa4d61326
    resourceVersion: "23951"
    uid: 3ab67445-751a-4c60-952c-e9c7bcaaed30
  spec:
    sourcePod: network-check-source-6947749cfc-4n6j5
    targetEndpoint: a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T16:05:41Z"
      message: 'load-balancer-api-internal: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.600267ms
      message: 'load-balancer-api-internal: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:05:41Z"
    - latency: 7.051175ms
      message: 'load-balancer-api-internal: resolved host name a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:05:41Z"
    - latency: 5.770445ms
      message: 'load-balancer-api-internal: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:04:41Z"
    - latency: 8.240016ms
      message: 'load-balancer-api-internal: resolved host name a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:04:41Z"
    - latency: 5.455762ms
      message: 'load-balancer-api-internal: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:03:41Z"
    - latency: 8.809359ms
      message: 'load-balancer-api-internal: resolved host name a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:03:41Z"
    - latency: 4.768156ms
      message: 'load-balancer-api-internal: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:02:41Z"
    - latency: 9.176627ms
      message: 'load-balancer-api-internal: resolved host name a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:02:41Z"
    - latency: 7.735391ms
      message: 'load-balancer-api-internal: tcp connection to a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:01:41Z"
    - latency: 7.817321ms
      message: 'load-balancer-api-internal: resolved host name a20b4923c56d949fc966b7dcc332de12-6704818da31fa9c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:01:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T15:59:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-161-to-network-check-target-ip-10-0-129-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-161.ec2.internal
      uid: bf9256f7-d4d7-463a-b76d-0c5fa4d61326
    resourceVersion: "24582"
    uid: ae59de6f-7d29-45f9-9120-bc35bd3531a3
  spec:
    sourcePod: network-check-source-6947749cfc-4n6j5
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T16:06:41Z"
      message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.248696ms
      message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:06:41Z"
    - latency: 890.305µs
      message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:05:41Z"
    - latency: 750.966µs
      message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:04:41Z"
    - latency: 870.53µs
      message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:03:41Z"
    - latency: 776.829µs
      message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:02:41Z"
    - latency: 1.3419ms
      message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:01:41Z"
    - latency: 1.110029ms
      message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:00:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T15:59:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-161-to-network-check-target-ip-10-0-134-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-161.ec2.internal
      uid: bf9256f7-d4d7-463a-b76d-0c5fa4d61326
    resourceVersion: "24583"
    uid: c7865206-f07c-4279-bb36-712d3fb6d4d3
  spec:
    sourcePod: network-check-source-6947749cfc-4n6j5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T16:06:41Z"
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.361885ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:06:41Z"
    - latency: 2.305755ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:05:41Z"
    - latency: 2.546981ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:04:41Z"
    - latency: 2.195968ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:03:41Z"
    - latency: 2.395803ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:02:41Z"
    - latency: 2.37093ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:01:41Z"
    - latency: 4.167805ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:00:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T15:59:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-161-to-network-check-target-ip-10-0-143-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-161.ec2.internal
      uid: bf9256f7-d4d7-463a-b76d-0c5fa4d61326
    resourceVersion: "24584"
    uid: 1d82d978-1432-4473-a574-e51a62a1347a
  spec:
    sourcePod: network-check-source-6947749cfc-4n6j5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T16:06:41Z"
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.395984ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:06:41Z"
    - latency: 2.251526ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:05:41Z"
    - latency: 2.106545ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:04:41Z"
    - latency: 2.304571ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:03:41Z"
    - latency: 2.64353ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:02:41Z"
    - latency: 2.328279ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:01:41Z"
    - latency: 3.455852ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:00:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T15:59:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-161-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-161.ec2.internal
      uid: bf9256f7-d4d7-463a-b76d-0c5fa4d61326
    resourceVersion: "23949"
    uid: 5fb98f00-cf21-445c-b2ac-a202c98ee71a
  spec:
    sourcePod: network-check-source-6947749cfc-4n6j5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T16:05:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.419µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:05:41Z"
    - latency: 1.655657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:05:41Z"
    - latency: 1.32136ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:04:41Z"
    - latency: 1.795826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:04:41Z"
    - latency: 1.000135ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:03:41Z"
    - latency: 1.689335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:03:41Z"
    - latency: 869.357µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:02:41Z"
    - latency: 2.00665ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:02:41Z"
    - latency: 1.470291ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T16:01:41Z"
    - latency: 1.812565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T16:01:41Z"
kind: List
metadata:
  resourceVersion: ""