azure-kubernetes

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 Kubernetes, I have no idea about how to find the error log in Kibana instance. Can anyone help me on

I allocated resource to 1 pod only with 650MB/30% of memory (with other built-in pods, limit memory is 69% only) However, when the pod handling process, the usage of pod is within 650MB but overall usage of node is 94%. Why does it happen because it supposed to have upper limit of 69%? Is it due to other built-in pods which did not set limit? How to prevent this as sometimes my pod with error if usage of Memory > 100%? My allocation setting ( kubectl describe nodes ): Memory usage of Kubernetes Node and Pod when idle: kubectl top nodes kubectl top pods Memory usage of Kubernetes Node and Pod

I've tried un-registering and re-registering and it just keeps getting stuck. No logs I can see so I'm not really sure what to do... Has anyone experienced this before? It appears that there was some issue, which is now mitigated. Check your Service Health/Resource Health page. The ‘Service Health’ - Service issues view shows any ongoing problems in Azure services that are impacting your resources. You can understand when the issue began, and what services and regions are impacted. You can also read the most recent update to understand what Azure is doing to resolve the issue. Resource health

We have configured our Azure Kubernetes Clusters to use Azure Active Directory RBAC. This means when using kubectl we need to first authenticate as an AD user (usually done through manually completing device code authentication via the web browser). We have configured this almost exactly as per the MSDN article Integrate Azure Active Directory with Azure Kubernetes Service . The issue is that this authentication is now also required for Kubernetes build/release tasks in Azure DevOp Pipelines, for example when we run kubectl apply: 2019-01-02T08:48:21.2070286Z ##[section]Starting: kubectl apply

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 in these files, and what those commands are compatible with (for example, I've noticed that 'kind: