https://flyte.org logo
Join Slack
Powered by
<@UNW4VP36V> I saw <your post> a few weeks back sa...
# announcements
n
@Haytham Abuelfutuh I saw your post a few weeks back saying that Flyte v0.19.2 helm chart would work with K8s 1.22+. I see this PR was successfully merged that makes the necessary helm updates. However, when I try and run using 
helm
it does not seem to be pulling in all the changes. Specifically 
kind: Ingress
and 
kind: CustomResourceDefinition
are still using 
v1beta1
. I have run
Copy code
helm repo update
helm template --version v0.19.2 ...
Copy code
kubectl apply -f flyte_generated_dev.yaml -n flyte

serviceaccount/flytescheduler created
serviceaccount/flyte-pod-webhook created
secret/flyte-admin-secrets created
secret/flyte-secret-auth created
secret/db-pass created
secret/flyte-pod-webhook created
configmap/flyte-admin-config created
configmap/clusterresource-template created
configmap/flyte-clusterresourcesync-config created
configmap/flyte-console-config created
configmap/datacatalog-config created
configmap/flyte-scheduler-config created
configmap/flyte-propeller-config created
<http://clusterrole.rbac.authorization.k8s.io/flyteadmin|clusterrole.rbac.authorization.k8s.io/flyteadmin> created
<http://clusterrole.rbac.authorization.k8s.io/flytepropeller|clusterrole.rbac.authorization.k8s.io/flytepropeller> created
<http://clusterrole.rbac.authorization.k8s.io/flyte-pod-webhook|clusterrole.rbac.authorization.k8s.io/flyte-pod-webhook> created
<http://clusterrolebinding.rbac.authorization.k8s.io/flyteadmin-binding|clusterrolebinding.rbac.authorization.k8s.io/flyteadmin-binding> created
<http://clusterrolebinding.rbac.authorization.k8s.io/flytepropeller|clusterrolebinding.rbac.authorization.k8s.io/flytepropeller> created
<http://clusterrolebinding.rbac.authorization.k8s.io/flyte-pod-webhook|clusterrolebinding.rbac.authorization.k8s.io/flyte-pod-webhook> created
service/flyteadmin created
service/flyteconsole created
service/datacatalog created
service/flyte-pod-webhook created
deployment.apps/flyteadmin created
deployment.apps/flyteconsole created
deployment.apps/datacatalog created
deployment.apps/flytescheduler created
deployment.apps/flytepropeller created
deployment.apps/flyte-pod-webhook created
Warning: batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob
cronjob.batch/syncresources created
unable to recognize "flyte_generated_dev.yaml": no matches for kind "CustomResourceDefinition" in version "<http://apiextensions.k8s.io/v1beta1|apiextensions.k8s.io/v1beta1>"
unable to recognize "flyte_generated_dev.yaml": no matches for kind "Ingress" in version "<http://networking.k8s.io/v1beta1|networking.k8s.io/v1beta1>"
Am I missing something?
r
I got this issue last week, try do 
kubectl apply -f <https://raw.githubusercontent.com/rodrigobaron/flyte/issues/k8s_compt/deployment/sandbox/flyte_helm_generated.yaml> -n flyte
<- this is an open PR
h
@Nicholas LoFaso are you on 1.22 in K8s?
I merged @Rodrigo Baron’s PR… will release a beta version of flyte now…
n
@Haytham Abuelfutuh Hi yes we are on 1.22 for one of our dev clusters on GCP
I think our issue is getting the 
helm template
command to resolve this piece of code correctly:
Copy code
{{- if $.Capabilities.APIVersions.Has "<http://networking.k8s.io/v1/Ingress|networking.k8s.io/v1/Ingress>" }}
apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
{{- else }}
apiVersion: <http://networking.k8s.io/v1beta1|networking.k8s.io/v1beta1>
{{- end }}
I tried 
helm install
and it works 😄. So it seems 
helm template
for some reason thinks we’re on an older version of k8s. Even if I specify 
--api-versions
h
what did you pass in 
--api-versions
?
you will have to pass the full string we are searching for like this: https://github.com/flyteorg/flyte/blob/master/script/generate_helm.sh#L11
🙏 1
🎉 1
n
I was passing in the k8s version 1.22.1 not the API list. Thanks for your help!
h
165 Views
Open in Slack
PreviousNext
Powered by