erda-project / erda

An enterprise-grade Cloud-Native application platform for Kubernetes.

An enterprise-grade Cloud-Native application platform

Introduction | Quick Start | Installation | Documentation | CHANGELOG | Contributing

Demo

Introduction

Erda is an open-source platform created by Terminus to ensure the development of microservice applications. It provides DevOps, microservice governance, and multi-cloud management capabilities. The multi-cloud architecture based on Kubernetes and application-centric DevOps and microservice governance can make the development, operation, monitoring, and problem diagnosis of complex business applications simpler and more efficient.

Functional Architecture

Erda is mainly composed of the following parts:

• DevOps
• Microservice Governance, including Application Performance Management, Monitoring, Log Analysis, API Gateway, etc.
• Multi-Cloud Management
• Edge Computing
• FastData Management

Vision: Build any application, Deploy anywhere, Monitor anything

Architecture

The Erda project consists of multiple repsitories according to different functions. The key repositories are erda, erda-ui, erda-proto, erda-infra, erda-actions, erda-addons.

erda

It is the core repository that implements all the RESTful and gRPC interfaces of the backend services of Erda platform by multiple components in microservice architecture.

erda-ui

It is the graphical user portal of Erda platform built with React with the help of which users can work upon Erda platform very easily. It talks with erda backend services in RESTful APIs.

erda-proto

It defines a part of the communication protocols among erda backend services using Protocol Buffers. All the other protocols among erda backend services will be migrated here in the near future.

erda-infra

It is a lightweight microservices framework implements by golang. It provides many popular middleware providers such as Redis, KafKa, etcd, etc., so that developers can build a module-driven application quickly with help of it. It is also integrated into almost all the backend components in erda.

erda-actions

It holds the definition for the official Pipeline Actions of the Erda Action Marketplace as found at https://www.erda.cloud/market/action. A Pipeline Action plays as a mininal runnable unit in Erda Pipelines such as checking out source code in github, buiding a docker image, creating a deployment in a Kubernetes cluster etc.

erda-addons

It holds the definition for the official Addons of the Erda Addon Marketplace as found at https://www.erda.cloud/market/addon. An Addon holds the configration of a middleware like MySQL, Redis, etc. or a third-party service and it can be shared to different environments of applications, so that developers would not need to import the same configurations again and again in different environments.

There are some extra repositories that plays as customized third-partiy independent components and tools in Erda project such as

• erda-proto-go generated code for Erda protobuf data modals and protocols.
• erda-analyzer is the streaming aggregator for metrics and alert data.
• erda-java-agent is the apm java agent in Erda platform.
• telegraf is the plugin-driven server agent for collecting & reporting metrics.
• kubeprober is a large-scale Kubernetes cluster diagnostic tool.
• beats is the lightweight shippers for Elasticsearch & Logstash.
• remotedialer is a reverse tunneling dialer.
• erda-bot is the bot handing Github webhooks.

Quick Start

To get started, see Local installation.

Installation

Erda can be deployed in either a single node or multi-node setup. Please download binaries of Erda release and follow Installation & Configuration Guide to install Erda.

User Manual

To start using Erda, please refer to the following documentation.

• English
• 简体中文

Contributing

Contributions are always welcomed. Please refer to Contributing to Erda for details.

Contact Us

If you have any questions, please feel free to contact us.

• Email: [email protected]

• Twitter: @ErdaProject

• Zhihu：Erda技术团队 (A Chinese knowledge community, similar to Quora.)

• WeChat Official Account:

  

• DingTalk Group:

  

License

Erda is under the Apache 2.0 license. See the LICENSE file for details.

erda's Issues

pipelineyml parser adjust visitor_snippet.go

What would you like to be added:

this file will be delete totally soon. after all modules migrate to erda, then adjust it, move const like SnippetLogo to configurations.

用helm最小化安装，job任务失败

都是国人，我就不写英文了

安装的时候，我看启动了一个job，但是它执行失败，日志如下：

Waiting for generate ssl files for etcd...
panic: Error creating etcd secrets: can not detect secret erda-etcd-server-secret in namespace erda-system exist or not

goroutine 1 [running]:
main.createEtcdSecretsByK8sClient(0xc00035cb00, 0x1516e43, 0x19)
	/Users/tianxiang.liu/work/go/wip-erda-release/erda-helm/etcd_ssl/etcd_ssl.go:120 +0xc0f
main.main()
	/Users/tianxiang.liu/work/go/wip-erda-release/erda-helm/etcd_ssl/etcd_ssl.go:48 +0x9a

这是helm包里面的内容吧，我找到了那个etcd_ssl.go的文件，看来是创建 secret失败了，createEtcdSecretsByK8sClient这个方法。

我看了这个job镜像的Entrypoint

"Entrypoint": [
                "/bin/sh",
                "-c",
                "/opt/etcd_ssl/etcd_ssl"
            ],

这是把erda-release项目中，etcd-ssl的文件打成了job镜像吧，大致看了一下代码，之前有个读取文件的
createEtcdSecretsByK8sClient(clientset, "./etcd-server-secret.yaml") 总感觉这个有问题，这个路径难道不应该是./templates/etcd-client-secret.yaml 吗？不过看代码，检查的步骤都是通过的，是执行
_, err = cli.CoreV1().Secrets(secret.Namespace).Get(context.TODO(), secret.Name, metav1.GetOptions{})

进到了这个逻辑中，panic了

if errors.IsNotFound(err) {
	_, err = cli.CoreV1().Secrets(secret.Namespace).Create(context.TODO(), &secret, metav1.CreateOptions{})
	if err != nil {
		panic(err.Error())
	}
	fmt.Printf("Create secret %s in namespace %s by file %s successfully.\n", secret.Name, secret.Namespace, filename)
} else if err != nil {
	panic(fmt.Errorf("Error creating etcd secrets: can not detect secret %s in namespace %s exist or not", secret.Name, secret.Namespace).Error())
}

我测试了 v1.5 v1.4 都是不行的，求助一下

补充一下环境：
centos 8，内核 4.18，k8s 1.19.6

启动erda 到anlanyer后 系统iowait 飚高, etcd被打挂

集群配置 1master 3node , PS master也是Node , 4c 14G

devops平台，项目协同

我有个想法，看板那里，我把任务拖到已完成，能不能就顺便加上部署的操作，拖进来就自动完成部署，应该就很完美了

微服务观测项目的基本设置里可以新建一个devops应用

What happened:

微服务观测项目的基本设置里可以新建一个devops应用，对这个应用新建流水线时，报错提示（ 创建流水线失败: 异常 创建流水线失败: 缺少参数 clusterName）

What you expected to happen:

应该新建流水线成功，微信群里沟通后，刘浩杨老师说这个是功能上的bug，这个功能不用应该出现，应该隔离起来，看不到才对。

How to reproduce it (as minimally and precisely as possible):

1. 新建微服务观测项目
2. 点击微服务观测项目的基本设置，在基本设置里添加应用，
3. 新建好应用后，就可以在 devops 里看到新建的应用，然后编写 pipelie.xml 文件。
4. 对这个应用新建流水线，就会有报错提示（ 创建流水线失败: 异常 创建流水线失败: 缺少参数 clusterName）

Anything else we need to know?:

新手理解客观测项目的使用难度太大，我以为客观测的程序对语言是不限的，搞的我一头雾水。请在完善下文档，并在其中体现下 erda 平台可以自动观测到项目，不需要额外配置，但是目前只支持java和nodejs项目。期望能够观测到 python 项目

Environment:

• Erda version: 1.4
• Kubernetes version (use kubectl version): v1.21.7
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
  NAME="Ubuntu"
  VERSION="18.04.5 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.5 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/"
  SUPPORT_URL="https://help.ubuntu.com/"
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
• Kernel (e.g. uname -a): 62~18.04.1-Ubuntu SMP Fri Oct 22 21:51:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
• Network plugin and version (if this is a network-related bug):
• Others:

Join the cluster, display the node memory resource error

After adding the cluster, it is found that the memory resource of the display server is too small, which is not equal to the actual memory resource.

部署说明中关于helm install，需要提示请到主目录中

What happened:

按照此安装说明来安装，在安装子章节的第3步中，有一个通过 Helm 安装 Erda Helm 包的步骤，但是直接输入helm install 命令会报以下错误:

# helm install package/erda-base-0.1.0.tgz --generate-name
Error: failed to download "package/erda-base-0.1.0.tgz" (hint: running `helm repo update` may help)

What you expected to happen:

期望安装成功。

这里是因为必须在erda这个文件夹中进行安装导致的。而安装途中变更了目录。

How to reproduce it (as minimally and precisely as possible):

安装好k8s之后，按照此安装说明进行操作即可。

Anything else we need to know?:

Environment:

• Erda version: v1.0.0
• Kubernetes version (use kubectl version): v1.21.0
• Cloud provider or hardware configuration: tencent cloud
• OS (e.g: cat /etc/os-release): centos 7.9
• Kernel (e.g. uname -a): 3.10.0-1160.11.1.el7.x86_64
• Network plugin and version (if this is a network-related bug):
• Others:

登录失败：OAuth Error

版本：1.2.1
操作流程：
使用邮箱注册成功后登录，提示OAuth Error： invalid_request， At least one redirect_uri must be registered with the client.

Erda dashboard value view problem

What happened:

�when value below 0.005 percent, dashboard value round down view will not be readable.

What you expected to happen:

round down like 0.00 or other readable type.

Environment:

• Erda Cloud

Go action support dynamic go version or higher version

What would you like to be added:

1.support go build action module go version dynamic or be optional.
2.Increase the display of the current go version and other language version in the action to facilitate the location of problems.

Why is this needed:

some feature is not support , like 1.16 feature “go embed”.

使用安装指导安装，不能够正常的安装其openapi服务

What happened:

概况

按照安装指导，在第3步和第4步之间不能够正常安装。

详述

1. 通过第3步最后一步安装：

helm install package/erda-0.1.0.tgz --generate-name

2. k8s上对应pod和task已经执行成功，然而，在k8s中并没有生成名字为openapi的pod

# kubectl get all
NAME                                         READY   STATUS      RESTARTS   AGE
pod/addon-cassandra-dc1-rack1-0              2/2     Running     0          37m
pod/addon-elasticsearch-0                    1/1     Running     0          37m
pod/addon-kafka-8686c5dc7d-kzn5t             1/1     Running     1          37m
pod/addon-kms-5ffb9c994d-mzs7n               1/1     Running     0          37m
pod/addon-nexus-59478988-5lf7g               1/1     Running     0          37m
pod/addon-registry-65c5bc9fc5-v2ppd          1/1     Running     0          37m
pod/addon-sonar-7fcbd7f6f6-l62lf             1/1     Running     0          37m
pod/addon-zookeeper-776dbf8694-bvsgs         1/1     Running     0          37m
pod/cassandra-operator-6bfff7d475-92f97      1/1     Running     0          45m
pod/elasticsearch-operator-ff85d4bc4-pf76x   1/1     Running     0          45m
pod/erda-etcd-745674469c-gkxzj               1/1     Running     0          37m
pod/erda-init-image-nvh6l                    0/1     Completed   0          34m
pod/erda-mysql-f868ccd5f-ckwr4               1/1     Running     0          37m
pod/erda-operator-676dc98cc-9snjk            1/1     Running     0          45m
pod/netportal-7d6c49c8d7-9fs8c               1/1     Running     0          37m
pod/redis-operator-7f5cfdf469-xm66p          1/1     Running     0          45m
pod/rfr-addon-redis-0                        1/1     Running     0          37m
pod/rfs-addon-redis-559494bf95-frv2z         1/1     Running     0          37m
pod/volume-provisioner-5cnpc                 1/1     Running     0          45m
pod/volume-provisioner-bdgtv                 1/1     Running     0          45m
pod/volume-provisioner-dgj8g                 1/1     Running     0          45m
pod/volume-provisioner-g4zhj                 1/1     Running     0          45m
pod/volume-provisioner-pgjln                 1/1     Running     0          45m
pod/volume-provisioner-pqjw4                 1/1     Running     0          45m

NAME                                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
service/addon-cassandra                ClusterIP   None            <none>        9042/TCP                     37m
service/addon-cassandra-exporter-jmx   ClusterIP   None            <none>        9500/TCP                     37m
service/addon-elasticsearch            ClusterIP   10.68.176.167   <none>        9200/TCP                     37m
service/addon-elasticsearch-master     ClusterIP   10.68.5.114     <none>        9300/TCP                     37m
service/addon-kafka                    ClusterIP   None            <none>        9092/TCP,9988/TCP,8778/TCP   37m
service/addon-kms                      ClusterIP   10.68.158.39    <none>        3082/TCP                     37m
service/addon-nexus                    ClusterIP   10.68.166.35    <none>        8081/TCP,5000/TCP,5500/TCP   37m
service/addon-registry                 ClusterIP   10.68.175.212   <none>        5000/TCP,5050/TCP            37m
service/addon-sonar                    ClusterIP   10.68.130.217   <none>        9000/TCP                     37m
service/addon-zookeeper                ClusterIP   10.68.32.22     <none>        2181/TCP,2888/TCP,3888/TCP   37m
service/cassandra-operator-metrics     ClusterIP   10.68.221.183   <none>        8383/TCP                     45m
service/elasticsearch-operator         ClusterIP   10.68.219.118   <none>        443/TCP                      45m
service/erda-etcd                      ClusterIP   10.68.176.156   <none>        2379/TCP                     37m
service/erda-mysql                     ClusterIP   10.68.135.23    <none>        3306/TCP                     37m
service/kubernetes                     ClusterIP   10.68.0.1       <none>        443/TCP                      4h50m
service/netportal                      ClusterIP   10.68.201.196   <none>        80/TCP                       37m
service/rfs-addon-redis                ClusterIP   10.68.62.148    <none>        26379/TCP                    37m

NAME                                DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/volume-provisioner   6         6         6       6            6           <none>          45m

NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/addon-kafka              1/1     1            1           37m
deployment.apps/addon-kms                1/1     1            1           37m
deployment.apps/addon-nexus              1/1     1            1           37m
deployment.apps/addon-registry           1/1     1            1           37m
deployment.apps/addon-sonar              1/1     1            1           37m
deployment.apps/addon-zookeeper          1/1     1            1           37m
deployment.apps/cassandra-operator       1/1     1            1           45m
deployment.apps/elasticsearch-operator   1/1     1            1           45m
deployment.apps/erda-etcd                1/1     1            1           37m
deployment.apps/erda-mysql               1/1     1            1           37m
deployment.apps/erda-operator            1/1     1            1           45m
deployment.apps/netportal                1/1     1            1           37m
deployment.apps/redis-operator           1/1     1            1           45m
deployment.apps/rfs-addon-redis          1/1     1            1           37m

NAME                                               DESIRED   CURRENT   READY   AGE
replicaset.apps/addon-kafka-8686c5dc7d             1         1         1       37m
replicaset.apps/addon-kms-5ffb9c994d               1         1         1       37m
replicaset.apps/addon-nexus-59478988               1         1         1       37m
replicaset.apps/addon-registry-65c5bc9fc5          1         1         1       37m
replicaset.apps/addon-sonar-7fcbd7f6f6             1         1         1       37m
replicaset.apps/addon-zookeeper-776dbf8694         1         1         1       37m
replicaset.apps/cassandra-operator-6bfff7d475      1         1         1       45m
replicaset.apps/elasticsearch-operator-ff85d4bc4   1         1         1       45m
replicaset.apps/erda-etcd-745674469c               1         1         1       37m
replicaset.apps/erda-mysql-f868ccd5f               1         1         1       37m
replicaset.apps/erda-operator-676dc98cc            1         1         1       45m
replicaset.apps/netportal-7d6c49c8d7               1         1         1       37m
replicaset.apps/redis-operator-7f5cfdf469          1         1         1       45m
replicaset.apps/rfs-addon-redis-559494bf95         1         1         1       37m

NAME                                         READY   AGE
statefulset.apps/addon-cassandra-dc1-rack1   1/1     37m
statefulset.apps/addon-elasticsearch         1/1     37m
statefulset.apps/rfr-addon-redis             1/1     37m

NAME                        COMPLETIONS   DURATION   AGE
job.batch/erda-init-image   1/1           57s        34m

NAME                                                AGE
redisfailover.databases.spotahome.com/addon-redis   37m

3. 参考第4步的bash scripts/push-ext.sh脚本，易得知此时第4步会陷入死循环中。因为此时openapi的svc为空，无法生成正确的hosts

...
echo `kubectl get svc -n default | grep openapi | awk '{print $3}'` openapi.${ERDA_NAMESPACE}.svc.cluster.local >> /etc/hosts
...

4. 再参考quickstart的安装，可以看到quickstart的docker中有openapi的镜像。

5. 当我们忽略前面的错误继续配置，然后通过浏览器访问，得到404 错误，反馈消息是

backend server not found

What you expected to happen:

在helm install package/erda-0.1.0.tgz --generate-name命令执行之后，可以生成对应的openapi pod和service；抑或是该服务更改了名字的情况下，需要修改bash-ext.sh脚本。

How to reproduce it (as minimally and precisely as possible):

1. 使用kubeasz的标准步骤部署k8s。网络组件使用flannel。
2. 使用该指导进行操作

Anything else we need to know?:

Environment:

• Erda version: v1.0.0，v1.0.0-rc（两个版本都试过，上面的日志是v1.0.0的问题）
• Kubernetes version (use kubectl version): v1.21.0
• Cloud provider or hardware configuration: tencent cloud, 3-masters-and-3-slaves-k8s installed by kubeasz
• OS (e.g: cat /etc/os-release): centos 7.9
• Kernel (e.g. uname -a): 3.10.0-1160.11.1.el7.x86_64
• Network plugin and version (if this is a network-related bug):
• Others:

erda通过uc页面输入用户名密码后无法跳转到主页面

问题:

erda通过uc页面输入用户名密码后无法跳转到主页面

复现方法:

通过在ingress-controller中添加 hide-header x-frame-option
外部起一个网站通过iframe嵌入erda
此时通过iframe访问erda会发生登录后无法跳转的问题

Environment:

• Erda version: 1。4
• Kubernetes version (use kubectl version): 1.19.16
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release): centos 7.6.18
• helm部署

添加已有集群报错

What happened:
导入已有集群报错

What you expected to happen:

能够通过界面导入一个已有的k8s集群

How to reproduce it (as minimally and precisely as possible):

多云管理平台 ->添加集群 -> 导入已创建的Erda Kubernetes集群

Environment:

• Erda version: 1.1.1
• Kubernetes version (use kubectl version): 1.18.20
• Cloud provider or hardware configuration: vmware vsphere
• OS (e.g: cat /etc/os-release): CentOS Linux release 7.6.1810 (Core)
• Kernel (e.g. uname -a): 3.10.0-957.el7.x86_64
• Network plugin and version (if this is a network-related bug): calico 3.20.0
• Others:

A quickstart script to help newbie try erda without dizzy

What would you like to be added:

a docker-compose.yml file that let users to run erda in their own computer.

Why is this needed:

everyone can have a try of our product, with no dizzy~

• one compose file to run in local #222
• a more closed uc replacement #224
• domainless startup #225
• migration of db #235

可以给一个线上demo体验一下嘛，不要这种图片demo骗我们

integrating wechat mini-program ci

What would you like to be added:

integrating wechat mini-program ci which is provided by wechat official:
https://developers.weixin.qq.com/miniprogram/dev/devtools/ci.html

Why is this needed:

have a fluent continue integration about wechat mini-program

无法通过自建集群的方式创建一个集群，报get cloud resource context failed, err:<nil>

What happened:

无法通过自建集群的方式创建一个集群，报get cloud resource context failed, err:

What you expected to happen:

应该能够通过界面自建一个Erda的托管集群

How to reproduce it (as minimally and precisely as possible):

1. 在租户界面点击添加集群-->自建集群
   

2. 填入以下信息
   
   
   

3. 填写完成之后点击确定，可以看到上面第3个截图的错误。

get cloud resource context failed, err:<nil>

Anything else we need to know?:

Environment:

• Erda version: 1.0.1
• Kubernetes version (use kubectl version): v1.18.16
• Cloud provider or hardware configuration: tencent cloud
• OS (e.g: cat /etc/os-release): CentOS Linux release 7.9.2009
• Kernel (e.g. uname -a): 3.10.0-1160.31.1.el7.x86_64
• Network plugin and version (if this is a network-related bug):
• Others:

cmp中的4个组件分别是什么含义

cluster-manage: 我理解是控制端用来管理集群，集群的增删改查
cluster-init
cluster-agent
cluster-dialer
这几个的作用是什么？

Hello, I am a personal developer. I recently read erda open source and would like to ask if there is a deployment tutorial. I personally want to study the erda source code

Hello, I am a personal developer. I recently read erda open source and would like to ask if there is a deployment tutorial. I personally want to study the erda source code

获取访问权限失败: 异常 failed to Access permission

基于 Docker Compose 本地安装成功后，访问报错，求指导如何解决，谢谢~
{"success":false,"err":{"code":"InternalError","msg":"获取访问权限失败: 异常 failed to Access permission","ctx":null}}

http://one.erda.local/api/-/permissions/actions/access

期望增加 Windows 下基于 Docker-Compose 的安装部署引导

目前公司内部，使用的是正版 Windows 服务器，为了保证企业内部平台运行稳定，以及考虑到运维人员的工作量，Erda 需要部署在Windows 的 Docker 环境上，期待在官方文档中，增加对 Windows 的部署。

clone太慢了，到码云做个镜像吧

clone太慢了，到码云做个镜像吧

看不懂目录结构, 能提供开发文档么

What would you like to be added:

Why is this needed:

pipeline need support queue management

What would you like to be added:

You can create any number of queues if you need, and bind one workflow to one queue.
There is a priority between and inside queues. Each queue holds certain resources.

Between queues, queue with large priority number will be scheduled earlier, and workflow inside queue will be scheduled order by workflow's priority number one by one.
Only after all the workflows in the queue with the highest priority are executed successfully, will the workflows in the queue with the second highest priority be executed, and so on.

Why is this needed:

Achieve more fine-grained workflow scheduling.
To a certain extent, more important workflows can be completed with high priority.

这么喜欢搞全家桶

……

_{Sent from PPHub}

when i change my password ，cursor is missing

What happened:

when i type first word , the cursor will missing

What you expected to happen:

User experience optimization

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

nfs service not supported on centos8

What happened:

an error occurred when install nfs:

Failed to enable unit: Unit file nfs.service does not exist.

Anything else we need to know?:

You may only need to change nfs to nfs-server in script when enable/start nfs server

Environment:

• OS (e.g: cat /etc/os-release):

NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"

• Kernel (e.g. uname -a):

Linux xxx 4.18.0-147.5.1.el8_1.x86_64 #1 SMP Wed Feb 5 02:00:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

快数据模块在哪

快数据模块在哪

etcd,mysql,zk提示无法找不到PVC

自助添加k8s集群的时候，无法根据现在的界面来添加

What happened:

自助添加k8s集群的时候，无法根据现在的界面来添加

What you expected to happen:

添加集群的时候，泛域名和集群入口能够有相应的提示，并且能够配置

How to reproduce it (as minimally and precisely as possible):

1. 在同一个网络中，通过kubeasz创建另外一个K8S集群。
2. 通过erda的安装指导安装好erda，然后通过管理员创建一个erda-test的租户，再登录到erda-test-org.erda.io这个租户里面。
3. 参考了这个指导，在多云管理平台-->资源管理-->集群管理中，添加集群-->导入已创建的Erda Kubernetes集群。根据界面来填写时，发现泛域名和集群入口不能够直接拿我们K8S节点的IP地址。
   

Anything else we need to know?:

目前erda能够导入的K8S集群，只能够是erda自身创建的吗？能否导入外部的集群？

我现在主要是想要体验一下erda的各种功能；如果不添加额外的K8S集群，是否可以用erda目前所在的集群做DevOps、部署这类的操作呢？

Environment:

• Erda version: 1.0.1
• Kubernetes version (use kubectl version): v1.18.16
• Cloud provider or hardware configuration: tencent cloud
• OS (e.g: cat /etc/os-release): CentOS Linux release 7.9.2009
• Kernel (e.g. uname -a): 3.10.0-1160.31.1.el7.x86_64
• Network plugin and version (if this is a network-related bug):
• Others:

添加集群报错

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Erda version:
• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Network plugin and version (if this is a network-related bug):
• Others:
  添加集群报错：
  添加已有资源自建集群
  异常 get cloud resource context failed, err:

多云管理平台导入自建kubernetes集群后，只显示master节点信息，无work node节点相关信息

What happened:

多云管理平台导入自建kubernetes集群后，只显示master节点信息，无work node节点相关信息，添加kubernetes中work node节点时，操作窗口卡死无响应

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Erda version:v1.0.0
• Kubernetes version (use kubectl version):v1.18.4
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):centos7.6 1810
• Kernel (e.g. uname -a):3.10.0-957.el7.x86_64
• Network plugin and version (if this is a network-related bug):calico v3.8.6
• Others:

构建pipeline的时候，自动推送包到https接口，而不是http接口

What happened:

pipeline push package failed, err log as belows:

2021-12-30 19:12:58The push refers to repository [10.20.0.200:5000/test-java-demo/test1]
2021-12-30 19:13:08Get https://10.20.0.200:5000/v2/: net/http: TLS handshake timeout

What you expected to happen:

use http but not https

How to reproduce it (as minimally and precisely as possible):

start a pipeline line

Anything else we need to know?:

Environment:

• Erda version:
• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Network plugin and version (if this is a network-related bug):
• Others:

没有支持C#语言开发

现在使用C#（.net core）的公司也非常多，看语言支持里面还没有C#
或者是否能考虑把dapr整合进来呢？

关于步骤三helm install下载失败的问题

What happened:

在安装到步骤三的时候，执行说明中的步骤：
helm install erda-base package/erda-base-$(cat VERSION).tgz
无法下载包

What you expected to happen:

可以顺利安装试用

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Erda version:1.1.1
• Kubernetes version (use kubectl version):1.17.0
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):Centos7.8
• Kernel (e.g. uname -a):
• Network plugin and version (if this is a network-related bug):
• Others:

self deployed erda how to get admin password

What happened:

I have deployed a erda in my local k8s cluster, but I don't know how to found admin account and password

What you expected to happen:

show me a away to get admin password

How to reproduce it (as minimally and precisely as possible):

no

Anything else we need to know?:

no

Environment:

• Erda version:1.4

• Kubernetes version (use kubectl version):1.21.2

• Cloud provider or hardware configuration: aws

• OS (e.g: cat /etc/os-release): ubuntu 18.04

• Kernel (e.g. uname -a): 5.4.0-1059-aws

• Network plugin and version (if this is a network-related bug): calio

• Others:

基于 Helm 最小化安装 Erda以后，通过erda.io访问，一直处在循环的跳转之中

基于 Helm 最小化安装 Erda后，检测各种服务都正常；显示如下；


绑定域名hosts：
159.138.4.188 erda.io
159.138.4.188 collector.erda.io
159.138.4.188 openapi.erda.io
159.138.4.188 uc.erda.io
通过erda.io访问，一直处在无限循环跳转之中：

could you plan to split the single project to multi micro service?

the whole project is more than 800k go code, may be is too large to maintain

trigger pipeline by git tag

What would you like to be added:

trigger pipeline by git tag

e.g.

on:
   push:
       tags: "release*"

Why is this needed:

Trying to get in touch regarding a security issue

Hey there!

I'd like to report a security issue but cannot find contact instructions on your repository.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.

Thank you for your consideration, and I look forward to hearing from you!

(cc @huntr-helper)

集群安装失败

直接在页面上创建集群，选择创建阿里云托管版集群，资源都已经创建完成，在安装dice的步骤失败。

另外一种方式安装，基于Helm，在阿里云ACK集群中安装，也是安装失败:

急～执行scripts/push-ext.sh 找不到这个服务openapi.default.svc.cluster.local

kubectl get svc -A 没有该服务

执行push-ext.sh 错误提示：

并且pod有不少也没有启动起来

helm 也都安装了。

Erda version: 1.1.1
Kubernetes version (use kubectl version): v1.18.6
Cloud provider or hardware configuration:huaweiyun cloud
OS (e.g: cat /etc/os-release): CentOS Linux release 7.6.1810

erda's status failed : create init jobs failed: Job has reached the specified backoff limit

What happened:

When I installed erda by Helm, the status of erda is failed and cannot go on.
In the erda-system namespace, only the middleware pod, there are no erda's pod.
And there's no pod in default namespace.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Erda version: 1.4
• Kubernetes version (use kubectl version): 1.21.6
• Cloud provider or hardware configuration: RKE/rancher
• OS (e.g: cat /etc/os-release): centos 7.4
• Kernel (e.g. uname -a): 3.10.0-693.el7.x86_64
• Network plugin and version (if this is a network-related bug):
• Others:

如何在没有域名的情况下，外网访问erda.io？

What happened:

已完成k8s集群搭建，应用已经部署，ingress-controller已经安装，由于没有域名，有外网可访问的IP地址，配置了一台master三台node，不知如何配置ingress-controller才可以使外网访问到，已试过用master节点外网ip地址访问，无效。

What you expected to happen:

可以通过配置外网IP+端口访问到erda平台，谢谢。

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Erda version:
• Kubernetes version (use kubectl version): 1.17.0
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Network plugin and version (if this is a network-related bug):
• Others:

admin管理员不可创建集群

What happened:

在当前的管理员视图中(通过admin登录erda.io)，不能够创建集群。

What you expected to happen:

管理员应该可以创建集群，这样能够减轻组织自行创建集群的负担。
如果必须到组织才能创建集群，请也在前台给出明显提示，并且告知原因为什么不可以创建。

How to reproduce it (as minimally and precisely as possible):

1. 安装好之后，管理员登录erda.io
2. 进入管理后台界面，尝试创建集群，发现界面置灰。
   

Anything else we need to know?:

Environment:

• Erda version: 1.0.1
• Kubernetes version (use kubectl version): v1.18.16
• Cloud provider or hardware configuration: tencent cloud
• OS (e.g: cat /etc/os-release): CentOS Linux release 7.9.2009
• Kernel (e.g. uname -a): 3.10.0-1160.31.1.el7.x86_64
• Network plugin and version (if this is a network-related bug):
• Others:

Compile gittar module error

When I compile the gittar module, it throws the following error

------------ Start Build Version Details ------------
AppName: gittar
Arch: arm64
OS: darwin
Version: 4.0
BuildTime: 2021-05-16 23:20:58
GoVersion: go version go1.16.4 darwin/arm64
CommitID: 0c4e0654b9e934164f1ea03e2e5b0de0fb8775ed
DockerImage:
------------ End Build Version Details ------------
git submodule update --init
go mod tidy: already have vendor dir, skip tidy
cd "/Users/liuhaoyang/projects/github/erda/erda/cmd/gittar" && \
        PROJ_PATH=/Users/liuhaoyang/projects/github/erda/erda GOPRIVATE= go build -ldflags " -X 'github.com/erda-project/erda-infra/base/version.Version=4.0' -X 'github.com/erda-project/erda-infra/base/version.BuildTime=2021-05-16 23:20:58' -X 'github.com/erda-project/erda-infra/base/version.CommitID=0c4e0654b9e934164f1ea03e2e5b0de0fb8775ed' -X 'github.com/erda-project/erda-infra/base/version.GoVersion=go version go1.16.4 darwin/arm64' -X 'github.com/erda-project/erda-infra/base/version.DockerImage='" -tags dynamic -o "/Users/liuhaoyang/projects/github/erda/erda/bin/gittar"
# github.com/libgit2/git2go/v30
../../vendor/github.com/libgit2/git2go/v30/blame.go:4:10: fatal error: 'git2.h' file not found
#include <git2.h>
         ^~~~~~~~
1 error generated.
make: *** [build] Error 2

I have confirmed that I have installed libgit2 with reference to https://github.com/odewahn/git2go-test.
How should I solve this problem next ?

基于k8s部署后，集群总览中没有实例数显示。

基于k8s部署后，集群总览中没有实例数显示。

以下是telegraf pod的logs信息：

希望可以添加一个配置文件参数，用于修改x-frame-options

当我尝试将页面嵌入其他网站时，发生了错误。
查看发现是x-frame-options参数设置的是sameorigin。

希望可以参考下grafana，将此参数设置为可配置参数

在 windows 的下的 WSL2 Ubuntu 20.04 版本系统中，Issue 集合

1、在 Docker Desktop 上，erda 自动创建的 Quick Start 均为未启动状态：

2、ES 提示 500错误：


3、cassandra 异常：

4、erda-redis 异常：

通过查看系统端口占用情况，发现与 Docker 和 WSL2 系统有关：

怎么编译调试

What happened:

make build-image
发现找不到项目根目录cmd/build 文件

希望出一个 怎么编译readme

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Erda version:
• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Network plugin and version (if this is a network-related bug):
• Others: