Skip to content

Conversation

@scottilee
Copy link
Contributor

Release 12.0.0a1 introduces several changes and is compatible with Kubernetes v1.16.

[x] Updated the constants version
[x] Generated client changes
[x] Applied hotfixes
[x] Updated python-base submodules
[x] Updated the CHANGELOG

Fixes #1052

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Mar 30, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: scottilee
To complete the pull request process, please assign yliaog
You can assign the PR to them by writing /assign @yliaog in a comment when ready.

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

Details Needs approval from an approver in each of these files:

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

@k8s-ci-robot k8s-ci-robot requested review from roycaihw and yliaog March 30, 2020 17:38
@k8s-ci-robot k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Mar 30, 2020
# HTTP header `Content-Type`
header_params['Content-Type'] = self.api_client.select_header_content_type( # noqa: E501
['application/json-patch+json', 'application/merge-patch+json', 'application/strategic-merge-patch+json']) # noqa: E501
['application/json-patch+json', 'application/merge-patch+json', 'application/strategic-merge-patch+json', 'application/apply-patch+yaml']) # noqa: E501
Copy link

Choose a reason for hiding this comment

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

Hi. I have K8S 1.16. I noticed one interesting bug. If I call patch_namespaced_deployment through the client to DELETE 1 or more environment variables, then the request is successful, however, the deployment itself is not updated.

After a little research, I found out that the select_header_content_type method called here returns just the 1st element of this array. I also found out that if you put the 2nd element of an array in the header, then the deployment is updated perfectly.

Suggested change
['application/json-patch+json', 'application/merge-patch+json', 'application/strategic-merge-patch+json', 'application/apply-patch+yaml']) # noqa: E501
['application/merge-patch+json', 'application/json-patch+json', 'application/strategic-merge-patch+json', 'application/apply-patch+yaml']) # noqa: E501


# client version for packaging and releasing.
CLIENT_VERSION = "11.0.0-snapshot"
CLIENT_VERSION = "12.0.0a1"
Copy link
Member

Choose a reason for hiding this comment

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

This PR targets the master branch. I think we should first generates a 12.0.0-snapshot client in the master branch with API changes from upstream release-1.16. Then generates a 12.0.0a1 client in the release-12.0 branch with only version constant changes.

**Deprecation Notice**
v12.0.0 of the client follows the Kubernetes [deprecation policy](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew) and will
be deprecated as and when Kubernetes version v1.16 gets deprecated.

Copy link
Member

Choose a reason for hiding this comment

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

Could you add CHANGELOG about the API changes generated?

@scottilee
Copy link
Contributor Author

Will open a new PR when #1141 merges.

@scottilee scottilee closed this Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cut version 12.0.0 alpha for client

4 participants