rnkhouse

@bjornmagnusson Is there any way to check if the chart is being installed or not in `draft task`? So, no fresh install if the chart is already there.

@lou-lan It's service located in istio-system namespace. cluster 1: istio-internal-ingressgateway LoadBalancer 10.6.38.143 10.2.10.2 15021:32225/TCP,80:32098/TCP,443:30775/TCP 54d app=istio-internal-ingressgateway,istio=internal-ingressgateway apiVersion: v1 kind: Service metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{"service.beta.kubernetes.io/azure-load-balancer-internal":"true"},"labels":{"app":"istio-internal-ingressgateway","install.operator.istio.io/owning-resource":"unknown","istio":"internal-ingressgateway","istio.io/rev":"default","operator.istio.io/component":"IngressGateways","release":"istio"},"name":"istio-internal-ingressgateway","namespace":"istio-system"},"spec":{"loadBalancerIP":"10.2.10.2","ports":[{"name":"status-port","port":15021,"protocol":"TCP","targetPort":15021},{"name":"http2","port":80,"protocol":"TCP","targetPort":8080},{"name":"https","port":443,"protocol":"TCP","targetPort":8443}],"selector":{"app":"istio-internal-ingressgateway","istio":"internal-ingressgateway"},"type":"LoadBalancer"}} service.beta.kubernetes.io/azure-load-balancer-internal: "true" creationTimestamp: "2022-03-17T22:55:14Z" finalizers:...

@lou-lan Actually, we need to point 2 clusters services with one domain. So, on azure DNS, there should be 2 A records for the same domain. I think my issue...

@darkn3rd Yes. RBAC is enabled. below is the config: --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: external-dns rules: - apiGroups: [""] resources: ["services","endpoints","pods"] verbs: ["get","watch","list"] - apiGroups: ["extensions","networking.k8s.io"] resources: ["ingresses"]...

@lou-lan @darkn3rd Can you please help here with what can be done to use the same DNS from multiple clusters?

no @flemzord

I tried with both actually. Same result. @aion-Ross

It looks like from drivers perspective it's fine. There need to be some changes from `aionminer` code so that it supports K80 and P100 (cloud-based GPUs). Waiting for the update.

I am getting the same error: Error: cannot POST /bitbucket-scmsource-hook/notify/ (500) at Response.toError (/usr/local/lib/node_modules/smee-client/node_modules/superagent/lib/node/response.js:94:15) at ResponseBase._setStatusProperties (/usr/local/lib/node_modules/smee-client/node_modules/superagent/lib/response-base.js:123:16) at new Response (/usr/local/lib/node_modules/smee-client/node_modules/superagent/lib/node/response.js:41:8) at Request._emitResponse (/usr/local/lib/node_modules/smee-client/node_modules/superagent/lib/node/index.js:752:20) at Stream.parser (/usr/local/lib/node_modules/smee-client/node_modules/superagent/lib/node/index.js:916:38) at Stream.emit (events.js:189:13)...

Temporary solution: Use version 1.9.3