Kubernetes

Using nginx as Forward proxy in kubernetes

99封情书 提交于 2021-02-10 09:47:34
问题 I am really new to kubernetes and nginx. I am able to use it as a reverse-proxy by setting up ingress resource, however, I am not sure about how should I use it to forward the request from kubernetes to a particular host. My case is as follows: I have a container running in kubernetes pod which access an external api url (example www.xxx.com) with some parameters, however, because I have blocked the outgoing requests for all the pods, it can not access that api url. To solve this I want to

Using nginx as Forward proxy in kubernetes

ぃ、小莉子 提交于 2021-02-10 09:47:07
问题 I am really new to kubernetes and nginx. I am able to use it as a reverse-proxy by setting up ingress resource, however, I am not sure about how should I use it to forward the request from kubernetes to a particular host. My case is as follows: I have a container running in kubernetes pod which access an external api url (example www.xxx.com) with some parameters, however, because I have blocked the outgoing requests for all the pods, it can not access that api url. To solve this I want to

SSE broken after deploying with Kubernetes and connecting via Ingress

有些话、适合烂在心里 提交于 2021-02-10 08:44:08
问题 I've a ReactJS client which uses EventStream and a golang backend which implements SSE. Everything seemed to work when I connected my browser to the backend running on localhost, as well as when my backend was running on k8s with port forwarding. As soon as I created an ingress with a hostname (so that I don't have to port-forward all the time) SSE stopped working. I still see that the client sends the request and this request is received and registered by the backend. However, when and event

Kubernetes logs command TLS handshake timeout

守給你的承諾、 提交于 2021-02-10 08:17:11
问题 I am running the open source kube version 1.9, getting TLS handshake timeout error while running the kubectl logs command, other kubectl commands are working fine. #:/etc/kubernetes/pki> kubectl get pods NAME READY STATUS RESTARTS AGE app1-9 1/1 Running 0 2d #:/etc/kubernetes/pki> kubectl logs counter Error from server: Get https://XX.XX.XX.XXXX:10250/containerLogs/default/counter/count: net/http: TLS handshake timeout kubectl version is: Client Version: version.Info{Major:"1", Minor:"9",

Kubernetes logs command TLS handshake timeout

百般思念 提交于 2021-02-10 08:13:46
问题 I am running the open source kube version 1.9, getting TLS handshake timeout error while running the kubectl logs command, other kubectl commands are working fine. #:/etc/kubernetes/pki> kubectl get pods NAME READY STATUS RESTARTS AGE app1-9 1/1 Running 0 2d #:/etc/kubernetes/pki> kubectl logs counter Error from server: Get https://XX.XX.XX.XXXX:10250/containerLogs/default/counter/count: net/http: TLS handshake timeout kubectl version is: Client Version: version.Info{Major:"1", Minor:"9",

Kubernetes logs command TLS handshake timeout

大憨熊 提交于 2021-02-10 08:08:06
问题 I am running the open source kube version 1.9, getting TLS handshake timeout error while running the kubectl logs command, other kubectl commands are working fine. #:/etc/kubernetes/pki> kubectl get pods NAME READY STATUS RESTARTS AGE app1-9 1/1 Running 0 2d #:/etc/kubernetes/pki> kubectl logs counter Error from server: Get https://XX.XX.XX.XXXX:10250/containerLogs/default/counter/count: net/http: TLS handshake timeout kubectl version is: Client Version: version.Info{Major:"1", Minor:"9",

使用Sealos + Longhorn部署KubeSphere v3.0.0

柔情痞子 提交于 2021-02-10 07:54:42
本文来自 KubeSphere 社区用户 Will,演示如何使用 Sealos + Longhorn 部署一个带有持久化存储的 Kubernetes 集群,然后使用 ks-installer 在该集群上部署 KubeSphere 3.0.0。这是一篇最适合小白初次上手的 KubeSphere 3.0.0 快速部署和体验的文章🚀。 Sealos 简介 Sealos ( https://sealyun.com/ ),只能用丝滑一词形容的 Kubernetes 高可用安装工具,一条命令,离线安装,包含所有依赖,内核负载不依赖 haproxy keepalived,纯 Golang 开发,99 年证书,支持 v1.16 ~ v1.19。 Longhorn简介 Longhorn ( https://www.rancher.cn/longhorn )是 Rancher 开源的 Kubernetes 高可用持久化存储,提供简单的增量快照和备份,支持跨集群灾难恢复。 KubeSphere 简介 KubeSphere( https://kubesphere.io ) 是在 Kubernetes 之上构建的以应用为中心的多租户容器平台,完全开源,支持多云与多集群管理,提供全栈的 IT 自动化运维的能力,简化企业的 DevOps 工作流。KubeSphere 提供了运维友好的向导式操作界面

Running A cronjob in a pod in Kubernetes

元气小坏坏 提交于 2021-02-10 07:48:56
问题 I have a backend nodeJS application running in a kubernetes cluster. Now I want to run two cron jobs to be scheduled every month. The cron jobs are in a JS file. How do I create a job that runs those JS files in the pod running that service every month using Kubernetes ? This link gives a basic understanding of how it works but I am a little confused on how to run it for a specific service and on a specific pod https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#writing-a

In Kubernetes what is deletecollection?

↘锁芯ラ 提交于 2021-02-10 06:58:41
问题 When listing all the API resources in K8s you get: $ kubectl api-resources -owide NAME SHORTNAMES APIGROUP NAMESPACED KIND VERBS bindings true Binding [create] componentstatuses cs false ComponentStatus [get list] configmaps cm true ConfigMap [create delete deletecollection get list patch update watch] endpoints ep true Endpoints [create delete deletecollection get list patch update watch] events ev true Event [create delete deletecollection get list patch update watch] limitranges limits

openssl giving Kubernetes Ingress Controller Fake Certificate

馋奶兔 提交于 2021-02-10 06:55:45
问题 I have configured ssl certificate, if I visit https://<domain>.com , I see that my certificate is configured successfully but when I try to check certificate by following command openssl s_client -connect <domain>.com:443 | openssl x509 -noout -subject -issuer i am getting Kubernetes Ingress Controller Fake Certificate My ingres config is : annotations: nginx.ingress.kubernetes.io/ssl-redirect: 'true' nginx.ingress.kubernetes.io/from-to-www-redirect: 'true' name: nginx-echo spec: tls: - hosts