-
Notifications
You must be signed in to change notification settings - Fork 566
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
fix(release): add support v3.4.1 for kubesphere cluster-configuration.yaml format error #2034
Conversation
Signed-off-by: joyceliu <[email protected]>
/cherry-pick release-3.0 |
@littleBlackHouse: once the present PR merges, I will cherry-pick it on top of release-3.4 in a new PR and assign it to you. 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. |
/lgtm |
LGTM label has been added. Git tree hash: bb61f26be9ab982a5e6a361460abf9bdc7166334
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: littleBlackHouse, pixiake 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 |
@littleBlackHouse: cannot checkout 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. |
/cherry-pick release-3.0 |
@littleBlackHouse: new pull request created: #2035 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. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
add support v3.4.1 for kubesphere cluster-configuration.yaml format error
Special notes for reviewers:
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: