kplcloud / cloud-website

开普勒云平台的教程文档

Introduction

开普勒使用教程

本教程主要围绕 Kplcloud 的安装，集成发布。

教程由 宜人金科-财富技术部-创新团队 提供技术支持

Kplcloud是什么?

kplcloud是一个基于Kubernetes的轻量级PaaS平台，通过可视化的界面对应用进行管理，降低应用容器化的对度，从而减少应用容器化的时间成本。

Kplcloud已在服务于宜人财富多个团队，稳定运行了近两年，目前平台已在生产环境跑着上百个应用，近千个容器。

本地启动文档库

1. 克隆

   $ git clone https://github.com/kplcloud/cloud-website.git

2. Docker启动

   $ docker build --rm -t cloud-website .
   $ docker run -it --rm -p 80:80 cloud-website

3. 访问 浏览器打开http://localhost即可访问。

cloud-website's Issues

install/kubernetes/namespace.yaml以及下面的文件在哪里能获取到呢？

git clone下来没有找到黎明有部署的文件呢？
install/kubernetes/namespace.yaml以及下面的文件在哪里能获取到呢？

kpaas部署报错

[root@master kpaas]# kubectl logs kplcloud-669d79f464-9v24q -f
panic: Exception (403) Reason: "username or password not allowed"

goroutine 1 [running]:
github.com/kplcloud/kplcloud/cmd/server.run()
/go/src/github.com/kplcloud/kplcloud/cmd/server/server.go:177 +0x7312
github.com/kplcloud/kplcloud/cmd/server.glob..func1(0x28bad00, 0xc00007eb40, 0x0, 0x6, 0x0, 0x0)
/go/src/github.com/kplcloud/kplcloud/cmd/server/server.go:118 +0x20
github.com/spf13/cobra.(*Command).execute(0x28bad00, 0xc00007ea20, 0x6, 0x6, 0x28bad00, 0xc00007ea20)
/go/pkg/mod/github.com/spf13/[email protected]/command.go:826 +0x460
github.com/spf13/cobra.(*Command).ExecuteC(0x28baa80, 0x0, 0x0, 0x0)
/go/pkg/mod/github.com/spf13/[email protected]/command.go:914 +0x2fb
github.com/spf13/cobra.(*Command).Execute(...)
/go/pkg/mod/github.com/spf13/[email protected]/command.go:864
github.com/kplcloud/kplcloud/cmd/server.Run()
/go/src/github.com/kplcloud/kplcloud/cmd/server/server.go:138 +0x2d
main.main()
/go/src/github.com/kplcloud/kplcloud/main.go:13 +0x20
请问，这里的的用户名或者密码是指的哪里的呢？

es error

[root@master elk]# kubectl get pods
NAME READY STATUS RESTARTS AGE
centos-569c9576f9-g5p6p 1/1 Running 3 17d
consul-server-0 1/1 Running 0 55m
consul-server-1 1/1 Running 0 55m
consul-server-2 1/1 Running 0 55m
es-master-0 1/1 Running 3 2m45s
es-master-1 1/1 Running 0 2m39s
es-master-2 1/1 Running 1 2m11s
mysql-0 1/1 Running 0 39m
rabbitmq-0 1/1 Running 0 36m
redis-0 1/1 Running 0 67m
[root@master elk]# kubectl get pods^C
[root@master elk]# kubectl logs es-master-0 -f
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
[root@master elk]# kubectl get pods
NAME READY STATUS RESTARTS AGE
centos-569c9576f9-g5p6p 1/1 Running 3 17d
consul-server-0 1/1 Running 0 56m
consul-server-1 1/1 Running 0 56m
consul-server-2 1/1 Running 0 56m
es-master-0 0/1 CrashLoopBackOff 4 4m7s
es-master-1 1/1 Running 0 4m1s
es-master-2 1/1 Running 1 3m33s
mysql-0 1/1 Running 0 40m
rabbitmq-0 1/1 Running 0 37m
redis-0 1/1 Running 0 69m
[root@master elk]# kubectl logs es-master-0 -f
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
[root@master elk]# kubectl logs es-master-0 -f
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.

麻烦给点解决问题的思路，谢谢。

logstash error

[root@master elk]# kubectl logs logstash-684678f76f-vt8vl
2019/11/12 11:16:13 Setting 'xpack.monitoring.elasticsearch.url' from environment.
OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N
[root@master elk]# kubectl logs logstash-684678f76f-vt8vl -f
2019/11/12 11:16:13 Setting 'xpack.monitoring.elasticsearch.url' from environment.
OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N
Sending Logstash logs to /usr/share/logstash/logs which is now configured via log4j2.properties
[2019-11-12T03:16:54,303][INFO ][logstash.setting.writabledirectory] Creating directory {:setting=>"path.queue", :path=>"/usr/share/logstash/data/queue"}
[2019-11-12T03:16:54,345][INFO ][logstash.setting.writabledirectory] Creating directory {:setting=>"path.dead_letter_queue", :path=>"/usr/share/logstash/data/dead_letter_queue"}
[2019-11-12T03:16:54,367][WARN ][logstash.runner ] Deprecated setting xpack.monitoring.elasticsearch.url please use xpack.monitoring.elasticsearch.hosts
[2019-11-12T03:16:55,421][INFO ][logstash.runner ] Starting Logstash {"logstash.version"=>"6.8.0"}
[2019-11-12T03:16:55,495][INFO ][logstash.agent ] No persistent UUID file found. Generating new UUID {:uuid=>"28374669-6859-4779-bff1-8178fd93e461", :path=>"/usr/share/logstash/data/uuid"}
[2019-11-12T03:16:56,925][WARN ][logstash.monitoringextension.pipelineregisterhook] xpack.monitoring.enabled has not been defined, but found elasticsearch configuration. Please explicitly set xpack.monitoring.enabled: true in logstash.yml
[2019-11-12T03:16:59,324][INFO ][logstash.licensechecker.licensereader] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[http://elasticsearch:9200/]}}
[2019-11-12T03:17:00,037][WARN ][logstash.licensechecker.licensereader] Restored connection to ES instance {:url=>"http://elasticsearch:9200/"}
[2019-11-12T03:17:00,258][INFO ][logstash.licensechecker.licensereader] ES Output version determined {:es_version=>6}
[2019-11-12T03:17:00,270][WARN ][logstash.licensechecker.licensereader] Detected a 6.x and above cluster: the type event field won't be used to determine the document _type {:es_version=>6}
[2019-11-12T03:17:00,655][INFO ][logstash.monitoring.internalpipelinesource] Monitoring License OK
[2019-11-12T03:17:00,665][INFO ][logstash.monitoring.internalpipelinesource] Validated license for monitoring. Enabling monitoring pipeline.
[2019-11-12T03:17:02,444][ERROR][logstash.agent ] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"LogStash::ConfigurationError", :message=>"Expected one of #, {, } at line 23, column 56 (byte 544) after output{\n elasticsearch {\n hosts => ["elasticsearch:9200"]\n index => "kpl-%{[fields][app_name]}-%{+YYYY.MM.dd}"", :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:41:in compile_imperative'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:49:in compile_graph'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:11:in block in compile_sources'", "org/jruby/RubyArray.java:2577:in map'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:10:in compile_sources'", "org/logstash/execution/AbstractPipelineExt.java:151:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:22:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:90:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:43:in block in execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:96:in block in exclusive'", "org/jruby/ext/thread/Mutex.java:165:in synchronize'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:96:in exclusive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:39:in execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:334:in block in converge_state'"]}
[2019-11-12T03:17:11,541][WARN ][logstash.outputs.elasticsearch] You are using a deprecated config setting "document_type" set in elasticsearch. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. Document types are being deprecated in Elasticsearch 6.0, and removed entirely in 7.0. You should avoid this feature If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=>"document_type", :plugin=><LogStash::Outputs::ElasticSearch bulk_path=>"/_xpack/monitoring/_bulk?system_id=logstash&system_api_version=6&interval=1s", hosts=>[//elasticsearch:9200], sniffing=>false, manage_template=>false, id=>"34997036476b33271a1e1df32dbba71befed9f26e87a284c9309e0d7aed4f7a4", document_type=>"%{[@metadata][document_type]}", enable_metric=>true, codec=><LogStash::Codecs::Plain id=>"plain_96577a5d-30fd-47a0-bc7b-de6a2d7b0ff4", enable_metric=>true, charset=>"UTF-8">, workers=>1, template_name=>"logstash", template_overwrite=>false, doc_as_upsert=>false, script_type=>"inline", script_lang=>"painless", script_var_name=>"event", scripted_upsert=>false, retry_initial_interval=>2, retry_max_interval=>64, retry_on_conflict=>1, ilm_enabled=>false, ilm_rollover_alias=>"logstash", ilm_pattern=>"{now/d}-000001", ilm_policy=>"logstash-policy", action=>"index", ssl_certificate_verification=>true, sniffing_delay=>5, timeout=>60, pool_max=>1000, pool_max_per_route=>100, resurrect_delay=>5, validate_after_inactivity=>10000, http_compression=>false>}
[2019-11-12T03:17:11,710][INFO ][logstash.pipeline ] Starting pipeline {:pipeline_id=>".monitoring-logstash", "pipeline.workers"=>1, "pipeline.batch.size"=>2, "pipeline.batch.delay"=>50}
[2019-11-12T03:17:12,088][INFO ][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[http://elasticsearch:9200/]}}
[2019-11-12T03:17:12,157][ERROR][logstash.agent ] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"LogStash::ConfigurationError", :message=>"Expected one of #, {, } at line 23, column 56 (byte 544) after output{\n elasticsearch {\n hosts => ["elasticsearch:9200"]\n index => "kpl-%{[fields][app_name]}-%{+YYYY.MM.dd}"", :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:41:in compile_imperative'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:49:in compile_graph'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:11:in block in compile_sources'", "org/jruby/RubyArray.java:2577:in map'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:10:in compile_sources'", "org/logstash/execution/AbstractPipelineExt.java:151:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:22:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:90:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:43:in block in execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:96:in block in exclusive'", "org/jruby/ext/thread/Mutex.java:165:in synchronize'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:96:in exclusive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:39:in execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:334:in block in converge_state'"]}
[2019-11-12T03:17:12,184][WARN ][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=>"http://elasticsearch:9200/"}
[2019-11-12T03:17:12,208][INFO ][logstash.outputs.elasticsearch] ES Output version determined {:es_version=>6}
[2019-11-12T03:17:12,209][WARN ][logstash.outputs.elasticsearch] Detected a 6.x and above cluster: the type event field won't be used to determine the document _type {:es_version=>6}
[2019-11-12T03:17:12,388][INFO ][logstash.outputs.elasticsearch] New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>["//elasticsearch:9200"]}
[2019-11-12T03:17:12,643][INFO ][logstash.pipeline ] Pipeline started successfully {:pipeline_id=>".monitoring-logstash", :thread=>"#<Thread:0x4c2a9806 run>"}
[2019-11-12T03:17:13,559][INFO ][logstash.agent ] Successfully started Logstash API endpoint {:port=>9600}
[2019-11-12T03:17:19,285][INFO ][logstash.pipeline ] Pipeline has terminated {:pipeline_id=>".monitoring-logstash", :thread=>"#<Thread:0x4c2a9806 run>"}
[2019-11-12T03:17:19,298][INFO ][logstash.runner ] Logstash shut down.

麻烦提示下是哪里的问题呢？

kpass的deployment.yaml文件有问题

以下是修改好的。
kind: Deployment
apiVersion: apps/v1
metadata:
name: kplcloud
labels:
app: kplcloud
language: Golang
spec:
replicas: 1
selector:
matchLabels:
app: kplcloud
strategy:
rollingUpdate:
maxSurge: 1
maxUnavailable: 1
type: RollingUpdate
template:
metadata:
labels:
app: kplcloud
name: kplcloud
spec:
serviceAccountName: kplcloud
volumes:
- name: "tz-config"
hostPath:
path: "/usr/share/zoneinfo/Asia/Shanghai"
- name: kplcloud
configMap:
name: kplcloud
imagePullSecrets:
- name: regcred
containers:
- image: kplcloud/kplcloud
name: kplcloud
ports:
- name: http
containerPort: 8080
command:
- /go/bin/kplcloud
- start
args:
- -p
- :8080
- -c
- /etc/kplcloud/app.cfg
- -k
- /etc/kplcloud/config.yaml
resources:
requests:
memory: 128Mi
limits:
memory: 256Mi
env:
- name: POD_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.namespace
- name: INSTANCE_IP
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: status.podIP
volumeMounts:
- name: tz-config
mountPath: /etc/localtime
- name: kplcloud
mountPath: /etc/kplcloud/app.cfg
readOnly: true
subPath: app.cfg
- name: kplcloud
mountPath: /etc/kplcloud/config.yaml
readOnly: true
subPath: config.yaml
livenessProbe:
failureThreshold: 3
httpGet:
path: /metrics
port: 8080
scheme: HTTP
initialDelaySeconds: 30
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 30
在最后的健康检查有没有对齐+ 协议应该是大写