Offline install kubesphere, many POD initContainers use busybox:latest

[ygqygq2]

Offline install kubesphere, many POD initContainers use busybox:latest imagePullPolicy: Always

Hope to improve in the future.

[zheng1]

Thank you for your feedback

/assign @pixiake

[Juminiy]

please tell me the kubectl edit sts opensearch-cluster-data -n kubesphere-logging-system kubectl edit sts opensearch-cluster-master -n kubesphere-logging-system /busybox

I want to change busybox:latest to our local-harbor address "192.168.31.242:8662/kubesphere-io-centos7/busybox:1.31.1" I wanna to know how to edit the code to write it permanently, I have correct the code to skip the os.RepositoryModule It runs well!!!

[pixiake]

please tell me the kubectl edit sts opensearch-cluster-data -n kubesphere-logging-system kubectl edit sts opensearch-cluster-master -n kubesphere-logging-system /busybox

I want to change busybox:latest to our local-harbor address "192.168.31.242:8662/kubesphere-io-centos7/busybox:1.31.1" I wanna to know how to edit the code to write it permanently, I have correct the code to skip the os.RepositoryModule It runs well!!!

This is due to the fact that the OpenSearch's busybox image parameters are not exposed for centralized management by the ks-installer.

You can get the corresponding version of the ks-installer code, adjust the following two files, and then build image for yourself.

https://github.com/kubesphere/ks-installer/blob/v3.4.1/roles/common/templates/custom-values-opensearch-master.yaml.j2 https://github.com/kubesphere/ks-installer/blob/v3.4.1/roles/common/templates/custom-values-opensearch-data.yaml.j2

persistence:
  enabled: true
  image: {{ busybox_repo }}     # new add
  imageTag: {{ busybox_tag }}   # new add

[Juminiy]

Ok,well done, I'm trying it. thanks!

[Juminiy]

Sorry, we cannot find about how to build image of ks-installer, we don't find out the document in the page of https://github.com/kubesphere/ks-installer , can you state the details more clearly, or give me a doc, I need build and deploy all manually and 100% offline.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.