Chris Hoffman

For elasticsearch I'm using a policy like this. ```yaml kind: NetworkPolicy apiVersion: networking.k8s.io/v1 metadata: name: elasticsearch-in-cluster spec: podSelector: matchLabels: navigator.jetstack.io/elasticsearch-cluster-name: logging ingress: - ports: - protocol: TCP port: 9300 from:...

Apparently there is a new dependency on DNS that did not exist in the standalone pilot & helm install. I had to add network policy entries for DNS: ~~~yaml -...

I have a similar problem on node.js 5.4.0 and `triton ssh`. I can see that the ssh command has executed successfully, but it doesn't appear to be connected or piped...

#2022 was PR from a long time ago directly around this before the `tectonic_iscsi_enabled` flag even existed

I am seeing a similar provisioning problem as well. The problem has to do with a fresh VM with attached data disks. The provision fails and in the boot logs...

I want to add if this isn't clear. You can not currently provision VMs that use data disks with the current stable Container Linux version on Azure due to this...

@euank you’re right this missing module seems to be fine since it exists when deploying without data disks. The problem I have is that the same ignition config works on...

@justaugustus yes, it seems to be flakey in so much that new OS releases seem to fail for some period of time and then they will work. For example, 1520.9.0...

I'd be interested in knowing if you guys came up with workarounds for this. The only solution I have come up with is using a `?format=` on the requests. This...

I've seen this alternative before. I hadn't looked too closely at it, but now I see the main difference in what types of paths each offer. Perhaps there is room...