vmware-archive / kubeless-ui Goto Github PK

Graphical User Interface for Kubeless

License: Apache License 2.0

JavaScript 88.31% HTML 0.62% Shell 0.41% Dockerfile 0.32% SCSS 10.34%

kubeless-ui's Introduction

WARNING: Kubeless is no longer actively maintained by VMware.

VMware has made the difficult decision to stop driving this project and therefore we will no longer actively respond to issues or pull requests. If you would like to take over maintaining this project independently from VMware, please let us know so we can add a link to your forked project here.

Thank You.

kubeless-ui

NOTICE This project is no longer actively maintained. Kubeless maintainers will still accept and review Pull Requests but no active development is expected.

Graphical User Interface for Kubeless, a serverless framework for Kubernetes.

In-Cluster Installation

To run the UI inside your Kubernetes cluster as a Deployment and Service you can run the following:

kubectl create -f https://raw.githubusercontent.com/kubeless/kubeless-ui/master/k8s.yaml

These are known to work on minikube, they may need a few tweaks if you have RBAC turned on (docs coming soon).

Development

Project based on davezuko/react-redux-starter-kit

Install dependencies It is recommended that you use Yarn for deterministic installs.

yarn install    # Install project dependencies
yarn run dev    # Launch and watch server

(npm will also work if you really want)

Dev server with Hot Module Replacement should run at http://localhost:3000

Production

You can bundle the app in dist/ folder

This will also run linter and tests.

yarn run build

Now you just have to serve the dist/ folder with node (yarn run start) or with an nginx.

Docker image

Exists and automated build that you can find on DockerHub, Quay.io and Gcloud Registry by this name: bitnami/kubeless-ui

Snapshot

kubeless-ui's People

Contributors

Stargazers

Watchers

Forkers

jbianquetti-nami yodata kmarquardsen edwardjrp andresmgot jjo arjunrao87 woss prydonius anguslees gokulchandrap station19 kimat linebreaker lorenz duke-lv mccjul thingswise myang32 donteam sportsbitenews ajacques konsorten mvranic digideskio eagle9527 sangkyunyoon kkoojjyy oswaldderiemaecker t1seungy lynchpin4 apple0407 vermanotes mixergit dalavancloud fwdnickv cloudmelon sudhirkthakur joejordanbrown thomasgauthierr forkkit cloud-land sunqiang25 gowravshekar ikkedus tscswcn umeshh laashub-soa georgekaz wubiaowp halcyondude alexanderroloinc aditya-bhuyan baseonballs liubarnabas wannasky joaonart qmutz maduhu changsongyang renuacpro tun-0-9-tap-0-9 technologyinstitute umair-gujjar xeinn jbadru73 darcuripan pheverless sshyran alainlompo imsatendersingh1997 lerix43

kubeless-ui's Issues

Passing JSON does not seem to work

GET functions work fine, but for POST functions, it does not seem that we can pass JSON objects.

Think about integrating a repo of functions

Say some functions are packaged as "charts"

Retrieve this library of functions and display them in the UI, offering possibility to deploy.

Fix CSS for large functions name

When the function name is bigger than its placeholder it is displayed over the next item:

Can't access kubeless-ui non-localhost

kubeless-ui will run on localhost:3000. I'd like to access it through server IP like 217.20.113.125:3000 .
Is there any way?
thanks

run function gives 500

Hi, I have deployed kubeless v0.6.0 and kubeless-ui on kubernetes 1.10. I created test.foobar function using quick-start. I can call the function from kubeless as mentioned in guide:

$ kubeless function call get-python --data '{"echo": "echo echo"}'
{"echo": "echo echo"}

However, when I try to run function using ui, I get nothing back. In browser console, I see response to POST http://<ui-pod-ip>:3000/proxy is 500 and request payload has following:

{url: "http://localhost:8080/api/v1/proxy/namespaces/kubeless/services/get-python:8080",…}
headers:{event-id: "ui-11ebb8bc32f0", event-time: "2018-04-24T14:42:21.809Z", event-type: "application/json",…}
Accept:"application/json"
Content-Type:"application/json"
X-Requested-With:"XMLHttpRequest"
event-id:"ui-11ebb8bc32f0"
event-namespace:"ui.kubeless.io"
event-time:"2018-04-24T14:42:21.809Z"
event-type:"application/json"
json:"{"hi":"d"}"
method:"post"
url:"http://localhost:8080/api/v1/proxy/namespaces/kubeless/services/get-python:8080"

I ran kubectl proxy -p 8080 locally and tried following:

 $ curl http://localhost:8080/api/v1/proxy/namespaces/kubeless/services/get-python
{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {  },
  "status": "Failure",
  "message": "the server could not find the requested resource",
  "reason": "NotFound",
  "details": {  },
  "code": 404
}

is this url correct? As per kubernetes doc, shouldn't this be localhost:8080/api/v1/namespaces/kubeless/services/get-python:8080/proxy?

How to run kubeless UI using docker-compose

Hi,

docker-compose is able to display the UI but there are some issues connecting the UI to the k8s cluster via the proxy.

Basically the issue is that the UI's docker envionment does not have access to proxy-url:proxy-port

dev_1  | webpack: Compiled successfully.
dev_1  | Mon, 05 Jun 2017 17:37:12 GMT app:server Error: request to http://localhost:8080/api/v1/pods failed, reason: connect ECONNREFUSED 127.0.0.1:8080

What would be the best way to achieve this? From the top of my head, we could tell the UI service to run in network mode host

--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -13,3 +13,4 @@ services:
       - .:/app
     ports:
       - "3000:3000"
+    network_mode: host

Think about authentication and identity management

We need to think about authentication for this.

The k8s dashboard might give us some ideas.

The coreOS dex project might be useful as well.

CORS not running in Docker image

@jbianquetti-nami the UI runs on port 3000 but there is a CORS proxy running on port 3001.

I am wondering if in the Docker image, the CORS proxy process actually starts properly, preventing the UI to load functions when running inside a cluster. #17

Retrieve multiple files from configmaps

A configmap might have multiple files in it.

kubectl create configmap barfoo --from-file=foo.py --from-file=requirements.txt

Be able to retrieve and display this in some type of tree structure
Edit and save

POST calls received as GET

For an unknown reason, when sending a POST call to a function (/api/v1/proxy/namespaces/default/services/foo), the function receive a GET request

Here are some facts:

Sending a curl POST request works fine.
I thought it was due to the cors-proxy used to fix cors in dev, but a curl request through the cors-proxy works fine.
Sending a POST request to create the function works fine.
Sending a POST request in the app, through the cors-proxy, to a sample api server (https://httpbin.org/post) works fine.

I'm thinking about a problem with headers on the kubernetes api server, if someone has any idea..?

Install kubeless from UI

I'm wondering if it could be a good idea to allow the installation of kubeless/kubeless-controller directly from the UI

Just opening the discussion, to see what it involves 🙌

AceEditor mode bug

Hi,

I'm using minikube and I've deployed kubeless-ui via the k8s.yml file.
I am getting the service url via minikube service -n kubeless ui --url which gives me http://192.168.99.100:30113.
I am using Chrome Version 69.0.3497.100 (Official Build) (64-bit) on Windows 7 x64.
The bug also occurs on Firefox 62.0.3 (64-bit) so I don't think it's a browser specific bug.

Something goes wrong in the editor react component and the editor does not have syntax highlighting.
The chain of events starts in src/components/Editor/Editor.js at line 145 in render(), where the mode is computed for the AceEditor 3rd party component.

-> render() -> runtimeToMode() -> RuntimeHelper.runtimeToLanguage() ->
-> await this.getAllRuntimes() -> ... start returning

Somewhere along the way this fails because a Promise is not handled properly. Because of that the
browser issues a request to http://192.168.99.100:30113/mode-[object%20Promise].js which
of course fails.

I think you need an async/await pair either in runtimeToMode() or render() or both :).

In let mode = this.runtimeToMode(), mode ends up to be a Promise object, not the resolved result.

I wanted to run the app locally but I'm on Windows and node-sass does not support it.

Load python dependencies from Kubeless UI

Migrated from vmware-archive/kubeless#229.

Feature: Have a option to load python dependencies from Kubeless UI

UI create functions failed (connect ECONNREFUSED 127.0.0.1:8080)

minikube (signal node)

sudo minikube start --image-mirror-country cn     --iso-url=https://kubernetes.oss-cn-hangzhou.aliyuncs.com/minikube/iso/minikube-v1.9.0.iso     --registry-mirror=https://mirror.aliyuncs.com --vm-driver=none --insecure-registry=[192.168.31.211:5000]

sudo kubectl proxy --port=8001 --accept-hosts='^.*' --address='192.168.31.211'

docker version

# docker version
Client: Docker Engine - Community
 Version:           19.03.12
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        48a66213fe
 Built:             Mon Jun 22 15:45:49 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       48a66213fe
  Built:            Mon Jun 22 15:44:20 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

kubeless version

# kubeless version
Kubeless version: v1.0.7-dirty

create,call function success by cli

# kubeless function call hello --data 'Hello world!'
Hello world!

but create function in UI failed
and server error info

# yarn run dev
yarn run v1.22.4
$ better-npm-run dev
running better-npm-run in /k8s/kubeless/kubeless-ui
Executing script: dev

to be executed: nodemon bin/server --ignore dist --ignore coverage --ignore tests --ignore src
[nodemon] 1.11.0
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node bin/server index.js`
  app:config:project Creating default configuration. +0ms
  app:config:project Looking for environment overrides for NODE_ENV "development". +3ms
  app:config:project Found overrides, applying to default configuration. +1ms
  app:config:webpack Creating configuration. +808ms
  app:config:webpack Enabling plugins for live development (HMR, NoEmitOnErrors). +2ms
  app:server Enabling webpack dev and HMR middleware +134ms
  app:bin:server
  app:bin:server
  app:bin:server  💻  Server is now running at localhost:3000 +43ms
(node:4443) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
    at Object.parseQuery (/k8s/kubeless/kubeless-ui/node_modules/babel-loader/node_modules/loader-utils/index.js:78:3)
    at Object.module.exports (/k8s/kubeless/kubeless-ui/node_modules/babel-loader/lib/index.js:104:35)
    at LOADER_EXECUTION (/k8s/kubeless/kubeless-ui/node_modules/loader-runner/lib/LoaderRunner.js:119:14)
    at runSyncOrAsync (/k8s/kubeless/kubeless-ui/node_modules/loader-runner/lib/LoaderRunner.js:120:4)
    at iterateNormalLoaders (/k8s/kubeless/kubeless-ui/node_modules/loader-runner/lib/LoaderRunner.js:229:2)
    at Array.<anonymous> (/k8s/kubeless/kubeless-ui/node_modules/loader-runner/lib/LoaderRunner.js:202:4)
    at Storage.finished (/k8s/kubeless/kubeless-ui/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:38:15)
    at /k8s/kubeless/kubeless-ui/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:69:9
    at /k8s/kubeless/kubeless-ui/node_modules/graceful-fs/graceful-fs.js:115:16
    at FSReqWrap.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:53:3)
webpack built b401a52cb111a9aeacc2 in 9882ms
Hash: b401a52cb111a9aeacc2
Version: webpack 2.4.1
Time: 9882ms
                                                                            Asset       Size  Chunks                    Chunk Names
/k8s/kubeless/kubeless-ui/node_modules/font-awesome/fonts/fontawesome-webfont.eot     166 kB          [emitted]
                                             ba89e316e1e812fc4e91923f94d76895.png    24.5 kB          [emitted]
                                                      app.b401a52cb111a9aeacc2.js    4.73 MB       0  [emitted]  [big]  app
                                                   vendor.b401a52cb111a9aeacc2.js     445 kB       1  [emitted]  [big]  vendor
                                                  app.b401a52cb111a9aeacc2.js.map    5.53 MB       0  [emitted]         app
                                               vendor.b401a52cb111a9aeacc2.js.map     493 kB       1  [emitted]         vendor
                                                                      favicon.ico    34.5 kB          [emitted]
                                                                       index.html  977 bytes          [emitted]
Child html-webpack-plugin for "index.html":
         Asset    Size  Chunks  Chunk Names
    index.html  571 kB       0
webpack: Compiled successfully.
  app:server Error: request to http://localhost:8080/api/v1/namespaces/kubeless/configmaps/kubeless-config failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +17s
  app:server Error: request to http://localhost:8080/api/v1/pods failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +28ms
  app:server Error: request to http://localhost:8080/apis/kubeless.io/v1beta1/functions failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +1ms
  app:server Error: request to http://localhost:8080/api/v1/namespaces/kubeless/configmaps/kubeless-config failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +57ms
  app:server Error: request to http://localhost:8080/api/v1/namespaces/kubeless/configmaps/kubeless-config failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +2s
  app:server Error: request to http://localhost:8080/api/v1/namespaces/kubeless/configmaps/kubeless-config failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +1ms
  app:server Error: request to http://localhost:8080/api/v1/namespaces/kubeless/configmaps/kubeless-config failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +18s
  app:server Error: request to http://localhost:8080/api/v1/namespaces/kubeless/configmaps/kubeless-config failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +3ms
  app:server Error: request to http://localhost:8080/api/v1/namespaces/kubeless/configmaps/kubeless-config failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +21m
  app:server Error: request to http://localhost:8080/api/v1/pods failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +13ms
  app:server Error: request to http://localhost:8080/apis/kubeless.io/v1beta1/functions failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +1ms
  app:server Error: request to http://localhost:8080/api/v1/namespaces/kubeless/configmaps/kubeless-config failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +81ms
  app:server Error: request to http://localhost:8080/api/v1/namespaces/kubeless/configmaps/kubeless-config failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +25m
  app:server Error: request to http://localhost:8080/api/v1/namespaces/kubeless/configmaps/kubeless-config failed, reason: connect ECONNREFUSED 127.0.0.1:8080 +16ms

all pod are running

# kubectl get pod --all-namespaces
NAMESPACE              NAME                                          READY   STATUS    RESTARTS   AGE
default                hello-f765f6fbd-p4r4c                         1/1     Running   0          5h16m
kube-system            coredns-546565776c-28cw2                      1/1     Running   0          5h25m
kube-system            coredns-546565776c-xd825                      1/1     Running   0          5h25m
kube-system            etcd-pc09                                     1/1     Running   0          5h25m
kube-system            kube-apiserver-pc09                           1/1     Running   0          5h25m
kube-system            kube-controller-manager-pc09                  1/1     Running   0          5h25m
kube-system            kube-proxy-48mml                              1/1     Running   0          5h25m
kube-system            kube-scheduler-pc09                           1/1     Running   0          5h25m
kube-system            storage-provisioner                           1/1     Running   0          5h25m
kubeless               kubeless-controller-manager-59d484f4d-9zpjg   3/3     Running   0          5h19m
kubeless               ui-698c9989-4bhcx                             2/2     Running   0          66m
kubernetes-dashboard   dashboard-metrics-scraper-84bfdf55ff-rlrrv    1/1     Running   0          5h25m
kubernetes-dashboard   kubernetes-dashboard-bc446cc64-hls4t          1/1     Running   0          5h25m

and i cannot curl 8080 on server

# curl 127.0.0.1:8080
curl: (7) Failed to connect to 127.0.0.1 port 8080: 拒绝连接
# kubectl logs ui-698c9989-4bhcx -n kubeless -c proxy
Starting to serve on 127.0.0.1:8080

help!!!!

use next.js instead of davezuko/react-redux-starter-kit which is deprecated

I suggest you have a look to https://github.com/zeit/next.js/

IMO it is very easy to use and it is a good replacement for

https://github.com/davezuko/react-redux-starter-kit
and
https://github.com/facebookincubator/create-react-app

kubeless-ui doesnt support functions in other namespaces

functions deployed in namespaces other then "default" are not shown.
also if the config: functions-namespace, is used, kubeless-ui does not show anything at all

Put ASL license headers everywhere

that's the correct way to apply a ASF license. Putting the license file int the root is not enough.

Retrieve function code from configmaps

Start from code being stored in configmaps:

kubectl create configmaps foobar --from-file=foobar.py

be able to load those configmaps
display code in editor
edit function and save, triggering an update of the configmap

no matches for kind "Deployment" in version "extensions/v1beta1"

The exact command to reproduce the issue:

kubectl create -f https://raw.githubusercontent.com/kubeless/kubeless-ui/master/k8s.yaml

Error

unable to recognize "https://raw.githubusercontent.com/kubeless/kubeless-ui/master/k8s.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"

kubectl version

Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T23:42:50Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:09:08Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

Reason

Using deprecated Kubernetes API Endpoints.

UI page is not scrolling Down.

Not able to Scroll down the UI page. Cursor going down but not able to view page.

UI not working

I brought up the UI using the Docker image. Does it need something else to be running in the backend?

Please help ASAP.

Issue with basic authentication

When trying to access the Kubeless UI with basic authentication enabled, the UI works until you try to create a function.

Steps to reproduce:

Create an ingress rule with basic authentication enabled to the Kubeless UI service
Create a function

kubeless-ui needs to enable visibility to configmap

got this bug with: kubectl create -f https://raw.githubusercontent.com/kubeless/kubeless-ui/master/k8s.yaml
it will result in creation of kubeless-ui but serviceaccount lack of visibility to see configmap.

View that shows running function

Some functions may not be running (just code that is retrieved from configmaps not linked to kubeless).

For functions that are running via kubeless, we need a view that does:

Show pods running
Show type of function
Show logs kubectl get logs
Test call to function

Unable to connect to Minikube via Kubeless UI

I am running the kubeless UI and it comes up just fine. However, I am unable to create any new functions or see existing functions through the UI. I am running behind a proxy so I am wondering if that has anything to do with it. My minikube cluster IP is 192.168.99.100. The cluster IP on the Kubeless UI is like so

I try to create the function and while the function modal pops up it doesnt actually create anything.

When I look at the ui pod logs I see this

yarn run v0.24.4
$ better-npm-run start 
running better-npm-run in /app
Executing script: start
 to be executed: node bin/server 
Thu, 12 Oct 2017 14:59:59 GMT app:config:project Creating default configuration.
Thu, 12 Oct 2017 14:59:59 GMT app:config:project Looking for environment overrides for NODE_ENV "production".
Thu, 12 Oct 2017 14:59:59 GMT app:config:project Found overrides, applying to default configuration.
Thu, 12 Oct 2017 15:00:01 GMT app:config:webpack Creating configuration.
Thu, 12 Oct 2017 15:00:01 GMT app:config:webpack Enabling plugins for production (OccurenceOrder, Dedupe & UglifyJS).
Thu, 12 Oct 2017 15:00:01 GMT app:config:webpack Applying ExtractTextPlugin to CSS loaders.
Thu, 12 Oct 2017 15:00:01 GMT app:bin:server 
  💻  Server is now running on port 3000
Thu, 12 Oct 2017 15:00:28 GMT app:server Error: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the API version in the data () does not match the expected API version (k8s.io/v1)","reason":"BadRequest","code":400}
 Thu, 12 Oct 2017 15:01:03 GMT app:server Error: request to http://192.168.99.100:8080/api/v1/pods failed, reason: connect ECONNREFUSED 192.168.99.100:8080
Thu, 12 Oct 2017 15:01:03 GMT app:server Error: request to http://192.168.99.100:8080/apis/k8s.io/v1/functions failed, reason: connect ECONNREFUSED 192.168.99.100:8080
Thu, 12 Oct 2017 15:01:09 GMT app:server Error: request to http://192.168.99.100:8080/apis/k8s.io/v1/namespaces/default/functions failed, reason: connect ECONNREFUSED 192.168.99.100:8080
Thu, 12 Oct 2017 15:02:27 GMT app:server Error: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the API version in the data () does not match the expected API version (k8s.io/v1)","reason":"BadRequest","code":400}
 Thu, 12 Oct 2017 15:10:45 GMT app:server Error: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the API version in the data () does not match the expected API version (k8s.io/v1)","reason":"BadRequest","code":400}
 Thu, 12 Oct 2017 15:14:46 GMT app:server Error: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the API version in the data () does not match the expected API version (k8s.io/v1)","reason":"BadRequest","code":400}

There seem to be 2 errors here

Refusal to connect ( could be a proxy issue but right now i have no means of passing a no_proxy env var to the UI deployment )
API version mismatch ( I am not sure what this error means )

What do you think is the problem here?

Stuck in loading pods

After creating an initial function, I clicked on the console button and I get:

I can retrieve those resources via kubectl

kubectl get po,svc,cm -l function=miguel
NAME                         READY     STATUS    RESTARTS   AGE
po/miguel-4191672957-whsz5   1/1       Running   0          4m

NAME         TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
svc/miguel   ClusterIP   10.47.248.108   <none>        8080/TCP   4m

NAME        DATA      AGE
cm/miguel   3         4m

And the logs for the proxy container look like:

$ kubectl logs kubeless-ui-184132610-tv4rt -c proxy -n kubeapps -p

Error from server (BadRequest): previous terminated container "proxy" in pod "kubeless-ui-184132610-tv4rt" not found

Refreshing the UI after some time makes the UI console work.

Docker image to run the UI

Finish the dockerfile that packages the UI

limit the number of logs

with the readiness probe currently probing every 5 seconds, the logs are loonnng....

we should default to the last 100 long entries (at least for now in dev)....

Or maybe have an option:

short logs (tail -f)
all (whatever is in the pod, but then the UI might become unresponsive).

Additional Documentation

I added some documentation associated with things like dev-guides and CONTRIBUTING.md. If it is useful I can submit a PR!

[minor] typo on function name placeholder

Shouldn't the placeholder be world instead of word?

Integrate a monocular view

using the monocular backend we can add a chart repo view in the UI.

This would be nice, because functions are here to link other applications. Applications will be deployed as Charts. With a chart repo view and deployment capability, a user will have a single UI to deploy the charts and then deploy functions.

k8s.yaml has duplicate key.

Line 100 of k8s.yaml has a duplicate key for imagePullPolicy.

Update documentation to mention the docker-compose file for development

Hi,

It seems that now it is possible to have a development environment by using the existing docker-compose file. It would probably make sense to mention it in the README.

Support for other namespace and other KAFKA services!

Deployed a Kubeless + Kubeless UI on cloud using my_namespace as my namespace.

When using Kubeless UI, functions are been created in the default namespace and can't use pubsub because can't set ENVs vars for runtime containers.

Cannot propagate KUBELESS_KAFKA_SVC and KUBELESS_NAMESPACE to runtime envs via UI.

How to propagate the correct env vars for via ui for runtime function containers¿?
How to set Kubeless o functions aren't create in the default namespace¿?

PD: thanks to @andresmgot for support on bitnami slack channel.

adding deps doesn't work

create function on UI with deps has no effect. function's dep field shows empty.

I can modify function to add dep(kubectl apply -f ) after creation though, and then deps shows on UI.

new code updated on kubeless-ui doesn't take effect

got this bug when try to change existing code on kubeless-ui.
For example:

create a new python2.7 function on kubeless-ui.
it will automatically generate a simple "hello world" code.
now if I change this code, to make it say "hello 123", and save it, then click on "run function", it will still show result "hello world".

Although I can see function got changed if I do "kubectl get function -o yaml", the result has no changes at all.
the result only changes when I manually delete function pod, which will trigger a recreation of that pod. I think this is due to recreation of a function pod reloads function scripts.

suggestions: automatically kill old pod if user changes and saves a script on kubeless-ui

View that lets us create a function in kubeless

select a function
create it with kubeless, this will be a call to a custom k8s endpoint.
provide status update by linking it to the running pod that runs the function

Want flexible root URL

When deploying kubeless-ui alongside other services, it would be really useful if I could put kubeless-ui somewhere other than / on a dedicated hostname. Ideally kubeless-ui would use relative URLs for other kubeless-ui assets (stylesheets, javascript, etc), or failing that use a URL path prefix configurable via docker env/args.

vmware-archive/kubeless#154

but it can't seem to be able to fetch the functions at all.

I am guessing an issue with the CORS proxy itself running in the UI code ?