azure-kubernetes

AML - Web service TimeoutError

限于喜欢 提交于 2020-08-08 05:24:12
问题 We created a webservice endpoint and tested it with the following code, and also with POSTMAN. We deployed the service to an AKS in the same resource group and subscription as the AML resource. UPDATE: the attached AKS had a custom networking configuration and rejected external connections. import numpy import os, json, datetime, sys from operator import attrgetter from azureml.core import Workspace from azureml.core.model import Model from azureml.core.image import Image from azureml.core

Error on Websocket Implementation on Azure Kubernetes Cluster Not working

爷,独闯天下 提交于 2020-07-23 07:17:18
问题 I am trying to make the websocket service work on Azure Kubernetes Cluster on our organization environment. My existing environment also have REST api and Angular application working on ingress with ssl. But when I added the websocket service on the ingress it is not working. So, I tried to use Azure Free Subscription to first implement the same WITHOUT SSL. For my applications I enabled Http Routing and using the annotation addon-http-application-routing. I am getting below error. 'ws://40

Error on Websocket Implementation on Azure Kubernetes Cluster Not working

自作多情 提交于 2020-07-23 07:16:08
问题 I am trying to make the websocket service work on Azure Kubernetes Cluster on our organization environment. My existing environment also have REST api and Angular application working on ingress with ssl. But when I added the websocket service on the ingress it is not working. So, I tried to use Azure Free Subscription to first implement the same WITHOUT SSL. For my applications I enabled Http Routing and using the annotation addon-http-application-routing. I am getting below error. 'ws://40

Error on Websocket Implementation on Azure Kubernetes Cluster Not working

爷,独闯天下 提交于 2020-07-23 07:15:06
问题 I am trying to make the websocket service work on Azure Kubernetes Cluster on our organization environment. My existing environment also have REST api and Angular application working on ingress with ssl. But when I added the websocket service on the ingress it is not working. So, I tried to use Azure Free Subscription to first implement the same WITHOUT SSL. For my applications I enabled Http Routing and using the annotation addon-http-application-routing. I am getting below error. 'ws://40

Can't get either Postgres permissions or PVC working in AKS

为君一笑 提交于 2020-07-10 07:56:41
问题 These are pretty much the steps I have followed in order. Basically what is outlined in the documentation: https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv azure-storage-claim.yaml kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: test-app-sc provisioner: kubernetes.io/azure-file mountOptions: - dir_mode=0777 - file_mode=0777 - uid=1000 - gid=1000 - mfsymlinks - nobrl - cache=none parameters: skuName: Standard_LRS location: westus azure-storage.yaml apiVersion:

kubernetes timescaledb statefulset: Changes lost on pod recreation

心已入冬 提交于 2020-06-17 15:12:17
问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

kubernetes timescaledb statefulset: Changes lost on pod recreation

允我心安 提交于 2020-06-17 15:11:58
问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

kubernetes timescaledb statefulset: Changes lost on pod recreation

廉价感情. 提交于 2020-06-17 15:10:27
问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

kubernetes timescaledb statefulset: Changes lost on pod recreation

我的梦境 提交于 2020-06-17 15:09:46
问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

kubernetes timescaledb statefulset: Changes lost on pod recreation

前提是你 提交于 2020-06-17 15:08:23
问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql