ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
I had the below YAML for my Ingress and it worked (and continues to work): apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: test-ingress namespace: test-layer annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: mylocalhost.com http: paths: - path: / backend: serviceName: test-app servicePort: 5000 However, it
Wanted your guidance on an issue while executing a Kubernetes YAML file. My kubectl version is as follows: Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0", GitCommit:"af46c47ce925f4c4ad5cc8d1fca46c7b77d13b38", GitTreeState:"clean", BuildDate:"2020-12-08T17:59:43Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"windows/amd64"} Server
I need to configure Ingress Nginx on azure k8s, and my question is if is possible to have ingress configured in one namespace et. ingress-nginx and some serivces in other namespace eg. resources? My files looks like so: # ingress-nginx.yaml apiVersion: extensions/v1beta1 kind: Deployment metadata: name: nginx-ingress-controller namespace: ingress-nginx spec:
I have microk8s v1.22.2 running on Ubuntu 20.04.3 LTS. Output from /etc/hosts : 127.0.0.1 localhost 127.0.1.1 main Excerpt from microk8s status : addons: enabled: dashboard # The Kubernetes dashboard ha-cluster # Configure high availability on the current node ingress # Ingress controller for external access metrics-server # K8s Metrics Server for API access
I set up a k8s cluster using kubeadm (v1.18) on an Ubuntu virtual machine. Now I need to add an Ingress Controller. I decided for nginx (but I'm open for other solutions). I installed it according to the docs , section "bare-metal": kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-0.31.1/deploy/static/provider/baremetal/
Trying to figure out how to expose multiple TCP/UDP services using a single LoadBalancer on Kubernetes. Let's say the services are ftpsrv1.com and ftpsrv2.com each serving at port 21. Here are the options that I can think of and their limitations : One LB per svc: too expensive. Nodeport : Want to use a port outside the 30000-32767 range. K8s Ingress : does
I'm adding an Ingress as follows: apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: cheddar spec: rules: - host: cheddar.213.215.191.78.nip.io http: paths: - backend: service: name: cheddar port: number: 80 path: / pathType: ImplementationSpecific but the logs complain: W0205 15:14:07.482439 1 warnings.go:67] extensions/v1beta1 Ingress is deprec
kubernetes