Comments (5)
FYI: I finally get it working, I changed the mesh-name in kustomize, but only on nlb/deployment, I changed it also in base/gateway/deployment and everything is working, thank you again
from flagger-appmesh-gateway.
3000
is the port, looks like that port is not opened or it's not setup correctly in the virtual node, virtual service, deployment or kubernetes service. The name of the port should be http
.
from flagger-appmesh-gateway.
Thanks, I rechecked/recreated and I got the same error:
apiVersion: appmesh.k8s.aws/v1beta1
kind: VirtualService
metadata:
name: s1.apps.svc.cluster.local
namespace: apps
annotations:
gateway.appmesh.k8s.aws/expose: "true"
gateway.appmesh.k8s.aws/retries: "5"
gateway.appmesh.k8s.aws/timeout: "25s"
gateway.appmesh.k8s.aws/domain: "example.com,www.example.com"
spec:
meshName: applications
routes:
- name: route-to-svc-blue
http:
match:
prefix: /
action:
weightedTargets:
- virtualNodeName: s1-blue
weight: 1
---
apiVersion: appmesh.k8s.aws/v1beta1
kind: VirtualNode
metadata:
name: s1-blue
namespace: apps
spec:
meshName: applications
listeners:
- portMapping:
port: 3000
protocol: http
serviceDiscovery:
dns:
hostName: s1-blue.apps.svc.cluster.local
backends:
- virtualService:
virtualServiceName: s1.apps.svc.cluster.local
- virtualService:
virtualServiceName: s2.apps.svc.cluster.local
logging:
accessLog:
file:
path: /dev/stdout
---
apiVersion: v1
kind: Service
metadata:
name: s1
namespace: apps
labels:
app: s1
spec:
ports:
- name: http
port: 3000
protocol: TCP
targetPort: http
---
apiVersion: v1
kind: Service
metadata:
name: s1-blue
namespace: apps
labels:
app: s1
version: blue
spec:
ports:
- port: 3000
name: http
selector:
app: s1
version: blue
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: s1-blue
namespace: apps
spec:
replicas: 1
selector:
matchLabels:
app: s1
version: blue
template:
metadata:
labels:
app: s1
version: blue
spec:
containers:
- name: xxx
image: xxx.dkr.ecr.eu-west-1.amazonaws.com/xxx:12
ports:
- name: http
containerPort: 3000
protocol: TCP
from flagger-appmesh-gateway.
So did it work in the end?
from flagger-appmesh-gateway.
No, same behaviour, we are currently testing gloo. Thank you very much for your support
from flagger-appmesh-gateway.
Related Issues (5)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from flagger-appmesh-gateway.