Giter Club home page Giter Club logo

naftis's Introduction

Naftis

License Build Status

English | 中文

Naftis is a web-based dashboard for Istio that helps users manage their Istio tasks more easily. Using Naftis, we can customize our own task templates, build tasks from them, then execute them.

Features

  • Integrates with some real-time dashboards
  • Customizable task template
  • Supports Rollback specific tasks
  • Optimized Istio service graph with support for specifying particular root service nodes
  • Diagnose data of Istio services and pods
  • Out of the box, easy deployment with kubectl commands
  • Istio 1.0 supported

Quick start

# download latest Naftis release files and manifest
wget -O - https://raw.githubusercontent.com/XiaoMi/naftis/master/tool/getlatest.sh | bash

# deploy Naftis under bare metal Kubernetes
kubectl create namespace naftis && kubectl apply -n naftis -f mysql.yaml && kubectl apply -n naftis -f naftis.yaml

# deploy Naftis under cloud Kubernetes cluster, such as GKE, Amazon EKS, Alibaba Cloud Kubernetes
kubectl create namespace naftis && kubectl apply -n naftis -f mysql-cloud.yaml && kubectl apply -n naftis -f naftis.yaml

# port forward Naftis
kubectl -n naftis port-forward $(kubectl -n naftis get pod -l app=naftis-ui -o jsonpath='{.items[0].metadata.name}') 8080:80 &

# explore http://localhost:8080/ with your browser - default user name and password is "admin".

Detailed deployments

# download latest Naftis files and manifest
wget -O - https://raw.githubusercontent.com/XiaoMi/naftis/master/tool/getlatest.sh | bash

# create Naftis namespace
$ kubectl create namespace naftis

# ensure Naftis namespace is created
$ kubectl get namespace naftis
NAME           STATUS    AGE
naftis         Active    18m

# deploy Naftis MySQL service under bare metal Kubernetes
$ kubectl apply -n naftis -f mysql.yaml
# deploy Naftis MySQL service under cloud Kubernetes cluster, such as GKE, Amazon EKS, Alibaba Cloud Kubernetes
$ kubectl apply -n naftis -f mysql-cloud.yaml

# ensure MySQL service is deployed
$ kubectl get svc -n naftis
NAME                           READY     STATUS    RESTARTS   AGE
naftis-mysql-c78f99d6c-kblbq   1/1       Running   0          9s
naftis-mysql-test              1/1       Running   0          10s

# deploy Naftis API and UI service
$ kubectl apply -n naftis -f naftis.yaml

# ensure Naftis all services is correctly defined and running
$ kubectl get svc -n naftis
NAME           TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
naftis-api     ClusterIP      10.233.3.144    <none>        50000/TCP      7s
naftis-mysql   ClusterIP      10.233.57.230   <none>        3306/TCP       55s
naftis-ui      LoadBalancer   10.233.18.125   <pending>     80:31286/TCP   6s

$ kubectl get pod -n naftis
NAME                           READY     STATUS    RESTARTS   AGE
naftis-api-0                   1/2       Running   0          19s
naftis-mysql-c78f99d6c-kblbq   1/1       Running   0          1m
naftis-mysql-test              1/1       Running   0          1m
naftis-ui-69f7d75f47-4jzwz     1/1       Running   0          19s

# browse Naftis via port-forward
$ kubectl -n naftis port-forward $(kubectl -n naftis get pod -l app=naftis-ui -o jsonpath='{.items[0].metadata.name}') 8080:80 &

Explore http://localhost:8080/ with your browser - default user name and password is "admin".

Previews

Dashboard

Dashboard

Services

Service detail

Services-Detail

Service pod

Services-Pod

Task templates

Task tpl

Task Tpl

Task view

Task View

Task new

Task New

Create task

Create Task Step1

Create Task Step2

Create Task Step3

Istio diagnosis

Istio Diagnosis

Contribution

See CONTRIBUTING for details on submitting patches and the contribution workflow.

License

Apache License 2.0

naftis's People

Contributors

0xflotus avatar czah avatar jukylin avatar lincolnzhou avatar micah-el avatar newt0n avatar rootsongjc avatar sevennt avatar silenceper avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

naftis's Issues

创建模板 sql报错

创建模板 sql报错。 模板里面的yaml内容在命令行是可以正常创建的

naftis pod状态不正确

按照yaml文件部署后,查看pod,状态一直未能处于running状态,如图:
image
然后依次查看events和logs后,仍不知道怎么解决,events和logs依次如下:

  1. 第一个pod的events:Back-off restarting failed container;
    logs:panic: failed to connect database dial tcp 10.104.171.112:3306: connect: connection refused。
  2. 第二个pod的events:pulling image "mysql:5.7.14"一直处于拉取状态,但是镜像已经拉取成功了;
    logs:Error from server (BadRequest): container "naftis-mysql" in pod "naftis-mysql-7fcc6f9799-v68h4" is waiting to start: PodInitializing。
  3. 第三个pod的events没有发现什么异常,logs如下:
    image
  4. 第四个pod和第二个pod的events和logs一样。
    希望前辈们能帮我这个小菜鸟解决一下,先谢谢了。

使用nodeport暴露端口,访问后登录时报错

Describe the bug
按照github上的步骤进行端口转发失败后,使用nodeport暴露端口,访问后登录时报错。

To Reproduce
想试一下naftis的功能,但是到这一步,一直访问不了,想请大佬们指导指导。
Steps :

  1. 端口转发失败后,我修改了naftis.yaml,将LoadBalance改为了NodePort,然后replace naftis.yaml;
  2. 之后就执行暴露端口的命令:
    NAFTIIS_NODEPORT=$(kubectl get svc naftis-ui -n naftis -o jsonpath='{.spec.ports[0].nodePort}')
    INGRESS_HOST=$(kubectl get node -o jsonpath='{.items[0].status.addresses[0].address}')
    echo "http://$INGRESS_HOST:$NAFTIIS_NODEPORT/naftis-ui/"
  3. 执行后,输出地址:http://192.168.217.100:30326/naftis-ui/,然后用google浏览器访问;
  4. 访问后出现了naftis的登录页面,输入初始用户名admin和密码admin后,右上角出现:Notification
    app.common.errOthers(405)!
    错误页面截图如下:
    image
    想请大佬们帮我看一下,端口暴露的方式是否正确,为什么不可以端口转发?

Unable to open dashboard

After login, I got a blank page. There is an error in console.

main.9ea155fc030e37b46931.js:1 Uncaught TypeError: Failed to construct 'URL': Invalid URL
    at Module.l (main.9ea155fc030e37b46931.js:1)
    at Module.tjUo (main.9ea155fc030e37b46931.js:1)
    at c (main.9ea155fc030e37b46931.js:1)
    at Object.1 (main.9ea155fc030e37b46931.js:1)
    at c (main.9ea155fc030e37b46931.js:1)
    at a (main.9ea155fc030e37b46931.js:1)
    at main.9ea155fc030e37b46931.js:1
    at main.9ea155fc030e37b46931.js:1

Below is formatted code

            var e = window.localStorage.getItem("authToken")
              , t = Object(c.b)();
            "" === t && (t = window.location.host);
            var a = "ws://" + new URL(t).host + "/ws?access_token=" + e
              , o = new n.a(a,{
                timeout: 5e3,
                maxAttempts: 10,
                onopen: function(e) {

service 是否可以增加namespace

service 是否可以增加namespace

问题:
我不同namespace 里面有相同service name,显示出来就有点怪

另外:
创建mysql 使用secretKeyRef 的形式引入密码。实则启动后密码没生效,导致服务连不上
直接name ,value 字符串的方式才可以。

Reloader sidecar in naftis-api fails to reload promviz configuration

Describe the bug
naftis-api does not provide reload api, so the sidecar reloader fail to reload promviz configuration by reload url http://localhost:50000/reload.

Error from naftis-api:

$ kubectl -n naftis logs -f --tail 50  naftis-api-0 naftis-api
[GIN] 2018/12/01 - 11:56:55 | 200 |      71.096µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:56:56 | 200 |     121.448µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:57:01 | 404 |       2.013µs |             ::1 | POST     /reload
[GIN] 2018/12/01 - 11:57:05 | 200 |      94.056µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:57:06 | 200 |      68.985µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:57:15 | 200 |      144.69µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:57:16 | 200 |      74.286µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:57:25 | 200 |     249.232µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:57:26 | 200 |      61.465µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:57:35 | 200 |      91.104µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:57:36 | 200 |     163.875µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:57:39 | 404 |       1.813µs |             ::1 | POST     /reload
[GIN] 2018/12/01 - 11:57:45 | 200 |     116.342µs |  192.168.21.103 | GET      /api/probe/healthy
[GIN] 2018/12/01 - 11:57:46 | 200 |     115.269µs |  192.168.21.103 | GET      /api/probe/healthy

Error from reloader:

$ kubectl -n naftis logs -f --tail 50  naftis-api-0 reloader
{"level":"info","ts":1543665367.378195,"caller":"k8s-config-reloader/main.go:106","msg":"Starting reloader...","component":"reloader"}
{"level":"warn","ts":1543665367.5766084,"caller":"k8s-config-reloader/main.go:144","msg":"Failed to reload promviz configuration","component":"reloader","error":"Received response code %!s(int=404), expected 200","next retry":0.507739337}
{"level":"warn","ts":1543665368.180896,"caller":"k8s-config-reloader/main.go:144","msg":"Failed to reload promviz configuration","component":"reloader","error":"Received response code %!s(int=404), expected 200","next retry":1.047383961}
{"level":"warn","ts":1543665369.4312794,"caller":"k8s-config-reloader/main.go:144","msg":"Failed to reload promviz configuration","component":"reloader","error":"Received response code %!s(int=404), expected 200","next retry":1.217617209}
{"level":"warn","ts":1543665370.6576612,"caller":"k8s-config-reloader/main.go:144","msg":"Failed to reload promviz configuration","component":"reloader","error":"Received response code %!s(int=404), expected 200","next retry":0.916087631}

To Reproduce

Naftis: v0.1.3
Istio: v1.0.0
Kubernetes: v1.10

Expected behavior
There is no error.

Screenshots
If applicable, add screenshots to help explain your problem.

Environments (please complete the following information):

  • OS: [e.g. Linux]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 0.1.3]

Additional context
Add any other context about the problem here.

helm 安装时报错

helm version : 2.11.0
Error: render error in "naftis/templates/configmap.yaml": template: naftis/templates/configmap.yaml:5:24: executing "naftis/templates/configmap.yaml" at <indent>: wrong number of args for indent: want 2 got 1
应该是
values.yaml:

api:
  config: |-

未配置,配置后可以解决问题。

在kubernetes中启动,看不到服务。

在k8s 中启动的。
版本:
image: sevennt/naftis-api:0.1.4-rc5

遇到问题:
service中没有数据,个数为0

istio的服务显示正常。

请问需要配置什么吗?还是默认会收集service信息。

naftis-mysql Container Error

After applying the mysql.yaml, the pod doesn't start properly ("Init:CrashLoopBackOff")

kubectl apply -n naftis -f mysql.yaml

The event is probably

Error: failed to start container "remove-lost-found": Error response from daemon: error while creating mount source path '/mnt/data': mkdir /mnt/data: read-only file system

It's probably related to kubernetes/kubernetes#64120, but I don't know how to fix it. Can anyone help?

Kubernetes-Version: v1.10.9 on GKE

创建模板报错

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environments (please complete the following information):

  • OS: kubernetes 1.12
  • Browser Chrome
  • Version [naftis Chats Version 0.1.1]

Additional context
Add any other context about the problem here.

创建模板报错.

(/home/travis/gopath/src/github.com/xiaomi/naftis/src/api/storer/db/tasktmpl.go:44)
[2019-01-12 04:52:03] Error 1146: Table 'naftis.task_tmpls' doesn't exist

(/home/travis/gopath/src/github.com/xiaomi/naftis/src/api/storer/db/tasktmpl.go:44)
[2019-01-12 04:52:03] [1.71ms] INSERT INTO task_tmpls (created_at,updated_at,deleted_at,name,content,brief,revision,operator,icon) VALUES ('2019-01-12 04:52:03','2019-01-12 04:52:03',NULL,'qw','wq
','qw','1','admin','')
[0 rows affected or returned ]

istio配置显示和支持自定义host

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

1,当前只有配置的写入,没有查看当前已有配置的功能,希望增加~
2,当前配置的host只支持k8s的service,希望能支持host 自定义,一些场景如gateway的对外host、egress的外部host以及其他platform adapter的host(consul)

谢谢~
Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

不能连接到mysql

Describe the bug
按文档里的章节“Running Under Kubernetes Cluster”里的步骤执行后,mysql运行正常,但naftis-api的状态为CrashLoopBackOff,查看日志报:
failed to connect database Error 1130: Host 'cpe-172-88-169-137.socal.res.rr.com' is not allowed to connect to this MySQL server

naftis-api Pod启动出错

naftis-api Pod启动出错如下:
Error: failed to start container "naftis-api": Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: "--config=/etc/naftis/config/config.toml": stat --config=/etc/naftis/config/config.toml: no such file or directory"

我感觉是不是这个configmap哪里有问题,还是我的部署方式有问题?

apiVersion: v1
kind: ConfigMap
data:
config: |-
mode="debug"
[logger]
[logger.console]
color=true
prefix="[naftis]"
level="Info"
[logger.zap]
path="naftis-api.log"
level="Debug"
[db]
default="naftis:naftisIsAwesome@tcp(naftis-mysql.naftis.svc.cluster.local:3306)/naftis?charset=utf8&parseTime=True&loc=Local"
metadata:
name: naftis-config
namespace: naftis
selfLink: /api/v1/namespaces/naftis/configmaps/naftis-config

自定义创建问题

我创建了个自定义模板,跟traffic shift一样,就是把reviews改变为了{.Host},创建模板任务时填完参数提交就报错了,报400,提示namespace参数为空

服务拓扑看不到图

您好,现在生成服务拓扑是调用的servicegraph还是kiali。 我从kiali里是能看到拓扑图的。

使用nodeport暴露端口,访问后登录时报错

Describe the bug
按照github上的步骤进行端口转发失败后,使用nodeport暴露端口,访问后登录时报错。

To Reproduce
Steps :

  1. 端口转发失败后,我修改了naftis.yaml,将LoadBalance改为了NodePort,然后replace naftis.yaml;
  2. 之后就执行暴露端口的命令:
    NAFTIIS_NODEPORT=$(kubectl get svc naftis-ui -n naftis -o jsonpath='{.spec.ports[0].nodePort}')
    INGRESS_HOST=$(kubectl get node -o jsonpath='{.items[0].status.addresses[0].address}')
    echo "http://$INGRESS_HOST:$NAFTIIS_NODEPORT/naftis-ui/"
  3. 执行后,输出地址:http://192.168.217.100:30326/naftis-ui/,然后用google浏览器访问;
  4. 访问后出现了naftis的登录页面,输入初始用户名admin和密码admin后,右上角出现:Notification
    app.common.errOthers(405)!

错误页面截图如下:

image

请帮忙看下这是什么错误?怎么解决?先谢谢各位。

不支持自定义域名?

naftis是运行在默认域名 cluster.local 下的。如果集群的域名不是默认的,naftis-ui就起不来。api还好,可以修改参数。

Failed create pod sandbox

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T18:02:47Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
$ kubectl describe pod -n naftis naftis-api-0
Name:           naftis-api-0
Namespace:      naftis
Node:           192.168.100.101/192.168.100.101
Start Time:     Thu, 25 Oct 2018 09:17:25 -0400
Labels:         app=naftis-api
                controller-revision-hash=naftis-api-5dc5f875
                release=naftis
                statefulset.kubernetes.io/pod-name=naftis-api-0
Annotations:    <none>
Status:         Running
IP:             172.20.2.37
Controlled By:  StatefulSet/naftis-api
Containers:
  naftis-api:
    Container ID:  docker://a93bc414f2c81955f0e8427e63c71b3ac691cc7a33e3a60aeaf049830fa7da4e
    Image:         docker.io/sevennt/naftis-api:latest
    Image ID:      docker-pullable://sevennt/naftis-api@sha256:92ae3a89f00e11c8806f8a6161c83f09d4724c2740c86147ed8645fe1ca68481
    Port:          50000/TCP
    Host Port:     0/TCP
    Args:
      --config=/etc/naftis/config/config.toml
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Thu, 25 Oct 2018 10:37:47 -0400
      Finished:     Thu, 25 Oct 2018 10:37:48 -0400
    Ready:          False
    Restart Count:  19
    Liveness:       http-get http://:50000/api/probe/healthy delay=30s timeout=30s period=10s #success=1 #failure=3
    Readiness:      http-get http://:50000/api/probe/healthy delay=30s timeout=30s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /etc/naftis/config from naftis-config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-jl84z (ro)
  reloader:
    Container ID:  docker://6cc5d25880966837a8ffd45cc2eecc6428808cfa698a57213a02dde89514fe7d
    Image:         nghialv2607/k8s-config-reloader:v0.1.0
    Image ID:      docker-pullable://nghialv2607/k8s-config-reloader@sha256:7baea618e7558474da1b2af7493252a39bad484b89d9474acd0af96cec2ecbf4
    Port:          <none>
    Host Port:     <none>
    Args:
      --config.promviz-reload-url=http://localhost:50000/reload
      --config.promviz-config-dir=/etc/naftis
      --config.log-level=info
    State:          Running
      Started:      Thu, 25 Oct 2018 10:26:53 -0400
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Thu, 25 Oct 2018 10:11:26 -0400
      Finished:     Thu, 25 Oct 2018 10:26:52 -0400
    Ready:          True
    Restart Count:  3
    Limits:
      cpu:     50m
      memory:  64Mi
    Requests:
      cpu:        20m
      memory:     32Mi
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-jl84z (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  naftis-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      naftis-config
    Optional:  false
  default-token-jl84z:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-jl84z
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     <none>
Events:
  Type     Reason                  Age                 From                      Message
  ----     ------                  ----                ----                      -------
  Normal   Scheduled               1h                  default-scheduler         Successfully assigned naftis/naftis-api-0 to 192.168.100.101
  Normal   Pulling                 1h                  kubelet, 192.168.100.101  pulling image "docker.io/sevennt/naftis-api:latest"
  Normal   Pulled                  1h                  kubelet, 192.168.100.101  Successfully pulled image "docker.io/sevennt/naftis-api:latest"
  Normal   Pulling                 1h                  kubelet, 192.168.100.101  pulling image "nghialv2607/k8s-config-reloader:v0.1.0"
  Normal   Pulled                  1h                  kubelet, 192.168.100.101  Successfully pulled image "nghialv2607/k8s-config-reloader:v0.1.0"
  Normal   Created                 1h                  kubelet, 192.168.100.101  Created container
  Normal   Started                 1h                  kubelet, 192.168.100.101  Started container
  Normal   Pulled                  1h (x3 over 1h)     kubelet, 192.168.100.101  Container image "docker.io/sevennt/naftis-api:latest" already present on machine
  Normal   Created                 1h (x4 over 1h)     kubelet, 192.168.100.101  Created container
  Normal   Started                 1h (x4 over 1h)     kubelet, 192.168.100.101  Started container
  Warning  Unhealthy               1h                  kubelet, 192.168.100.101  Readiness probe failed: Get http://172.20.2.22:50000/api/probe/healthy: dial tcp 172.20.2.22:50000: connect: connection refused
  Warning  BackOff                 1h (x14 over 1h)    kubelet, 192.168.100.101  Back-off restarting failed container
  Warning  FailedCreatePodSandBox  43m                 kubelet, 192.168.100.101  Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "413c6742cbc22c3769088b8b5235ec247df57a09b4bb9c02cd885755b18a0d77" network for pod "naftis-api-0": NetworkPlugin cni failed to set up pod "naftis-api-0_naftis" network: open /run/flannel/subnet.env: no such file or directory
  Warning  FailedCreatePodSandBox  43m                 kubelet, 192.168.100.101  Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "5c53cbd5d248fe522076382647bdb63e4660d7abecea19538b6424de4b8f5c43" network for pod "naftis-api-0": NetworkPlugin cni failed to set up pod "naftis-api-0_naftis" network: open /run/flannel/subnet.env: no such file or directory
  Normal   SandboxChanged          43m (x3 over 43m)   kubelet, 192.168.100.101  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled                  43m                 kubelet, 192.168.100.101  Container image "nghialv2607/k8s-config-reloader:v0.1.0" already present on machine
  Normal   Created                 43m                 kubelet, 192.168.100.101  Created container
  Normal   Started                 43m                 kubelet, 192.168.100.101  Started container
  Normal   Pulled                  42m (x3 over 43m)   kubelet, 192.168.100.101  Container image "docker.io/sevennt/naftis-api:latest" already present on machine
  Normal   Created                 42m (x3 over 43m)   kubelet, 192.168.100.101  Created container
  Normal   Started                 42m (x3 over 43m)   kubelet, 192.168.100.101  Started container
  Warning  BackOff                 3m (x188 over 42m)  kubelet, 192.168.100.101  Back-off restarting failed container

dashboard界面显示出错

TIM截图20190530174342
dashboard页面显示的Pod和service数量和用api接口获取到的数量交换了,并且统计的数量和集群中Pod,service数量不一致

关于web界面路由规则汉字化的建议

在右上角选择了中文之后,显示的路由规则还是英文,可不可以修改成中文的?如图:
image

希望管理者能够提供一些帮助,我愿意做这个工作。
真心觉得naftis有些功能挺好的,但是活跃度好低啊。。。

api后端接口,时快时慢

装了一下naftis,首先显示是总共36个服务,总pod 39

在刷新一下页面 的接口
/api/services
/api/diagnose
/api/tasktmpls
发现有时候会有10s的请求是从,而有时候就是ms内

invalid serviceUID

Describe the bug
A clear and concise description of what the bug is.
当创建任务时,返回 invalid serviceUID 这个错误。几个任务都报错

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environments (please complete the following information):

  • OS: [e.g. Linux] Linux
  • Browser [e.g. chrome, safari] chrome
  • Version [e.g. 0.1.3] 0.1.4-rc5

Additional context
Add any other context about the problem here.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.