-
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
kustomize kf pipeline #1305
kustomize kf pipeline #1305
Conversation
artifactRepository: | ||
{ | ||
s3: { | ||
bucket: mlpipeline, |
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.
Maybe rename mlpipeline
to kubeflow-pipelines
or kf-pipelines
here and in other places?
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.
we can do a renaming in a dedicated PR. for now it might be better to align with the existing one.
{ | ||
executorImage: argoproj/argoexec:v2.2.0, | ||
artifactRepository: | ||
{ |
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.
Is this indent correct and do we need curly braces?
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.
it's just to align with the existing one.
/assign @Liujingfang1 |
@IronPan: GitHub didn't allow me to assign the following users: Liujingfang1. Note that only kubeflow members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
1 similar comment
@IronPan: GitHub didn't allow me to assign the following users: Liujingfang1. Note that only kubeflow members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
manifests/README.md
Outdated
- Edit [kustomization.yaml](namespaced-install/kustomization.yaml) namespace section to FOO | ||
- Then run | ||
``` | ||
kubectl kustomize . | kubectl create -f - |
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.
We don't recommend to use kubectl create
. You can use
kubectl kustomize . | kubectl apply -f -
Or
kubectl apply -k .
Or (with Kustomize installed)
kustomize build . | kubectl apply -f -
.
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.
great catch.
|
||
Or if you deploy using kustomize | ||
``` | ||
kubectl kustomize . | kubectl delete -f - |
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.
Similarly, here you have multiple choices
kubectl kustomize . | kubectl delete -f -
or
kubectl delete -k -
or (with kustomize installed)
kustomize build . | kubectl delete -f -
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.
great good to know. i'll keep it in mirror to the command above, to make it easy to understand.
kubectl create clusterrolebinding your-binding --clusterrole=cluster-admin --user=[your-user-name] | ||
``` | ||
|
||
# Customization |
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.
Is there any other customization that user want to perform other than namespace?
If there is, I suggest to add instructions as well.
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.
I'm plan to add it incrementally. want to use this PR as a good baseline.
does that sounds good?
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.
sounds good to me. Feel free to ping me when you add more customization.
- ml-pipeline-scheduledworkflow-deployment-patch.yaml | ||
|
||
vars: | ||
- name: NAMESPACE |
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.
This is a smart way of keeping the namespace the same as the namespace directive in kustomization.yaml. Good job.
|
||
# Customization | ||
|
||
## Change deploy namespace |
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.
Let's keep the base unchanged. It is recommend to create overlays and add customization in the overlay.
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.
OK I'd picture the base/ dir to be unchanged, and people add overlay if needed. regarding this comment, do you just want me to call this out, or something else i need to do?
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.
Call this out and explain that with all customization in the overlay, it is easy to understand what has been changed.
@@ -0,0 +1,26 @@ | |||
apiVersion: v1 | |||
kind: ConfigMap |
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.
We have configMapGenerator
and secretGenerator
which can the pods auto pick up the latest configmaps or secrets if they have changed. You can read more info here.
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.
Thanks for the doc. It looks great. Based on the doc it seems gen is optional.
The idea here is to reduce the templating "magic" to minimum and having the spec as close to the plain yaml as possible.
(it was a hard lesson learnt by using ksonnet and forgive me being overly cautious on it :P)
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: IronPan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: IronPan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
sample tests are flaky. |
* go mod tidy * Update k8s libs to 0.19.2, fix issues, and run make tests
…ubeflow#1343) * parent a0a52f8 author Manasvi Tickoo <MTICKOO@bloomberg.net> 1611275174 -0500 committer Manasvi Tickoo <MTICKOO@bloomberg.net> 1612370131 -0500 1159 - cloudevent support ofr kfserving PR comments Fix clpudevent headers Add unit test for cloud event messages Add avro unit test Add avro to kfserving requirements.txt PR comments kfserving check ce-contenttyp before unmarshalling Update k8s libraries to 0.19.2 (kubeflow#1305) * go mod tidy * Update k8s libs to 0.19.2, fix issues, and run make tests * Handle ce to_binary return type wile building resp
This change is