ks-installer

ks-installer copied to clipboard

argocd install fail

1

I even don't see argocd namespace ```bash root:3.3.0#k get ns |grep argocd root:3.3.0# ``` ``` Task 'devops' failed: ****************************************************************************************************************************************************** { "counter": 141, "created": "2022-07-02T19:02:34.368339", "end_line": 171, "event": "runner_on_failed", "event_data": {...

usernameisnull

minio arm64 support.

1

I set up the app-store according to the [documentation](https://kubesphere.io/zh/docs/v3.3/pluggable-components/app-store/) and encountered the following problems: minio pods CrashLoopBackOff，After looking at the logs I found the solution. Minio Version: RELEASE.2019-08-07T01-59-21Z This version...

besscroft

ES not running

2

 pod log: 2022-07-01T17:04:29.679302220+08:00 chroot: cannot change root directory to /: Operation not permitted

haitang5445

cluster-configuration.yaml Format is difficult to read and modify parameters https://raw.githubusercontent.com/kubesphere/ks-installer/v3.3.0/deploy/cluster-configuration.yaml the `#` should in top of the yaml values and have a standalone line, otherwise there have Too many words...

willzhang

offline-installation-tool.sh v3.3.0 404

2

https://github.com/kubesphere/ks-installer/releases/download/v3.3.0/offline-installation-tool.sh 404?

Gerrylinux

Current ansible task of install ArgoCD will fail if ArgoCD already installed in cluster. It's reports that some resource already exists. Can we have an option to disable ArgoCD install...

haozileung

install command： ./kk create cluster -f config.yaml result: Failed to pull image "kubespheredev/ks-installer:3.2.1": rpc error: code = Unknown desc = Error response from daemon: manifest for kubespheredev/ks-installer:3.2.1 not found: manifest...

yangyang122

Kubesphere install on existed kubernetes failed

3

I've been trying to install KubeSphere on existed kubernetes. My Kubernetes information below: - kubernetes version: v1.22.8 - Container Runtime: CRI-O - Cluster Environment: Bare-Metal (3Masters VMs / 3 HA...

rupang790

KubeSphere version release tool

1

Now that KubeSphere releases involve many projects, such as kubesphere, console, DevOps, installer, kubekey, we need to have a tool that can manage them all. It only takes one configuration...

zheng1

修改 CRD 中的 ClusterConfiguration 会重置 Prometheus 等监控组件

3

原文：https://kubesphere.com.cn/forum/d/6276-crd-clusterconfiguration-prometheus 简单看了一下 ks-installer pod 的代码和日志，我理解每次修改 CRD 中的 ClusterConfiguration 配置文件，就会将enabled=true 的组件与第一次安装时的初始值进行比较，如果有变化，就会重新安装对应组件。 这个逻辑不对吧？ 我理解应该是这次改动了哪个配置，就重新安装哪个组件，我没有动 Prometheus 相关配置，它就不应该变化呀。 这一次改动的变化，应该与改动前的配置进行比对，为何要与第一次安装时的初始值进行比对，这样设计的考虑是什么？

LeoDemon