-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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.
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
Manifests: Rename metadata gRPC server's resources to metadata-grpc-* #3108
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -76,6 +76,24 @@ kubectl kustomize base/crds | kubectl delete -f - | |
|
||
``` | ||
|
||
## Upgrade | ||
Note - Do **NOT** follow these instructions if you are upgrading KFP in a | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you include a link to https://www.kubeflow.org/docs/pipelines/installation/overview/ for background information of what a "proper kubeflow installation" means? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd suggest including "when upgrading from version < xxx, you need to do this". The exact version is still unknown now, but you can put a placeholder there. We will follow up before the release. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For the proper kubeflow installation, you mean the getting-started link instead, right? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I pushed the change with the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see, sounds good to me |
||
[proper Kubeflow installation](https://www.kubeflow.org/docs/started/getting-started/). | ||
|
||
If you have already deployed a standalone KFP installation of version prior to | ||
0.2.5 and you want to upgrade it, make sure the following resources do not | ||
exist: `metadata-deployment`, `metadata-service`. | ||
``` | ||
kubectl -n <KFP_NAMESPACE> get deployments | grep metadata-deployment | ||
kubectl -n <KFP_NAMESPACE> get service | grep metadata-service | ||
``` | ||
|
||
If they exist, you can delete them by running the following commands: | ||
``` | ||
kubectl -n <KFP_NAMESPACE> delete deployment metadata-deployment | ||
kubectl -n <KFP_NAMESPACE> delete service metadata-service | ||
``` | ||
|
||
## Troubleshooting | ||
|
||
### Permission error installing Kubeflow Pipelines to a cluster | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason on why prefer renaming it?
Is it more for understand the meaning? I agree with you that it should be named like this PR. Background: rename deployment in manifests is treated as not-back-compatibile in GCP Marketplace. It means we need to bump version. If just to make the name be more understandable, I may prefer you hold this CL or ~1-2 weeks so that we put it to KFP 0.4.x
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The purpose is to be consistent with kubeflow deployment.
We've released 0.3.0, even if we hold this, next release won't be backward compatible. So I think there is no reason to hold it.