-
Notifications
You must be signed in to change notification settings - Fork 878
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
Update manifest to deploy on Kubernetes 1.16. #376
Conversation
Hi @jbrette. Thanks for your PR. I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test If you send a PR to join the github org in kubeflow/internal-acls then you will be able to trigger the tests yourself. |
- Update Deployment apiVersion to apps/v1 - Update Ingress apiVersion to networking.k8s.io
@jlewi @kkasravi Seems to be working ok now.
|
/assign jlewi |
Yeah lots of room for cleanup and improvement in our eng infrastructure.
Could we potentially use an overlay to allow multi-version support? So we'd have an overlay that would change the apiVersion to networking.k8s.io and then folks deploying on 1.16 could include that overlay in the list of applied overlays? |
@@ -1,4 +1,4 @@ | |||
apiVersion: extensions/v1beta1 | |||
apiVersion: extensions/v1beta1 # networking.k8s.io/v1beta1 |
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.
Do you want to add a TODO() about updating this?
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.
@jlewi I will add an issue so that we remember to come back and fix them once with switch to Kubernete 1.14+. I'll add additional instruction on what to pay attention to in Role and ClusterRole definition.
selector: | ||
matchLabels: | ||
chart: gateways | ||
heritage: Tiller |
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.
nit: can we get rid of the heritage label in the selector?
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.
@jlewi I did not want to break anything. The labels, above an below the selectors have to match. Those currently contain Tiller everywhere. You will have to find somebody to run a script and do "grep -v Tiller" on the entire directory structure. We should do that in another PR.
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.
selector: | ||
matchLabels: | ||
chart: gateways | ||
heritage: Tiller |
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.
nit can we get rid of the heritage label in the selector?
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.
not in this PR
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.
matchLabels: | ||
app: jaeger | ||
chart: tracing | ||
heritage: Tiller |
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.
nit: Here and everywhere else get rid of heritage label in selector
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.
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 was surprised that we are still using kubectl 1.10 (in the testing/images/DockerFile) and not something consistent such as 1.12.7
Yeah lots of room for cleanup and improvement in our eng infrastructure.
I had to comment out the "apiVersion: networking.k8s.io/v1beta" in 4 or 5 places, and revert it back extension/v1beta1 because we are still testing with 1.12.7. That change was added in Kubernetes 1.14. Still the Roles are ready (they refer "extensions" and "networking.k8s.io"), so the amount of work next time will be much smaller.
Could we potentially use an overlay to allow multi-version support? So we'd have an overlay that would change the apiVersion to networking.k8s.io and then folks deploying on 1.16 could include that overlay in the list of applied overlays?
We can not.
- Kustomize is using the apiVersion field and the kind field for match resources between the base and the overlay,
- It could be a real problem in some of the kustomize params.xxx. But we are lucky, most of those configuration files are using Ingress, not (Ingress + apiVersion).
Thanks |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jlewi 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 |
…eway Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com>
Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com>
…gressgateway (kubeflow#383)" This reverts commit 8196f65.
…gressgateway (kubeflow#383)" This reverts commit 8196f65.
Which issue is resolved by this Pull Request:
Resolves #
Numerous kubeflow manifests can't deploy on Kubernetes 1.16 #375
Description of your changes:
Checklist:
cd manifests/tests
make generate
make test
This change is