apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T10:58:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-159-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-159.ec2.internal
      uid: c2e5a125-96f9-40e2-8ab7-303b1688e1d3
    resourceVersion: "24162"
    uid: 9abd1863-0bd5-4a6f-8312-a6ceb55ac00a
  spec:
    sourcePod: network-check-source-6947749cfc-q8cbn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T11:05:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.594µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:05:38Z"
    - latency: 1.146089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:04:38Z"
    - latency: 1.099714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:03:38Z"
    - latency: 1.501243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:02:38Z"
    - latency: 1.288041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:01:38Z"
    - latency: 991.327µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:00:38Z"
    - latency: 1.329334ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T10:59:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T10:58:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-159-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-159.ec2.internal
      uid: c2e5a125-96f9-40e2-8ab7-303b1688e1d3
    resourceVersion: "28296"
    uid: 12cc8c5c-e728-44c4-b2e8-675fd3c62175
  spec:
    sourcePod: network-check-source-6947749cfc-q8cbn
    targetEndpoint: a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T11:04:38Z"
      message: 'load-balancer-api-external: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.336932ms
      message: 'load-balancer-api-external: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:10:38Z"
    - latency: 7.532513ms
      message: 'load-balancer-api-external: resolved host name a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:10:38Z"
    - latency: 4.90643ms
      message: 'load-balancer-api-external: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:09:38Z"
    - latency: 10.717415ms
      message: 'load-balancer-api-external: resolved host name a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:09:38Z"
    - latency: 5.025843ms
      message: 'load-balancer-api-external: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:08:38Z"
    - latency: 8.041364ms
      message: 'load-balancer-api-external: resolved host name a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:08:38Z"
    - latency: 5.041943ms
      message: 'load-balancer-api-external: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:07:38Z"
    - latency: 7.837529ms
      message: 'load-balancer-api-external: resolved host name a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:07:38Z"
    - latency: 4.134809ms
      message: 'load-balancer-api-external: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:06:38Z"
    - latency: 9.661706ms
      message: 'load-balancer-api-external: resolved host name a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:06:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T10:58:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-159-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-159.ec2.internal
      uid: c2e5a125-96f9-40e2-8ab7-303b1688e1d3
    resourceVersion: "28297"
    uid: 84417517-2a45-46d4-975c-96aea2a3c405
  spec:
    sourcePod: network-check-source-6947749cfc-q8cbn
    targetEndpoint: a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T11:04:38Z"
      message: 'load-balancer-api-internal: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.356718ms
      message: 'load-balancer-api-internal: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:10:38Z"
    - latency: 7.603946ms
      message: 'load-balancer-api-internal: resolved host name a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:10:38Z"
    - latency: 4.838022ms
      message: 'load-balancer-api-internal: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:09:38Z"
    - latency: 10.728753ms
      message: 'load-balancer-api-internal: resolved host name a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:09:38Z"
    - latency: 4.336601ms
      message: 'load-balancer-api-internal: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:08:38Z"
    - latency: 8.081512ms
      message: 'load-balancer-api-internal: resolved host name a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:08:38Z"
    - latency: 5.072792ms
      message: 'load-balancer-api-internal: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:07:38Z"
    - latency: 7.878671ms
      message: 'load-balancer-api-internal: resolved host name a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:07:38Z"
    - latency: 5.601532ms
      message: 'load-balancer-api-internal: tcp connection to a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:06:38Z"
    - latency: 9.757183ms
      message: 'load-balancer-api-internal: resolved host name a94fceca490344b188b095aacb5f3fa1-5c146c781c85dc6e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:06:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T10:58:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-159-to-network-check-target-ip-10-0-132-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-159.ec2.internal
      uid: c2e5a125-96f9-40e2-8ab7-303b1688e1d3
    resourceVersion: "24161"
    uid: be90f818-cfe4-4305-947a-9e02f434cecd
  spec:
    sourcePod: network-check-source-6947749cfc-q8cbn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T11:05:38Z"
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.243949ms
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:05:38Z"
    - latency: 2.374564ms
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:04:38Z"
    - latency: 2.363576ms
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:03:38Z"
    - latency: 2.644267ms
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:02:38Z"
    - latency: 2.121037ms
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:01:38Z"
    - latency: 2.220495ms
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:00:38Z"
    - latency: 2.833626ms
      message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T10:59:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T10:58:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-159-to-network-check-target-ip-10-0-137-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-159.ec2.internal
      uid: c2e5a125-96f9-40e2-8ab7-303b1688e1d3
    resourceVersion: "24159"
    uid: 0d74e471-b257-4614-b1ba-12ff19a20e8a
  spec:
    sourcePod: network-check-source-6947749cfc-q8cbn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T11:05:38Z"
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 818.884µs
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:05:38Z"
    - latency: 806.673µs
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:04:38Z"
    - latency: 1.192621ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:03:38Z"
    - latency: 926.262µs
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:02:38Z"
    - latency: 937.762µs
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:01:38Z"
    - latency: 1.561474ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:00:38Z"
    - latency: 1.021762ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T10:59:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T10:58:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-159-to-network-check-target-ip-10-0-139-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-159.ec2.internal
      uid: c2e5a125-96f9-40e2-8ab7-303b1688e1d3
    resourceVersion: "24160"
    uid: dbac2e65-2ec8-4f6a-b7d8-6eda821686f0
  spec:
    sourcePod: network-check-source-6947749cfc-q8cbn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T11:05:38Z"
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.330876ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:05:38Z"
    - latency: 2.060448ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:04:38Z"
    - latency: 2.333815ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:03:38Z"
    - latency: 2.404807ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:02:38Z"
    - latency: 2.877486ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:01:38Z"
    - latency: 2.162073ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:00:38Z"
    - latency: 2.30336ms
      message: 'network-check-target-ip-10-0-139-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T10:59:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T10:58:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-159-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-159.ec2.internal
      uid: c2e5a125-96f9-40e2-8ab7-303b1688e1d3
    resourceVersion: "28295"
    uid: 1503dd22-a5ed-4db7-afe4-866d07c540c7
  spec:
    sourcePod: network-check-source-6947749cfc-q8cbn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T11:04:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 843.425µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:10:38Z"
    - latency: 1.691595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:10:38Z"
    - latency: 847.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:09:38Z"
    - latency: 1.739903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:09:38Z"
    - latency: 1.317377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:08:38Z"
    - latency: 1.789047ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:08:38Z"
    - latency: 882.19µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:07:38Z"
    - latency: 1.613097ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:07:38Z"
    - latency: 1.012602ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T11:06:38Z"
    - latency: 1.884809ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T11:06:38Z"
kind: List
metadata:
  resourceVersion: ""