Skip to content

Merge master into release-next#720

Merged
jetstack-bot merged 58 commits intocert-manager:release-nextfrom
JoshVanL:release-next-merge-v1.6.0-beta.0
Oct 19, 2021
Merged

Merge master into release-next#720
jetstack-bot merged 58 commits intocert-manager:release-nextfrom
JoshVanL:release-next-merge-v1.6.0-beta.0

Conversation

@JoshVanL
Copy link
Contributor

@JoshVanL JoshVanL commented Oct 19, 2021

This PR mergees master into release-next. Here you can see the diff between this branch and the current master. The changes look sane..

/assign @jakexks

aazon and others added 30 commits August 4, 2021 19:18
A description of resource `Certificate` has `foo.example.com` and
`bar.example.com` in the `dnsNames` section, which is different from the
diagram that has `example.com` and `foo.example.com` domains. When I was
looking at the schema in the article, I thought that the part related to
`bar.example.com` is to follow, but it didn't and therefore was a bit
confusing.

Signed-off-by: Alex Litvinenko <alex@litvinenko.tech>
Signed-off-by: Maël Valais <mael@vls.dev>
"d" is not a valid character for a duration

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
Merge release-next into master for the 1.5 release
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
Fix broken certificaterequest yaml
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
this follows cert-manager/testing#553 being merged

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
we never looked at the output from this command - it didn't fail the
build. it also has so many false positives that it would take a
significant amount of effort to be able to use it effectively.

I like the idea of tools like this, but I don't think this specific tool
- with the false-positives - is providing any value to us here.

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
forcing the value is harmful in environments which use a local caching
GOPROXY

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
Signed-off-by: irbekrm <irbekrm@gmail.com>
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
Update plugin download command to always download latest version
Don't force GOPROXY when generating docs
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
…provider_tests

adding docs for cloud provider tests
Signed-off-by: irbekrm <irbekrm@gmail.com>
The 'latest' GitHub release can be a patch for an older minor release, so we have to specify version number explicitly

Signed-off-by: irbekrm <irbekrm@gmail.com>
…ctions

Signed-off-by: irbekrm <irbekrm@gmail.com>
Bump helm installed cm version v1.5.0 -> v1.5.3
Signed-off-by: Aidan Jensen <aidan@artificial.com>
Remove trailing `/` in docker registry
fixes cert-manager#696

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
Signed-off-by: joshvanl <vleeuwenjoshua@gmail.com>
Signed-off-by: James Westby <james@jameswestby.net>
@netlify
Copy link

netlify bot commented Oct 19, 2021

✔️ Deploy Preview for cert-manager-website ready!

🔨 Explore the source changes: 1edc9be

🔍 Inspect the deploy log: https://app.netlify.com/sites/cert-manager-website/deploys/616edd0f959b630009ca5ccc

😎 Browse the preview: https://deploy-preview-720--cert-manager-website.netlify.app

@jetstack-bot jetstack-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Oct 19, 2021
@JoshVanL JoshVanL changed the base branch from master to release-next October 19, 2021 14:42
@jetstack-bot jetstack-bot added do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 19, 2021
@JoshVanL JoshVanL force-pushed the release-next-merge-v1.6.0-beta.0 branch from e50d3a9 to 912ac24 Compare October 19, 2021 14:43
@JoshVanL
Copy link
Contributor Author

/dco override

@JoshVanL
Copy link
Contributor Author

/dco-override

@JoshVanL
Copy link
Contributor Author

/override dco

@jetstack-bot
Copy link
Contributor

@JoshVanL: Overrode contexts on behalf of JoshVanL: dco

Details

In response to this:

/override dco

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.

@JoshVanL
Copy link
Contributor Author

/assign @jakexks

@JoshVanL JoshVanL changed the title Merge master into release-next Rebase release-next onto master Oct 19, 2021
@JoshVanL JoshVanL force-pushed the release-next-merge-v1.6.0-beta.0 branch from 912ac24 to 1edc9be Compare October 19, 2021 14:58
@jetstack-bot
Copy link
Contributor

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

Details

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. I understand the commands that are listed here.

@JoshVanL JoshVanL changed the title Rebase release-next onto master Merge master into release-next Oct 19, 2021
@JoshVanL
Copy link
Contributor Author

/override dco

@jetstack-bot
Copy link
Contributor

@JoshVanL: Overrode contexts on behalf of JoshVanL: dco

Details

In response to this:

/override dco

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.

Copy link
Member

@jakexks jakexks left a comment

Choose a reason for hiding this comment

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

/lgtm

@jetstack-bot jetstack-bot added the lgtm Indicates that a PR is ready to be merged. label Oct 19, 2021
@jakexks jakexks added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. and removed dco-signoff: no Indicates that at least one commit in this pull request is missing the DCO sign-off message. do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. labels Oct 19, 2021
@jetstack-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jakexks, JoshVanL

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:

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

@jetstack-bot jetstack-bot merged commit 1262797 into cert-manager:release-next Oct 19, 2021
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 cherry-pick PR into a release branch has been approved by the release branch manager dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. lgtm Indicates that a PR is ready to be merged. 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.