Skip to content
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

[release/v1.8] feat: add flag to skip TLS verification #3554

Conversation

kubermatic-bot
Copy link
Contributor

@kubermatic-bot kubermatic-bot commented Feb 5, 2025

This is an automated cherry-pick of #3522

/assign xmudrii

Add parameter `insecure` to the `backups-restic` addon used to disable/skip the TLS verification

steled and others added 2 commits February 5, 2025 11:32
@kubermatic-bot kubermatic-bot added do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 5, 2025
Copy link
Member

@xmudrii xmudrii left a comment

Choose a reason for hiding this comment

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

/kind feature
/lgtm
/approve

@kubermatic-bot kubermatic-bot added kind/feature Categorizes issue or PR as related to a new feature. cherry-pick-approved Indicates a PR has been approved by release managers. lgtm Indicates that a PR is ready to be merged. and removed do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. labels Feb 5, 2025
@kubermatic-bot
Copy link
Contributor Author

LGTM label has been added.

Git tree hash: 716f5eda687f23c19600ce647727f4cb75ed3fdb

@kubermatic-bot
Copy link
Contributor Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xmudrii

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Feb 5, 2025
@kubermatic-bot kubermatic-bot merged commit b7a1eb1 into kubermatic:release/v1.8 Feb 5, 2025
14 checks passed
@kubermatic-bot kubermatic-bot deleted the cherry-pick-3522-to-release/v1.8 branch February 5, 2025 13:13
@xmudrii
Copy link
Member

xmudrii commented Feb 6, 2025

/release-note-edit

Add parameter `insecure` to the `backups-restic` addon used to disable/skip the TLS verification

@xmudrii
Copy link
Member

xmudrii commented Feb 6, 2025

/release-note-edit

Add parameter `insecure` to the `backups-restic` addon used to disable/skip the TLS verification.

@kubermatic-bot
Copy link
Contributor Author

@xmudrii: /release-note-edit must be used with a release note block.

In response to this:

/release-note-edit

Add parameter `insecure` to the `backups-restic` addon used to disable/skip the TLS verification.
`

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-sigs/prow repository.

@xmudrii
Copy link
Member

xmudrii commented Feb 6, 2025

/release-note-edit

Add parameter `insecure` to the `backups-restic` addon used to disable/skip the TLS verification

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a PR has been approved by release managers. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants