wso2 / cellery-controller Goto Github PK

The controller goes in crashloop with the following error

flag provided but not defined: -logtostderr
Usage of /tmp/___go_build_main_go:
-kubeconfig string
Path to a kubeconfig. Only required if out-of-cluster.
-master string
The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.

Currently, a component inside a cell can only support exposing one port with one protocol. We may need to provide support for specifying multiple ports for a component in order to support multiple protocols.

Currently, all of the sensitive information fields in the cell is in plain text. As a solution, we can add RSA encryption support so that users can use a public key to encrypt the sensitive information fields.

Description:
Once the yamls are applied, I can access the pet-store.com. But only pet-store.com/items/ works as expected, if I access pet-store.com or pet-store.com/item then I get a blank page or error. Please change the sample such that it will work if user access that via pet-store.com or pet-store.com/item.

Currently, the controller generates a self-sign certificate for each cell which is used by the sts. With issue #47 the runtime will have its own key-pair which can be used to sign the generated cell certificates.

Replace the glog in the controller with zap logging as zap provides better perfomance and supports structured logging.

Zap:      527 ns per log request 
StdLog:  2992 ns per log request 
Glog:    3223 ns per log request 

Description:
Supporting SMI would allow us to easily support a number of service meshes without being bound to a single SM. We could even allow the user to select a supported SM of choice during installation of Cellery.

Useful links
https://smi-spec.io/
https://github.com/deislabs/smi-spec/
https://github.com/deislabs/smi-sdk-go/

LinkerD is working on supporting SMI

There's no Native support for Istio but there's an Istio adapter here https://github.com/deislabs/smi-adapter-istio

There's also maesh, which supports SMI natively. https://blog.containo.us/announcing-maesh-a-lightweight-and-simpler-service-mesh-made-by-the-traefik-team-cb866edc6f29

Currently, the gateway spec does not have grpc configuration. This is required in order to accept grpc traffic from the gateway.