Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

K8s 1.11 fails on generateName when upgrading pipelines #409

Closed
timbuktuu opened this issue Nov 29, 2018 · 2 comments
Closed

K8s 1.11 fails on generateName when upgrading pipelines #409

timbuktuu opened this issue Nov 29, 2018 · 2 comments
Assignees
@IronPan
Labels
area/kfctl kind/bug priority/p1

Comments

@timbuktuu
Copy link

When attempting to upgrade Kubeflow Pipelines by kubectl apply -f deploy.yaml leverages a k8s deployment job with generateName. This works on initial Kubeflow Pipelines cluster creation as one calls kubectl create -f, but fails when upgrading via kubectl apply -f in Kubernetes 1.11. Backing the cluster down to 1.10 allows to work as expected.

'kubectl apply -f https://storage.googleapis.com/ml-pipeline/release/$PIPELINE_VERSION/bootstrapper.yaml"

Similar issues are being reportes elsewhere.
@timbuktuu timbuktuu changed the title K8s 1.11 fails on generateName when upgrade pipelines K8s 1.11 fails on generateName when upgrading pipelines Nov 29, 2018
@vicaire
Copy link
Contributor

vicaire commented Mar 26, 2019

@IronPan, is this fixed as part of the Kubeflow/Pipeline upgrade story?

@IronPan
Copy link
Member

IronPan commented Mar 27, 2019

bootstrapper is now deprecated.

@IronPan IronPan closed this as completed Mar 27, 2019
Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
@zhenghuiwang @k8s-ci-robot
Fix auto deployment (kubeflow#409)
1d4bf0f 
* use kustomize&istio for auto deployment

* use kustomize master
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this issue Oct 22, 2023
@animeshsingh @k8s-ci-robot
Pipe patch (kubeflow#409)
c5f93da 
* pipeline update

* top two paragraphs need to reflect current set of available features

* license change

* addressing review comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@IronPan IronPan

Labels
area/kfctl kind/bug priority/p1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@IronPan @timbuktuu @vicaire