azure-kubernetes

问题 I have a Container with a very simple Web App uploaded to an Azure Container Registry. I have an AKS cluster created. Now I want to deploy my container into AKS. I've found a number of tutorials on this, but they all seem to refer to YAML files that have very little, or no, explanation. I, therefore, have two questions: Is it necessary to use a YAML file to achieve this (kubectl create -f myyaml.yml)? (If not, what are the alternatives) Is there any documentation for exactly what needs to be

问题 I have a working Cluster with services that all respond behind a helm installed Ingress nGinx running on Azure AKS. This ended up being Azure specific. My question is: Why does my connection to the services / pods in this cluster periodically get severed (apparently by some sort of idle timeout), and why does that connection severing appear to also coincide with my Az AKS Browse UI connection getting cut? This is an effort to get a final answer on what exactly triggers the time-out that

问题 I have a working Cluster with services that all respond behind a helm installed Ingress nGinx running on Azure AKS. This ended up being Azure specific. My question is: Why does my connection to the services / pods in this cluster periodically get severed (apparently by some sort of idle timeout), and why does that connection severing appear to also coincide with my Az AKS Browse UI connection getting cut? This is an effort to get a final answer on what exactly triggers the time-out that

问题 I've set-up an AKS cluster and am now trying to connect to it. My deployment YAML is here: apiVersion: v1 kind: Pod spec: containers: - name: dockertest20190205080020 image: dockertest20190205080020.azurecr.io/dockertest ports: - containerPort: 443 metadata: name: my-test If I run the dashboard, I get this: Which looks like it should be telling me the external endpoint, but isn't. I have a theory that this is because the Yaml file is only deploying a Pod, which is in some way not able to

问题 I'm setting up ELK services in Azure Kubernetes Service. But I only see this error: "Kibana server is not ready yet" I'm using Helm to install the stable/elastic-stack release without any changes (default for everything) in AKS. helm install --name elk stable/elastic-stack And I also added an ingress controller to expose the Kibana server to public. However, I only see "Kibana server is not ready yet" error. I've checked the Kibana pod is running, as well as the ElasticSearch. As a newbie in

问题 My metrics-server was sudden not working and got below information: $ kubectl get apiservices |egrep metrics v1beta1.metrics.k8s.io kube-system/metrics-server False (MissingEndpoints) I tried to implement below but still not okay: $ git clone https://github.com/kubernetes-incubator/metrics-server.git $ cd metrics-server $ kubectl apply -f deploy/1.8+/ Please advise, thanks. 回答1: in this case the solution was to upgrade kubernetes version for nodes to reapply metrics server 来源： https:/

问题 Building a docker image using Docker in Docker is not working. before_script: - apt-get update && apt-get install -y apt-transport-https - apk add --update curl && rm -rf /var/cache/apk/ - curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl - chmod +x ./kubectl - mv ./kubectl /usr/local/bin/kubectl build: stage: build image: docker:dind services: - docker:dind variables:

问题 I created my AKS cluster in the Azure portal using the 'Create Kubernetes cluster' functionality and allowed it to create a new Service Principal. I started to wonder about expiry of the credentials this principal uses. Hoping to avoid an issue with K8s talking to Azure on credential expiry, I started looking at the account which had been created. What I'm seeing if I run: az ad app show --id <app Id> ... is the account manifest apart from the password expiry. I don't need to see the password

问题 I have a service that I want to expose publicly over http running on AKS. I created a Kubernetes cluster and enabled the HTTP addon following these instructions here. I then launched a service myservicea in namespace mynamespace . And then I created an ingress controller for using the following configuration. --- apiVersion: extensions/v1beta1 kind: Ingress metadata: name: myservicea-ingress namespace: mynamespace annotations: kubernetes.io/ingress.class: addon-http-application-routing spec:

问题 I'm getting the node IP address instead of the client IP. Is it possible to get the client IP with a service of type LoadBalancer ? Or will I need to use a ingress controller? apiVersion: v1 kind: Service metadata: name: app-svc labels: name: app-svc environment: dev spec: type: LoadBalancer loadBalancerIP: XXX.XXX.XXX.XXX ports: - name: http-port port: 80 targetPort: 80 protocol: TCP selector: name: app-deploy 回答1: You do not need any Ingress controller. However it is required to set the