ks-installer
ks-installer copied to clipboard
Install KubeSphere on existing Kubernetes cluster
 如图, 是因为专有网络IP的问题吗?
i had executed kubesphere-delete.sh of v3.3.0 , but hanged, how to do?? like this: ---------------------------------------------------------- s2ibuildertemplate.devops.kubesphere.io/java patched (no change) s2ibuildertemplate.devops.kubesphere.io/nodejs patched (no change) s2ibuildertemplate.devops.kubesphere.io/python patched (no change) s2ibuildertemplate.devops.kubesphere.io/tomcat patched (no...
kubesphere 3.2.1 k8s:1.20.6 -------------------------- Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1129)'))': /apis/installer.kubesphere.io/v1alpha1/namespaces/kubesphere-system/clusterconfigurations/ks-installer Retrying (Retry(total=1, connect=None, read=None, redirect=None,...
After ks-installer, the helm upgrade directly causes the deploy and cm of kubeedge to be reset to default
I have a k3s (kubesphere lightweight cluster) and I was trying to install kubesphere v3.3.0 on it. the k3s is not very stable, it restarts sometimes, and the ks-installer seems...
cc : ``` apiVersion: installer.kubesphere.io/v1alpha1 kind: ClusterConfiguration metadata: creationTimestamp: "2022-08-18T09:15:54Z" generation: 6 labels: version: v3.3.0 name: ks-installer namespace: kubesphere-system resourceVersion: "2784" uid: c5c8f4cf-9016-4427-8ad1-01b306db0a1a spec: alerting: enabled: false auditing: enabled: false...
```release-note Fixed problems with installing Gatekeeper caused by old Kubernetes API versions. It adapts to different Kubernetes versions (tested with v1.24 and v1.28) and selects the right API version to...
有个中文符号"," 在95行 auditing: # Provide a security-relevant chronological set of records,recording the sequence of activities happening on the platform, initiated by different tenants. 导致 kubectl apply yaml: control characters are...
如何指定安装到特定的node下
jaeger 1.29 使用的是 cronjob的v1beta,但这个已经在k8sv1.25被弃用了,至少需要升级jaeger到1.34,但v1.26里autoscaling v2beta2也废弃了,所以要升级jaeger到v1.38。。。