-
**Describe the bug**
A simple task started on my laptop with a worker on an AWS EC2 instance never completes. There is just an endlessly repeating:
```
2021-01-05 13:23:09.876 parsl.dataflow.stra…
-
## Feature request description
Allow the possibility to run a script **before** the EC2 Instance Compute Node is terminated. A suitable location may be the [scaling section](https://docs.aws.amazon…
-
### Description
Hi, I read documentation and have a question about the how the upgrade process should look like.
1. First update CRDs
`kubectl apply -f https://raw.githubusercontent.com/aws/karpe…
-
### Description
**Observed Behavior**:
We have a `default` nodePool in one availability zone (`a`) with higher weight and a second `fallback` nodePool in another availability zone (`b`) with lower w…
-
Created by: @bboylilshaw
Source: https://github.com/RedisGraph/RedisGraph/issues/722
Hi, I got few questions about the redisgraph distribution support.
1. does redisgraph support distribution at this…
-
Currently Spark has it's own script for launching EC2 instances: https://spark.apache.org/docs/0.8.1/ec2-scripts.html and [source](https://github.com/apache/spark/blob/master/ec2/spark_ec2.py).
I fil…
-
Warning FailedScheduling 66s default-scheduler 0/1 nodes are available: 1 Insufficient aws.ec2.nitro/nitro_enclaves.
To address this, I need to manually label worker node with "$ kubectl labe…
-
### What is the problem?
Scheduling with the default of 0 lifetime CPUs for actors seems to cause issues with cluster utilization.
If you run the below script that should consume all CPUs i…
-
### What are you trying to do?
After some experimentation, it appears Split DNS will only work for Tailscale nodes if MagicDNS is also enabled. We want to be able to disable MagicDNS (to prevent leak…
-
### Description
**Observed Behavior**:
- Nodes are running and healthy
- Suddenly the pods of a node turn into Terminating state
- Validating the node is in NotReady state
- Description of the …