edge-stack | EMQ X edge stack consolidates all of EMQ edge softwares

by emqx Shell Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | edge-stack Summary

edge-stack is a Shell library typically used in Edge Computing, Docker, Kafka applications. edge-stack has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

The EMQ X edge stack consolidates all of EMQ edge softwares, and user can start to use edge stack with one-click deployment.

Support

Quality

Security

License

Reuse

Support

edge-stack has a low active ecosystem.

It has 18 star(s) with 6 fork(s). There are 11 watchers for this library.

It had no major release in the last 6 months.

edge-stack has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of edge-stack is current.

Quality

edge-stack has no bugs reported.

Security

edge-stack has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

edge-stack is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

edge-stack releases are not available. You will need to build from source code and install.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of edge-stack

Get all kandi verified functions for this library.

edge-stack Key Features

No Key Features are available at this moment for edge-stack.

edge-stack Examples and Code Snippets

No Code Snippets are available at this moment for edge-stack.

Community Discussions

Trending Discussions on edge-stack

ambassador service stays "pending"

Ambassador Edge Stack w/ GKE Health Check and LB Provisioning Errors

QUESTION

ambassador service stays "pending"

Asked 2021-May-26 at 20:19

Currently running a fresh "all in one VM" (stacked master/worker approach) kubernetes v1.21.1-00 on Ubuntu Server 20 LTS, using

cri-o as container runtime interface
calico for networking/security

also installed the kubernetes-dashboard (but I guess that's not important for my issue 😉). Taking this guide for installing ambassador: https://www.getambassador.io/docs/edge-stack/latest/topics/install/yaml-install/ I come along the issue that the service is stuck in status "pending".

kubectl get svc -n ambassador prints out the following stuff

...

ANSWER

Answered 2021-May-26 at 20:19

Answer is pretty much here: https://serverfault.com/questions/1064313/ambassador-service-stays-pending . After installing a load balancer the whole setup worked. I decided to go with metallb (https://metallb.universe.tf/installation/#installation-by-manifest for installation). I decided to go with the following configuration for a single-node kubernetes cluster:

Source https://stackoverflow.com/questions/67637854

QUESTION

Ambassador Edge Stack w/ GKE Health Check and LB Provisioning Errors

Asked 2021-Apr-04 at 22:34

I'm currently installing the Ambassador Edge Stack (AES) to help manage several applications running applications in our GKE cluster but I'm experiencing a couple of issues.

The steps in the manual install guide seem to be working fine aside from edgectl being deprecated in favour of telepresence (I haven't tried this out really).

The next steps, setting up the ingress with GKE is where the issues begin.

As per the guide, this can be done with the legacy Ambassador API Gateway or the new AES. Doing a compare of both installs, you don't need to do anything in the API Gateway install other than sorting out patching the original aes ambassador service and the ambassador-admin service from LoadBalancer to NodePort types. I've done this with kustomize

...

ANSWER

Answered 2021-Apr-04 at 22:34

According to the google documentation, if you want the load balancer to terminate SSL traffic then you need to configure it to do so. You can use the following instructions: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls

These are linked to in the original documentation by google about how to create a L7 loadbalancer as linked in the ambassador docs: https://cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer (link comes from Step 1 of this site you linked: https://www.getambassador.io/docs/edge-stack/latest/topics/running/ambassador-with-gke/)

Unfortunately this means that you wouldn't be getting full advantage of Ambassador's letsencrypt automatic certificate generation when you specify both an ambassador Mapping and a Host. On my GKE cluster which I installed AES from scratch, has a Service of type LoadBalancer which automatically creates a google load balancer (if you're in GKE that is). This service has ports configured for 443 and 80 automatically and no additional ingress is needed.

Source https://stackoverflow.com/questions/66923069

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install edge-stack

As described in previous section, we prepared a tutorial doc, which allows you to deploy a docker & docker-compose based demo environment within several minutes.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: