Istio

IP Blacklisting in Istio

由 ∥☆過路亽．° 提交于 2020-06-27 03:49:11
问题 The IP whitelisting/blacklisting example explained here https://kubernetes.io/docs/tutorials/services/source-ip/ uses source.ip attribute. However, in kubernetes (kubernetes cluster running on docker-for-desktop) source.ip returns the IP of kube-proxy. A suggested workaround is to use request.headers["X-Real-IP"] , however it doesn't seem to work and returns kube-proxy IP in docker-for-desktop in mac. https://github.com/istio/istio/issues/7328 mentions this issue and states: With a proxy that

Why css and png are not accessible?

由 寵の児 提交于 2020-06-16 04:14:09
问题 I have created an Ingress, Deployment and Service as follows: apiVersion: v1 kind: Service metadata: name: hello-kubernetes-first spec: type: ClusterIP ports: - port: 80 targetPort: 8080 selector: app: hello-kubernetes-first --- apiVersion: apps/v1 kind: Deployment metadata: name: hello-kubernetes-first spec: replicas: 3 selector: matchLabels: app: hello-kubernetes-first template: metadata: labels: app: hello-kubernetes-first spec: containers: - name: hello-kubernetes image: paulbouwer/hello

Why css and png are not accessible?

由 时光毁灭记忆、已成空白 提交于 2020-06-16 04:13:26
问题 I have created an Ingress, Deployment and Service as follows: apiVersion: v1 kind: Service metadata: name: hello-kubernetes-first spec: type: ClusterIP ports: - port: 80 targetPort: 8080 selector: app: hello-kubernetes-first --- apiVersion: apps/v1 kind: Deployment metadata: name: hello-kubernetes-first spec: replicas: 3 selector: matchLabels: app: hello-kubernetes-first template: metadata: labels: app: hello-kubernetes-first spec: containers: - name: hello-kubernetes image: paulbouwer/hello

Why css and png are not accessible?

由 做~自己de王妃 提交于 2020-06-16 04:13:12
问题 I have created an Ingress, Deployment and Service as follows: apiVersion: v1 kind: Service metadata: name: hello-kubernetes-first spec: type: ClusterIP ports: - port: 80 targetPort: 8080 selector: app: hello-kubernetes-first --- apiVersion: apps/v1 kind: Deployment metadata: name: hello-kubernetes-first spec: replicas: 3 selector: matchLabels: app: hello-kubernetes-first template: metadata: labels: app: hello-kubernetes-first spec: containers: - name: hello-kubernetes image: paulbouwer/hello

HTTP404 for resources when using url rewriting on Istio gateway

由 限于喜欢 提交于 2020-05-28 04:38:28
问题 I'm trying to deploy a service to a specific url address on AKS. The following yaml let's me access the service at desired address, like xxxx.europe.cloudapp.azure.com/service-a. This works great, i've managed to hide the entire service under desired url: apiVersion: networking.istio.io/v1alpha3 kind: Gateway metadata: name: istio-gateway spec: selector: istio: ingressgateway servers: - port: number: 80 name: http protocol: HTTP hosts: - "*" --- apiVersion: networking.istio.io/v1alpha3 kind:

HTTP404 for resources when using url rewriting on Istio gateway

由 烈酒焚心 提交于 2020-05-28 04:37:46
问题 I'm trying to deploy a service to a specific url address on AKS. The following yaml let's me access the service at desired address, like xxxx.europe.cloudapp.azure.com/service-a. This works great, i've managed to hide the entire service under desired url: apiVersion: networking.istio.io/v1alpha3 kind: Gateway metadata: name: istio-gateway spec: selector: istio: ingressgateway servers: - port: number: 80 name: http protocol: HTTP hosts: - "*" --- apiVersion: networking.istio.io/v1alpha3 kind:

How to expose an external IP address for a sample Istio application

由 丶灬走出姿态 提交于 2020-05-16 02:44:28
问题 I am trying to set up the bookinfo sample application for Istio and Kubernetes on a small cluster. The cluster consists of two machines, a master and a worker, running on Ubuntu 18.04 on two Amazon AWS EC2 instances. Each of the instances has an external IP address assigned. What I'm unable to do is figure out how to expose the bookinfo service to the outside world. I am confused as to whether I need to expose the Istio ingress gateway or each one of the bookinfo services separately. When

How to expose an external IP address for a sample Istio application

由 别等时光非礼了梦想. 提交于 2020-05-16 02:44:26
问题 I am trying to set up the bookinfo sample application for Istio and Kubernetes on a small cluster. The cluster consists of two machines, a master and a worker, running on Ubuntu 18.04 on two Amazon AWS EC2 instances. Each of the instances has an external IP address assigned. What I'm unable to do is figure out how to expose the bookinfo service to the outside world. I am confused as to whether I need to expose the Istio ingress gateway or each one of the bookinfo services separately. When

Istio direct Pod to Pod communication

由 こ雲淡風輕ζ 提交于 2020-05-15 07:18:54
问题 I have a problem with the communication to a Pod from a Pod deployed with Istio? I actually need it to make Hazelcast discovery working with Istio, but I'll try to generalize the issue here. Let's have a sample hello world service deployed on Kubernetes. The service replies to the HTTP request on the port 8000. $ kubectl create deployment nginx --image=crccheck/hello-world The created Pod has an internal IP assigned: $ kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED

在线公开课 | 微服务太杂乱难以管理？一站式服务治理平台来袭！

由 二次信任 提交于 2020-05-08 22:36:35
课程概要 如今微服务已成为构建现代云应用的主导模式，它围绕着特定的业务功能，将单个组件分解为独立的服务。但随之而来产生另外的问题：越来越多的系统被拆解成了很多个细胞一样的微服务，如何对微服务进行管理，这成为许多工程师头疼的挑战。 相信很多成熟企业都拥有复杂的研发环境：上百条产品线、上千位开发人员、数千个服务。 服务部署在多个地域的多个机房，各种服务运行环境很多。开发语言繁多，例如京东智联云以Go、C++、Java、Node.js为主，少量的Python和PHP，随着业务线不同使用的技术框架不同。调用协议有rest，有非rest的HTTP等，还有自定义TCP协议的…… 如何统一管理？服务治理应运而生。通过服务治理来解决分布式服务和微服务在整体的开发和运行时出现的运维问题，处理服务之间的关系，提供一系列数据依据和工具。 4月21日，技术公开课《六周玩转云原生》第五讲《微服务架构下，服务治理体系的演进历程》由京东云与AI事业部云产品研发部架构师张俊峰为大家详细讲解了服务治理、Spring Cloud微服务架构特点、Service Mesh以及京东智联云在微服务的探索。 以下是精华分享内容，咱们一起来看看： 六周玩转云原生 微服务架构下服务治理体系的演进历程 — 京东云与AI产品研发部架构师 张俊峰 — 1 服务治理演变史 服务治理是随着业务规模的不断扩大
订阅 Istio