apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:07:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-120-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-120.ec2.internal
      uid: 58ccc328-fb81-491b-8d3e-b57abe91134b
    resourceVersion: "22563"
    uid: ccdfa530-c4d4-420d-bdd8-56fd90460664
  spec:
    sourcePod: network-check-source-6f8b768455-7fq5q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:14:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.037654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:14:05Z"
    - latency: 887.847µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:13:05Z"
    - latency: 1.493283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:12:05Z"
    - latency: 928.306µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:11:05Z"
    - latency: 1.078415ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:10:05Z"
    - latency: 1.719494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:09:05Z"
    - latency: 1.182145ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:08:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:07:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-120-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-120.ec2.internal
      uid: 58ccc328-fb81-491b-8d3e-b57abe91134b
    resourceVersion: "21963"
    uid: 3b86e592-bfe4-43c5-b033-49367f35bb15
  spec:
    sourcePod: network-check-source-6f8b768455-7fq5q
    targetEndpoint: a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:13:05Z"
      message: 'load-balancer-api-external: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.330978ms
      message: 'load-balancer-api-external: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:13:05Z"
    - latency: 7.202213ms
      message: 'load-balancer-api-external: resolved host name a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:13:05Z"
    - latency: 4.702076ms
      message: 'load-balancer-api-external: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:12:05Z"
    - latency: 8.08506ms
      message: 'load-balancer-api-external: resolved host name a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:12:05Z"
    - latency: 5.201808ms
      message: 'load-balancer-api-external: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:11:05Z"
    - latency: 9.439923ms
      message: 'load-balancer-api-external: resolved host name a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:11:05Z"
    - latency: 4.770719ms
      message: 'load-balancer-api-external: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:10:05Z"
    - latency: 6.452266ms
      message: 'load-balancer-api-external: resolved host name a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:10:05Z"
    - latency: 4.86132ms
      message: 'load-balancer-api-external: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:09:05Z"
    - latency: 11.979074ms
      message: 'load-balancer-api-external: resolved host name a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:09:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:07:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-120-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-120.ec2.internal
      uid: 58ccc328-fb81-491b-8d3e-b57abe91134b
    resourceVersion: "21962"
    uid: 0d206251-49c4-405f-b838-d61d3908f061
  spec:
    sourcePod: network-check-source-6f8b768455-7fq5q
    targetEndpoint: a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:13:05Z"
      message: 'load-balancer-api-internal: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.466937ms
      message: 'load-balancer-api-internal: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:13:05Z"
    - latency: 7.284468ms
      message: 'load-balancer-api-internal: resolved host name a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:13:05Z"
    - latency: 4.736901ms
      message: 'load-balancer-api-internal: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:12:05Z"
    - latency: 8.220728ms
      message: 'load-balancer-api-internal: resolved host name a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:12:05Z"
    - latency: 5.169181ms
      message: 'load-balancer-api-internal: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:11:05Z"
    - latency: 9.396357ms
      message: 'load-balancer-api-internal: resolved host name a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:11:05Z"
    - latency: 4.552758ms
      message: 'load-balancer-api-internal: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:10:05Z"
    - latency: 6.53459ms
      message: 'load-balancer-api-internal: resolved host name a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:10:05Z"
    - latency: 4.910042ms
      message: 'load-balancer-api-internal: tcp connection to a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:09:05Z"
    - latency: 12.058235ms
      message: 'load-balancer-api-internal: resolved host name a257b85bb664d4da7917a04841049aff-ad1de370fde98dfc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:09:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:07:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-120-to-network-check-target-ip-10-0-131-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-120.ec2.internal
      uid: 58ccc328-fb81-491b-8d3e-b57abe91134b
    resourceVersion: "22561"
    uid: c28d12a3-89b9-4d58-a5db-5284d2054386
  spec:
    sourcePod: network-check-source-6f8b768455-7fq5q
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:14:05Z"
      message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.642292ms
      message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:14:05Z"
    - latency: 1.995924ms
      message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:13:05Z"
    - latency: 2.267887ms
      message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:12:05Z"
    - latency: 1.830177ms
      message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:11:05Z"
    - latency: 2.014527ms
      message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:10:05Z"
    - latency: 2.119674ms
      message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:09:05Z"
    - latency: 2.172937ms
      message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:08:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:07:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-120-to-network-check-target-ip-10-0-132-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-120.ec2.internal
      uid: 58ccc328-fb81-491b-8d3e-b57abe91134b
    resourceVersion: "22560"
    uid: eaafdf71-903e-44b2-af32-d1dcdfb40661
  spec:
    sourcePod: network-check-source-6f8b768455-7fq5q
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:14:05Z"
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.012µs
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:14:05Z"
    - latency: 830.849µs
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:13:05Z"
    - latency: 1.126771ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:12:05Z"
    - latency: 1.066534ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:11:05Z"
    - latency: 870.306µs
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:10:05Z"
    - latency: 1.776742ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:09:05Z"
    - latency: 1.357548ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:08:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:07:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-120-to-network-check-target-ip-10-0-137-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-120.ec2.internal
      uid: 58ccc328-fb81-491b-8d3e-b57abe91134b
    resourceVersion: "22562"
    uid: db2553b4-986a-41aa-95df-f9c17ab1f7a7
  spec:
    sourcePod: network-check-source-6f8b768455-7fq5q
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:14:05Z"
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.055462ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:14:05Z"
    - latency: 2.11999ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:13:05Z"
    - latency: 2.150657ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:12:05Z"
    - latency: 2.129511ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:11:05Z"
    - latency: 2.403102ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:10:05Z"
    - latency: 2.256235ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:09:05Z"
    - latency: 2.337891ms
      message: 'network-check-target-ip-10-0-137-196: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:08:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:07:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-120-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-120.ec2.internal
      uid: 58ccc328-fb81-491b-8d3e-b57abe91134b
    resourceVersion: "21961"
    uid: 7389ba53-9ba3-4ce6-b104-722a6997b08e
  spec:
    sourcePod: network-check-source-6f8b768455-7fq5q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:13:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.622µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:13:05Z"
    - latency: 2.08893ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:13:05Z"
    - latency: 1.191151ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:12:05Z"
    - latency: 2.247096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:12:05Z"
    - latency: 1.015566ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:11:05Z"
    - latency: 1.759196ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:11:05Z"
    - latency: 928.653µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:10:05Z"
    - latency: 1.635745ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:10:05Z"
    - latency: 5.94564ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:09:05Z"
    - latency: 2.035379ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:09:05Z"
kind: List
metadata:
  resourceVersion: ""