Shivarp1 commented on issue #10722:
URL: https://github.com/apache/airflow/issues/10722#issuecomment-692174595
I have had the resource quota turned on and a limit range also specified
for the namespace
If it's also working for others, with limits set, you can close this Jira.
Thanks,
-------------------
my settings..
kubectl get resourcequota -n shivarp_namespace -o yaml -->
..
,kind: ResourceQuota
spec:
hard:
limits.cpu: "100"
limits.memory: 100Gi
requests.cpu: "10"
requests.memory: 10Gi
...
staus:
hard:
limits.cpu: "100"
limits.memory: 100Gi
requests.cpu: "10"
requests.memory: 10Gi
-----------------------------------
kubectl get limitRange -n shivarp_namespace -o yaml
,, kind: LimitRange
spec:
limits:
- default:
ephemeral-storage: 100Mi
defaultRequest:
ephemeral-storage: 100Mi
max:
ephemeral-storage: 1Gi
maxLimitRequestRaio:
ephemeral-storage: "1"
min:
ephemeral-storage: 1Mi
type: Container
On Mon, Sep 14, 2020 at 9:49 AM Paola Peraza Calderon <
[email protected]> wrote:
> Hi @Shivarp1 <https://github.com/Shivarp1> ! @dimberman
> <https://github.com/dimberman> looked into this at Astronomer and found
> that if your cluster has resource quotas turned on without a default
> limitRange specified, this will happen.
>
> This can be checked with kubectl get resourcequota -n <namespace> -o yaml
> and kubectl get limitRange -n <namespace> -o yaml
>
> @dimon222 <https://github.com/dimon222> Let me know if that's in line
> with the behavior you're seeing as well. Given the above, we're not looking
> into this for 1.10.13 but happy to take a closer look if you're still
> running into trouble.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/airflow/issues/10722#issuecomment-692108400>,
> or unsubscribe
>
<https://github.com/notifications/unsubscribe-auth/ACJQXPXFPK3MDKXYQFXTYR3SFYURPANCNFSM4QWZYY3Q>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
