apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-68-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-68.ec2.internal
      uid: a6d039a7-2d55-4ea6-b6eb-917c008bb6d3
    resourceVersion: "11811"
    uid: 34627e2c-0e3c-4dba-9153-db8f275d3b91
  spec:
    sourcePod: network-check-source-6f78d59f99-f88gr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.235932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:36Z"
    - latency: 1.073326ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:36Z"
    - latency: 1.476654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:36Z"
    - latency: 1.475483ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:36Z"
    - latency: 1.095057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:36Z"
    - latency: 1.551263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:36Z"
    - latency: 1.695265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:40:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-68-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-68.ec2.internal
      uid: a6d039a7-2d55-4ea6-b6eb-917c008bb6d3
    resourceVersion: "11529"
    uid: 674fff70-d545-4b86-8038-ba63f2cf92a4
  spec:
    sourcePod: network-check-source-6f78d59f99-f88gr
    targetEndpoint: add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:36Z"
      message: 'load-balancer-api-external: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.617908ms
      message: 'load-balancer-api-external: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:36Z"
    - latency: 11.141886ms
      message: 'load-balancer-api-external: resolved host name add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:45:36Z"
    - latency: 16.256162ms
      message: 'load-balancer-api-external: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:36Z"
    - latency: 8.108377ms
      message: 'load-balancer-api-external: resolved host name add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:44:36Z"
    - latency: 16.132024ms
      message: 'load-balancer-api-external: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:36Z"
    - latency: 6.561283ms
      message: 'load-balancer-api-external: resolved host name add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:43:36Z"
    - latency: 15.362555ms
      message: 'load-balancer-api-external: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:36Z"
    - latency: 8.555871ms
      message: 'load-balancer-api-external: resolved host name add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:42:36Z"
    - latency: 16.725223ms
      message: 'load-balancer-api-external: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:36Z"
    - latency: 7.130555ms
      message: 'load-balancer-api-external: resolved host name add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:41:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-68-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-68.ec2.internal
      uid: a6d039a7-2d55-4ea6-b6eb-917c008bb6d3
    resourceVersion: "11528"
    uid: f8759f21-b51a-40d3-b920-b54da185ea26
  spec:
    sourcePod: network-check-source-6f78d59f99-f88gr
    targetEndpoint: add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:36Z"
      message: 'load-balancer-api-internal: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.829909ms
      message: 'load-balancer-api-internal: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:36Z"
    - latency: 11.079068ms
      message: 'load-balancer-api-internal: resolved host name add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:45:36Z"
    - latency: 16.30389ms
      message: 'load-balancer-api-internal: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:36Z"
    - latency: 8.060571ms
      message: 'load-balancer-api-internal: resolved host name add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:44:36Z"
    - latency: 17.372338ms
      message: 'load-balancer-api-internal: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:36Z"
    - latency: 6.482675ms
      message: 'load-balancer-api-internal: resolved host name add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:43:36Z"
    - latency: 16.692254ms
      message: 'load-balancer-api-internal: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:36Z"
    - latency: 8.51319ms
      message: 'load-balancer-api-internal: resolved host name add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:42:36Z"
    - latency: 17.108513ms
      message: 'load-balancer-api-internal: tcp connection to add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:36Z"
    - latency: 7.059785ms
      message: 'load-balancer-api-internal: resolved host name add81325a6bf949fd9003d4040ef1a36-850444752d646ea1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:41:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-68-to-network-check-target-ip-10-0-130-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-68.ec2.internal
      uid: a6d039a7-2d55-4ea6-b6eb-917c008bb6d3
    resourceVersion: "11810"
    uid: 4f462e26-e8e5-42d2-8713-929824ca5121
  spec:
    sourcePod: network-check-source-6f78d59f99-f88gr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:36Z"
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.068647ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:36Z"
    - latency: 2.042561ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:36Z"
    - latency: 2.041798ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:36Z"
    - latency: 2.206929ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:36Z"
    - latency: 2.001261ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:36Z"
    - latency: 2.287913ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:36Z"
    - latency: 2.127128ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:40:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-68-to-network-check-target-ip-10-0-130-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-68.ec2.internal
      uid: a6d039a7-2d55-4ea6-b6eb-917c008bb6d3
    resourceVersion: "11808"
    uid: 51f40298-0bbb-4573-8cb7-823f7231c2ed
  spec:
    sourcePod: network-check-source-6f78d59f99-f88gr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:36Z"
      message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.595µs
      message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:36Z"
    - latency: 989.781µs
      message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:36Z"
    - latency: 1.023651ms
      message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:36Z"
    - latency: 1.340482ms
      message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:36Z"
    - latency: 904.254µs
      message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:36Z"
    - latency: 1.327256ms
      message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:36Z"
    - latency: 2.6049ms
      message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:40:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-68-to-network-check-target-ip-10-0-134-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-68.ec2.internal
      uid: a6d039a7-2d55-4ea6-b6eb-917c008bb6d3
    resourceVersion: "11809"
    uid: 99a2bbc8-d556-46a6-bafa-3d4ba77b91f5
  spec:
    sourcePod: network-check-source-6f78d59f99-f88gr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:36Z"
      message: 'network-check-target-ip-10-0-134-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.85594ms
      message: 'network-check-target-ip-10-0-134-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:36Z"
    - latency: 1.782748ms
      message: 'network-check-target-ip-10-0-134-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:36Z"
    - latency: 2.09934ms
      message: 'network-check-target-ip-10-0-134-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:36Z"
    - latency: 2.190832ms
      message: 'network-check-target-ip-10-0-134-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:36Z"
    - latency: 1.916718ms
      message: 'network-check-target-ip-10-0-134-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:36Z"
    - latency: 1.999828ms
      message: 'network-check-target-ip-10-0-134-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:36Z"
    - latency: 2.51262ms
      message: 'network-check-target-ip-10-0-134-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:40:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-68-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-68.ec2.internal
      uid: a6d039a7-2d55-4ea6-b6eb-917c008bb6d3
    resourceVersion: "11526"
    uid: 4a243be8-6b33-4a65-802c-c931d127d79b
  spec:
    sourcePod: network-check-source-6f78d59f99-f88gr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 825.331µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:36Z"
    - latency: 1.72422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:45:36Z"
    - latency: 987.084µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:36Z"
    - latency: 1.846437ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:44:36Z"
    - latency: 821.599µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:36Z"
    - latency: 1.750062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:43:36Z"
    - latency: 1.110366ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:36Z"
    - latency: 1.848613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:42:36Z"
    - latency: 793.225µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:36Z"
    - latency: 2.210512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:41:36Z"
kind: List
metadata:
  resourceVersion: ""