white-yak-77603
02/17/2023, 3:34 PMaverage-finland-92144
02/17/2023, 5:05 PMinline
section like this (example):
inline:
task_resources:
defaults:
cpu: 100m
memory: 100Mi
storage: 100Mi
limits:
memory: 1Gi
Take into account that Limits are only used by Flyte for validation so your deployed Pods could have a different behaviour. Take a look at this section of the docs
https://docs.flyte.org/en/latest/concepts/admin.html#task-resource-defaults
Does this answer your question?white-yak-77603
02/17/2023, 5:12 PMwhite-yak-77603
02/17/2023, 5:15 PMinline:
plugins:
k8s:
default-pod-template-name: flyte-template
Current setup inside helm chart. flyte-template defined as usual:
apiVersion: v1
kind: PodTemplate
metadata:
name: flyte-template
namespace: flyte
template:
spec:
<some settings>
average-finland-92144
02/17/2023, 5:46 PMdefault-pod-template-name
still configurable for propeller on single binary?freezing-boots-56761
white-yak-77603
02/17/2023, 6:00 PMfreezing-boots-56761
freezing-boots-56761
freezing-boots-56761
freezing-boots-56761
> cat test-pod-template.yaml
apiVersion: v1
kind: PodTemplate
metadata:
name: test-template
namespace: flyte
template:
spec:
containers:
- name: default
image: <http://docker.io/rwgrim/docker-noop|docker.io/rwgrim/docker-noop>
env:
- name: FOO
value: BAR
> kubectl get po fb5116731e64348e4919-n0-0 -n flytesnacks-development -o jsonpath='{.spec.containers[0].env[0]}'
{"name":"FOO","value":"BAR"}%
white-yak-77603
02/17/2023, 7:24 PMinline:
plugins:
k8s:
default-pod-template-name: flyte-template
freezing-boots-56761
inline:
plugins:
k8s:
default-pod-template-name: test-template
thankful-minister-83577
white-yak-77603
02/17/2023, 7:42 PMName: flyte-backend-flyte-binary-config
Namespace: flyte
Labels: <http://app.kubernetes.io/instance=flyte-backend|app.kubernetes.io/instance=flyte-backend>
<http://app.kubernetes.io/managed-by=Helm|app.kubernetes.io/managed-by=Helm>
<http://app.kubernetes.io/name=flyte-binary|app.kubernetes.io/name=flyte-binary>
<http://app.kubernetes.io/version=1.16.0|app.kubernetes.io/version=1.16.0>
<http://helm.sh/chart=flyte-binary-v1.3.0|helm.sh/chart=flyte-binary-v1.3.0>
Annotations: <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: flyte-backend
<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: flyte
Version 1.3thankful-minister-83577
<some settings>
?thankful-minister-83577
white-yak-77603
02/17/2023, 8:11 PMapiVersion: v1
kind: PodTemplate
metadata:
name: flyte-template
namespace: flyte
template:
spec:
volumes:
- name: dshm
emptyDir:
medium: Memory
sizeLimit: 64000Mi
containers:
- name: default
image: <http://docker.io/rwgrim/docker-noop|docker.io/rwgrim/docker-noop>
volumeMounts:
- mountPath: /dev/shm
name: dshm
This is full template configwhite-yak-77603
02/17/2023, 8:16 PMhallowed-mouse-14616
02/17/2023, 8:32 PMPodTemplate
in a more specific namespace? For example, if you are running the task in flytesnacks-development
then create the PodTemplate
there. So propeller looks for the default PodTemplate
in the namespace that it is running in, which defaults to flyte
, but perhaps in your setup this is different, or may end up being set differently. If the PodTemplate
works in a more specific namespace then we will know a little more.hallowed-mouse-14616
02/17/2023, 8:33 PMPodTemplate
registration. Something along the lines of "registered PodTemplate 'flyte-template:flytesnacks-development' in store". Then we can make sure propeller is detecting the `PodTemplate`swhite-yak-77603
02/17/2023, 8:36 PME0217 20:35:26.548098 7 reflector.go:138] pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: Failed to watch *v1.PodTemplate: failed to list *v1.PodTemplate: podtemplates is forbidden: User "system:serviceaccount:flyte:flyte-backend-flyte-binary" cannot list resource "podtemplates" in API group "" at the cluster scope
hallowed-mouse-14616
02/17/2023, 8:43 PMwhite-yak-77603
02/17/2023, 8:51 PMfreezing-boots-56761
thankful-minister-83577