Skip to content

Backport of Update k8s docs into release/1.19.x #30817

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 3, 2025
Merged

Backport of Update k8s docs into release/1.19.x #30817

merged 1 commit into from
Jun 3, 2025

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #30173 to be assessed for backporting due to the inclusion of the label backport/1.19.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@Zlaticanin
This person should resolve the merge-conflict(s) by either:

  • Manually completing the cherry picks into this branch
  • Creating a new branch and manually cherry-picking all commits being backported

merge conflict error: POST https://api.github.com/repos/hashicorp/vault/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

Original PR had no description content.

Overview of commits

@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jun 2, 2025
@github-actions GitHub Actions
Copy link

github-actions bot commented Jun 2, 2025

CI Results:
All Go tests succeeded! ✅

@Zlaticanin
Update k8s docs (#30173)
0deb46c 
* Update k8s docs

* update with suggestions

* update
@Zlaticanin Zlaticanin force-pushed the backport/VAULT-35099/update-k8s-docs/vertically-fleet-bull branch from 81fc5e2 to 0deb46c Compare June 2, 2025 22:11
@Zlaticanin Zlaticanin marked this pull request as ready for review June 2, 2025 22:12
@Zlaticanin Zlaticanin requested review from a team as code owners June 2, 2025 22:12
@github-actions GitHub Actions
Copy link

github-actions bot commented Jun 2, 2025

Build Results:
All builds succeeded! ✅

@Zlaticanin Zlaticanin merged commit ae181c5 into release/1.19.x Jun 3, 2025
48 of 51 checks passed
@Zlaticanin Zlaticanin deleted the backport/VAULT-35099/update-k8s-docs/vertically-fleet-bull branch June 3, 2025 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Zlaticanin Zlaticanin Zlaticanin approved these changes

@schavis schavis schavis approved these changes

@scellef scellef Awaiting requested review from scellef scellef is a code owner automatically assigned from hashicorp/vault-customer-engineering

@elliesterner elliesterner Awaiting requested review from elliesterner elliesterner is a code owner automatically assigned from hashicorp/vault-customer-engineering

Assignees

@Zlaticanin Zlaticanin

Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-milestone
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@hc-github-team-secure-vault-core @Zlaticanin @schavis