apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:29:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-77-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-77.ec2.internal
      uid: 4db2f2c8-71eb-4683-b18f-30235342f943
    resourceVersion: "23644"
    uid: 32758fe1-85e4-47e2-81af-f76b2b37f1d2
  spec:
    sourcePod: network-check-source-65bdbbff45-2ttzf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T19:36:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.702µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:36:38Z"
    - latency: 905.318µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:38Z"
    - latency: 844.129µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:38Z"
    - latency: 928.27µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:33:38Z"
    - latency: 1.083101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:32:38Z"
    - latency: 1.32196ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:31:38Z"
    - latency: 847.052µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:30:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:29:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-77-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-77.ec2.internal
      uid: 4db2f2c8-71eb-4683-b18f-30235342f943
    resourceVersion: "22573"
    uid: 5135480c-57b4-4492-b638-9f3240184d8a
  spec:
    sourcePod: network-check-source-65bdbbff45-2ttzf
    targetEndpoint: a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T19:35:38Z"
      message: 'load-balancer-api-external: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.038137ms
      message: 'load-balancer-api-external: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:38Z"
    - latency: 9.214903ms
      message: 'load-balancer-api-external: resolved host name a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:35:38Z"
    - latency: 3.89781ms
      message: 'load-balancer-api-external: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:38Z"
    - latency: 9.352919ms
      message: 'load-balancer-api-external: resolved host name a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:34:38Z"
    - latency: 5.423581ms
      message: 'load-balancer-api-external: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:33:38Z"
    - latency: 11.253038ms
      message: 'load-balancer-api-external: resolved host name a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:33:38Z"
    - latency: 5.847239ms
      message: 'load-balancer-api-external: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:32:38Z"
    - latency: 12.817889ms
      message: 'load-balancer-api-external: resolved host name a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:32:38Z"
    - latency: 5.858417ms
      message: 'load-balancer-api-external: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:31:38Z"
    - latency: 18.805215ms
      message: 'load-balancer-api-external: resolved host name a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:31:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:29:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-77-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-77.ec2.internal
      uid: 4db2f2c8-71eb-4683-b18f-30235342f943
    resourceVersion: "22572"
    uid: 83a546ad-1b84-4157-bcc1-5398df915ce8
  spec:
    sourcePod: network-check-source-65bdbbff45-2ttzf
    targetEndpoint: a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T19:35:38Z"
      message: 'load-balancer-api-internal: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.301391ms
      message: 'load-balancer-api-internal: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:38Z"
    - latency: 9.156289ms
      message: 'load-balancer-api-internal: resolved host name a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:35:38Z"
    - latency: 3.466752ms
      message: 'load-balancer-api-internal: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:38Z"
    - latency: 9.262947ms
      message: 'load-balancer-api-internal: resolved host name a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:34:38Z"
    - latency: 5.419458ms
      message: 'load-balancer-api-internal: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:33:38Z"
    - latency: 11.051462ms
      message: 'load-balancer-api-internal: resolved host name a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:33:38Z"
    - latency: 5.827354ms
      message: 'load-balancer-api-internal: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:32:38Z"
    - latency: 12.788049ms
      message: 'load-balancer-api-internal: resolved host name a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:32:38Z"
    - latency: 5.905017ms
      message: 'load-balancer-api-internal: tcp connection to a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:31:38Z"
    - latency: 18.211538ms
      message: 'load-balancer-api-internal: resolved host name a0da026a3d0204aa996df151f0364ff5-d16173b53ea005df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:31:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:29:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-77-to-network-check-target-ip-10-0-128-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-77.ec2.internal
      uid: 4db2f2c8-71eb-4683-b18f-30235342f943
    resourceVersion: "23643"
    uid: 023c4e2b-d79f-460f-bd44-045c0cb93bf3
  spec:
    sourcePod: network-check-source-65bdbbff45-2ttzf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T19:36:38Z"
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.414163ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:36:38Z"
    - latency: 2.329152ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:38Z"
    - latency: 2.175108ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:38Z"
    - latency: 2.248269ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:33:38Z"
    - latency: 2.338204ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:32:38Z"
    - latency: 2.521052ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:31:38Z"
    - latency: 2.501642ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:30:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:29:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-77-to-network-check-target-ip-10-0-132-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-77.ec2.internal
      uid: 4db2f2c8-71eb-4683-b18f-30235342f943
    resourceVersion: "23641"
    uid: d3cd296d-5e7c-478f-a1f9-c8f5cb08e8e7
  spec:
    sourcePod: network-check-source-65bdbbff45-2ttzf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T19:36:38Z"
      message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 874.878µs
      message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:36:38Z"
    - latency: 972.98µs
      message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:38Z"
    - latency: 856.431µs
      message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:38Z"
    - latency: 885.74µs
      message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:33:38Z"
    - latency: 862.82µs
      message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:32:38Z"
    - latency: 5.178639ms
      message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:31:38Z"
    - latency: 1.279037ms
      message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:30:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:29:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-77-to-network-check-target-ip-10-0-136-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-77.ec2.internal
      uid: 4db2f2c8-71eb-4683-b18f-30235342f943
    resourceVersion: "23642"
    uid: 874d8e90-2c1e-4c04-8d49-16bd820d103a
  spec:
    sourcePod: network-check-source-65bdbbff45-2ttzf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T19:36:38Z"
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.358853ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:36:38Z"
    - latency: 2.310859ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:38Z"
    - latency: 2.399606ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:38Z"
    - latency: 2.583649ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:33:38Z"
    - latency: 2.39374ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:32:38Z"
    - latency: 5.995584ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:31:38Z"
    - latency: 2.529853ms
      message: 'network-check-target-ip-10-0-136-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:30:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T19:29:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-77-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-77.ec2.internal
      uid: 4db2f2c8-71eb-4683-b18f-30235342f943
    resourceVersion: "22571"
    uid: 7b0983f5-083c-4e99-91be-3723eb2c7f98
  spec:
    sourcePod: network-check-source-65bdbbff45-2ttzf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T19:35:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.904µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:38Z"
    - latency: 1.763693ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:35:38Z"
    - latency: 887.642µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:38Z"
    - latency: 1.75698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:34:38Z"
    - latency: 1.012095ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:33:38Z"
    - latency: 2.193586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:33:38Z"
    - latency: 858.934µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:32:38Z"
    - latency: 1.672698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:32:38Z"
    - latency: 1.182922ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:31:38Z"
    - latency: 5.234847ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:31:38Z"
kind: List
metadata:
  resourceVersion: ""