Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Sep 12, 2023. It is now read-only.

Conversation

@Jeffwan
Copy link
Member

@Jeffwan Jeffwan commented Mar 30, 2021

  1. Upgrade k8s dependency to 1.19
  2. 1.18 client-go add context and extra options. Adapt to the new changes.
  3. Upgrade golang to 1.15 to match golang used in 1.19

Signed-off-by: Jiaxin Shan [email protected]

@Jeffwan
Copy link
Member Author

Jeffwan commented Mar 30, 2021

/hold

@Jeffwan
Copy link
Member Author

Jeffwan commented Mar 30, 2021

/cc @Thor-wl @shinytang6 for extra review due to blocked PR. #123
/cc @kubeflow/wg-training-leads

@google-oss-robot
Copy link

@Jeffwan: GitHub didn't allow me to request PR reviews from the following users: Thor-wl, shinytang6.

Note that only kubeflow members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @Thor-wl @shinytang6

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.

@gaocegege
Copy link
Member

I think the main purpose of #123 is to avoid the direct dependency to k8s. Then I am wondering if we should upgrade the version to 1.19.

Do you want to add context first, then we can eliminate the k8s import packages?

@Thor-wl
Copy link
Contributor

Thor-wl commented Mar 30, 2021

I'm both OK for avoiding the direct depend dependency to k8s first or upgrade to k8s to v1.19 first. You can make a decision @Jeffwan @gaocegege

@Jeffwan
Copy link
Member Author

Jeffwan commented Mar 30, 2021

I think the main purpose of #123 is to avoid the direct dependency to k8s. Then I am wondering if we should upgrade the version to 1.19.

Do you want to add context first, then we can eliminate the k8s import packages?

@gaocegege I think your concern is reasonable. community is releasing 1.21. It's better to keep < 3 version changes with latest version and we will update to higher version sometime soon.

1.18 brings in context changes, I am ok to bump to 1.18. The major reason I choose 1.19 is because volcano/api now is using 1.19 https://github.com/volcano-sh/apis/blob/cfacea273e7da6b53170cc00ece9b2caf019316f/go.mod#L6-L10

Another possible solution is to ask volcano/api to downgrade to version >=1.16 <=1.17 and we don't need client-go related changes. But we will still need to upgrade dependencies later.

@Thor-wl
Copy link
Contributor

Thor-wl commented Mar 30, 2021

I think the main purpose of #123 is to avoid the direct dependency to k8s. Then I am wondering if we should upgrade the version to 1.19.
Do you want to add context first, then we can eliminate the k8s import packages?

@gaocegege I think your concern is reasonable. community is releasing 1.21. It's better to keep < 3 version changes with latest version and we will update to higher version sometime soon.

1.18 brings in context changes, I am ok to bump to 1.18. The major reason I choose 1.19 is because volcano/api now is using 1.19 https://github.com/volcano-sh/apis/blob/cfacea273e7da6b53170cc00ece9b2caf019316f/go.mod#L6-L10

Another possible solution is to ask volcano/api to downgrade to 1.17 and we don't need client-go related changes. But we will still need to upgrade dependencies later.

It's OK for me to provide volcano.sh/apis release-1.17 to match k8s.io v1.17. Look forward to your decision.

@Jeffwan
Copy link
Member Author

Jeffwan commented Mar 30, 2021

volcano.sh/apis v1.2.0-k8s1.16.15 this makes sense. I think @gaocegege will like it. :D
In this case, we will not bump k8s version at this moment, this PR can be left for future usage.

@gaocegege
Copy link
Member

SGTM! I think we will update to a higher version soon.

@Thor-wl
Copy link
Contributor

Thor-wl commented Mar 30, 2021

volcano.sh/apis v1.2.0-k8s1.16.15 this makes sense. I think @gaocegege will like it. :D
In this case, we will not bump k8s version at this moment, this PR can be left for future usage.

SGTM! I think we will update to a higher version soon.

@Jeffwan @gaocegege So what's the version shall i provide?

Jeffwan added 3 commits May 17, 2021 21:03
1. Upgrade k8s dependency to 1.19
2. 1.18 client-go add context and extra options. Adapt to the new changes.
3. Upgrade golang to 1.15 to match golang used in 1.19

Signed-off-by: Jiaxin Shan <[email protected]>
@Jeffwan
Copy link
Member Author

Jeffwan commented May 18, 2021

/cc @kubeflow/wg-training-leads
/hold cancel

This unblocks user's request @chxk in #132

Copy link
Member

@terrytangyuan terrytangyuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Others PTAL.

Copy link
Member

@andreyvelich andreyvelich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for doing this @Jeffwan!
/lgtm

@google-oss-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich, Jeffwan, terrytangyuan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [Jeffwan,terrytangyuan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-robot google-oss-robot merged commit f162091 into kubeflow:master May 18, 2021
georgkaleido pushed a commit to georgkaleido/common that referenced this pull request Jun 9, 2022
* Use setup.cfg for packaging

* Add MANIFEST.in to exclude non-related files from removebg-core, Configure library in pyproject.toml according to PEP-612

* Add requires-python 3.7+ as we introduced dataclasses

* Update circleci config to use pip, build and twine instead of setup.py

* Adjust manifest

* Configure in setup.cfg as requirements do not get installed when specifying in pyproject.toml

* Remove PEP-621 pyproject.toml config for now

* Update circleci config check and install

* Remove wrong progess bar argument

* Update packaging to be able to install via pip locally

* Update venv path

* Set progress bar off

* Use FURY_AUTH_TOKEN

* Update python requires

Co-authored-by: Paul Angerer <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants