This message was deleted.
# harvester
a
This message was deleted.
g
i am currently caught up with a few things but i will try and get you the manifests we use
we just use upstream tink-stack.. and it creates the tink-stack service
r
There seems to be a large re-organization/refactoring recently. Almost all of the subcomponent repositories are going to be archived and sourced into the tinkerbell/tinkerbell repository.
a
I am not sure but smee component now supporting multiple configurations like auto-proxy, proxy which can ease out different deployment scenarios. I am not sure if this configurations are still possible on version v0.4.2. Thanks a lot for heads up!
@great-bear-19718, What do you mean by upstream chart? Chart.lock: and Chart.yaml and my Values:
Copy code
dependencies:
- name: stack
  repository: file://../tinkerbell-stack
  version: 0.4.2
digest: sha256:6072bf4caacab819446b69ead18b8cf5beb8d474e0fc26e6e933dcba6d0a5ad7
generated: "2025-08-06T13:10:38.26094976+02:00"
------
.
.
.
maintainers:
  - name: harvester

dependencies:
  - name: stack
    repository: file://../tinkerbell-stack
    version: 0.4.2
--------
# values/seeder.yaml
image:
  repository: rancher/harvester-seeder
cluster:
  imageURL: "http://###ZARF_VAR_K3S_HOST_IP###:32200"
  version: "###ZARF_CONST_HARVESTER_VERSION###"
stack:
  publicIP: "###ZARF_VAR_K3S_HOST_IP###"
----- 
(POD CIDR default)
Afterwards: I got these objects with error on harvester-seeder pod saying no tink-stack service.
After some tinkering, I was able to provision Harvester without using seeder with just tinkerbell.